Closed StevenBucher98 closed 2 months ago
Support switching agent by tagging an agent's name:
@<agent>
and @<agent> <query>
to switch to a different agent, or switch and send the query to that agent.
@<agent>
only, landing page of that agent will be display, just like running /agent use <agent>
@<agent> <query>
, we assume the user already knows about the capabilities of the target agent and thus won't show the landing page of that agent again.--shell-wrapper
is used at startup, the prompt defined in the wrapper.json
will be used for the agent declared in the same file. aish
will be used.@<agent>
are enabled.
Summary of the new feature / enhancement
In many other platforms including VSCode, and clio the concept of scoping responses to specific agents or extensions is being done by prefixing responses with " to switch between different agents and maintain that agent scope until user runs "@". This helps reduce the number of commands users need to run to switch agents and get the right answer to their question, previously users would need to do
@<scope>
, we should adopt a similar method where the user can run "@/agent use <x>
and then ask their question.Proposed technical implementation details (optional)
Since there are landing page that agents provide, we need to surface these somehow to ensure users can understand the capabilities of the agent and see necessary links before beginning to use this agent. To get this behavior we need to show the landing page when the user only uses the
@agent
without a query and then only on first time use for@agent <query>
.A complete user flow can be seen:
In the example above
ollama
agent has been used before and no longer needs to display the landing page.