Skip to content

ExpressionAssistant: improve fence parsing - #7963

Merged
labkey-nicka merged 3 commits into
release26.7-SNAPSHOTfrom
26.7_fb_assistant_1487
Aug 21, 2026
Merged

ExpressionAssistant: improve fence parsing#7963
labkey-nicka merged 3 commits into
release26.7-SNAPSHOTfrom
26.7_fb_assistant_1487

Conversation

@labkey-nicka

@labkey-nicka labkey-nicka commented Aug 20, 2026

Copy link
Copy Markdown
Contributor

Rationale

This seeks to address #1487 by improving edge case detection and handling for fence parsing.

Related Pull Requests

Changes

  • Fence parsing: accept any backtick length, use only the first info-string token, and scan all responses at once.
  • Prompt fix: the four-backtick example could lead the model to emit fences the parser missed.
  • Log the raw response at debug, and warn when a validator payload renders as prose instead of an apply action.
  • Unit coverage for the fence shapes and leak detector

@labkey-nicka labkey-nicka self-assigned this Aug 20, 2026
@labkey-nicka
labkey-nicka merged commit 6c7125f into release26.7-SNAPSHOT Aug 21, 2026
6 of 9 checks passed
@labkey-nicka
labkey-nicka deleted the 26.7_fb_assistant_1487 branch August 21, 2026 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants