Problem (one or two sentences)
Currently, tools for built-in modes cannot be modified. I want them to be editable. In particular I want Orchestrator was able to read .md files.
Context (who is affected and when)
I usually have a TASKS.md file in my project root. It contains a list of development phases and associated tasks. It's usually an entry point for a new chat. With it agents can clearly understand the current progress without additional context.
I want Orchestrator was able to read this file and also README.md file at beginning of new conversation. Unfortunately, I cannot configure it as it's not allowed to change tools for built-in modes.
So, by design Orchestrator is supposed to do the job only once per project- at the very beginning. Otherwise he is unable to get the already running project context.
The cheat fix is to tell the Orchestrator to spin the Code which would provide all the necessary files full text(not just summary) in order to inject that to the Orchestrator's context. This works fine, but I think built-in tool would be a conceptually better option.
Desired behavior (conceptual, not technical)
It's possible to change tools for built-in modes.
Constraints / preferences (optional)
No response
Request checklist
Zoo Code Task Links (optional)
No response
Acceptance criteria (optional)
No response
Proposed approach (optional)
No response
Trade-offs / risks (optional)
No response
Problem (one or two sentences)
Currently, tools for built-in modes cannot be modified. I want them to be editable. In particular I want Orchestrator was able to read .md files.
Context (who is affected and when)
I usually have a TASKS.md file in my project root. It contains a list of development phases and associated tasks. It's usually an entry point for a new chat. With it agents can clearly understand the current progress without additional context.
I want Orchestrator was able to read this file and also README.md file at beginning of new conversation. Unfortunately, I cannot configure it as it's not allowed to change tools for built-in modes.
So, by design Orchestrator is supposed to do the job only once per project- at the very beginning. Otherwise he is unable to get the already running project context.
The cheat fix is to tell the Orchestrator to spin the Code which would provide all the necessary files full text(not just summary) in order to inject that to the Orchestrator's context. This works fine, but I think built-in tool would be a conceptually better option.
Desired behavior (conceptual, not technical)
It's possible to change tools for built-in modes.
Constraints / preferences (optional)
No response
Request checklist
Zoo Code Task Links (optional)
No response
Acceptance criteria (optional)
No response
Proposed approach (optional)
No response
Trade-offs / risks (optional)
No response