Core Concepts
Invocation Routing & Isolation
Explain why plugin calls do not cross agent environments and how routing works
Invocation Routing & Isolation
Short Answer
- one running agent binds to one project root
- plugin calls stay inside that agent by default
- cross-agent routing only happens when you explicitly change host/port or target project
Main Call Path
1) CLI -> plugin
- resolve the target project
- resolve the daemon endpoint
- call
/api/plugins/list,/api/plugins/control,/api/plugins/command, or another/api/plugins/*endpoint - dispatch inside the current agent
2) plugin -> plugin points
Plugins should not depend on plugin-private implementation. They only trigger the extension points they define.
- plugin-point dispatch is in-process
- the same agent execution context is reused
- shell is not involved by default
Endpoint Resolution Priority
- explicit CLI
--host/--port DC_CITY_HOST/DC_CITY_PORT- current project daemon metadata
- default
127.0.0.1:5314
Port and Instance Lifecycle
How console, agent, and plugin endpoints coordinate on port allocation, routing, and runtime lifecycle
Console Registration, Execution Context, and Shell Flow
Explains console registry writes, how the execution context surface connects runtime capability, and how shell injects environment