Skip to content

Apply compact assistant edits without rewriting experiments - #468

Merged
ctfbruce merged 9 commits into
mainfrom
fix/assistant-editor-incremental
Nov 5, 2026
Merged

ctfbruce merged 9 commits into
mainfrom
fix/assistant-editor-incremental

Conversation

@ctfbruce

@ctfbruce ctfbruce commented Nov 5, 2026 •

Copy link
Copy Markdown
Collaborator

Small assistant changes previously regenerated every node and wire, increasing response time and risking unrelated edits. The assistant can now return bounded edits to existing workflows; the server applies them to a copy, validates the complete graph, and returns the same full-document response expected by the editor. Invalid proposals leave the current draft unchanged. Corrections can repair a rejected proposal without repeating all of it.

Built-in block names and channel value types are constrained to supported choices. Custom blocks use explicit references and must have definitions. Instructions describe supported Go packages and the distinction between action execution and data dependencies. New participants and channels still use complete-document proposals.

Focused assistant tests and race checks passed. In a same-prompt provider comparison, a target-only edit fell from 17.34 seconds to 2.72 seconds with exact preservation and successful WASM compilation. These are individual samples, not latency guarantees. Creation, report-addition and coordinated DNS/TCP fixtures also compiled during testing.

Complex generation remains fallible: a larger DNS/exchange/TCP prompt still reached the existing two-call limit with invalid channel references and was rejected without returning a draft. This change does not establish complete semantic validation of arbitrary generated programs. Hosted browser acceptance passed: create a three-block workflow, change only its target, compile, submit through the normal review flow, and confirm a successful TCP connection between two owned executors. Merge is held by an external CI dependency failure: the initial attempt and one exact-head retry both stopped during kernel-job dependency installation because the Debian snapshot service returned 503/504 errors, before kernel tests ran. The local lane also stalled on metadata download in the initial attempt. No required checks have been bypassed.

@ctfbruce
ctfbruce merged commit 4f1cca5 into main Nov 5, 2026
17 checks passed
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.

1 participant