Preflight Checklist
Problem statement
Currently in Settings there's a primary "Identity" and then there are "Agents".. and each Agent is basically the same configuration as the primary agent (which even shows up under Agents and sends you to the identiy settings tab). This feels clunky; unless I'm mistaken, the "primary agent" notion only comes into play in a few places, like security settings ("restrict except for primary agent" or whatever it is), and then there are a bunch of things that are just routed to the primary agent (like channel connections).
Proposed solution
The "primary agent" should just become a "Default" tag that's applied to an agent. The Identity tab goes away, and Agents remain.
Places that were implicitly routed to the Default agent should have explicit routing choices -- for example, I should be able to create two telegram bots, one that routes to Agent A, and the other to Agent B. Configuration settings should include explicit lists of agents ("sandbox except for agents A B"). But the "Default" agent can still remain as a fallback until things become more flexible.
Additionally, things like MCP tools and skills should be configured per-agent ("inherit from Default" or other way to have defaults)... I may want an agent that has access to my home via home assistant, but other agents may not need to see those tools at all (or have to waste the context interrogating them).
Alternatives considered
No response
Category
Configuration
How important is this to your workflow?
Medium — would be very helpful
Additional context
No response
Chat session context (if applicable)
Preflight Checklist
Problem statement
Currently in Settings there's a primary "Identity" and then there are "Agents".. and each Agent is basically the same configuration as the primary agent (which even shows up under Agents and sends you to the identiy settings tab). This feels clunky; unless I'm mistaken, the "primary agent" notion only comes into play in a few places, like security settings ("restrict except for primary agent" or whatever it is), and then there are a bunch of things that are just routed to the primary agent (like channel connections).
Proposed solution
The "primary agent" should just become a "Default" tag that's applied to an agent. The Identity tab goes away, and Agents remain.
Places that were implicitly routed to the Default agent should have explicit routing choices -- for example, I should be able to create two telegram bots, one that routes to Agent A, and the other to Agent B. Configuration settings should include explicit lists of agents ("sandbox except for agents A B"). But the "Default" agent can still remain as a fallback until things become more flexible.
Additionally, things like MCP tools and skills should be configured per-agent ("inherit from Default" or other way to have defaults)... I may want an agent that has access to my home via home assistant, but other agents may not need to see those tools at all (or have to waste the context interrogating them).
Alternatives considered
No response
Category
Configuration
How important is this to your workflow?
Medium — would be very helpful
Additional context
No response
Chat session context (if applicable)