Skip to content

Treat settings-owned MCP as guaranteeing read_thread on handoff - #680

Merged
SDSLeon merged 1 commit into
masterfrom
poracode/sunny-meteor-2afe2ef2
Sep 2, 2026
Merged

Treat settings-owned MCP as guaranteeing read_thread on handoff#680
SDSLeon merged 1 commit into
masterfrom
poracode/sunny-meteor-2afe2ef2

Conversation

@SDSLeon

@SDSLeon SDSLeon commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator
  • Tickets: none
  • Bugfix: Continue-in-provider handoff no longer treats composer MCP scope "none" as “no read_thread” when the target owns MCP from agent settings.
  • Providers that bake built-in servers at launch (composer has nothing to toggle) now use the thread-transcript strategy instead of extracting a context file.
  • Shared targetGuaranteesReadThreadTool helper plus dialog and unit coverage so settings-owned MCP and real “no MCP wiring” stay distinct.

- Count agentSettings MCP config as a guaranteed read_thread target
- Avoid context-file handoff when composer MCP scope is none
- Cover the dialog path and shared helper with tests
@SDSLeon
SDSLeon merged commit ddfc9cd into master Sep 2, 2026
8 checks passed
@SDSLeon
SDSLeon deleted the poracode/sunny-meteor-2afe2ef2 branch September 2, 2026 21:58
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