Core Concepts
Invocation Routing & Isolation
Explain why service and plugin calls do not cross agent environments and how routing works
Invocation Routing & Isolation
Short Answer
- one running agent binds to one project root
serviceandplugincalls 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 -> service / plugin
- resolve the target project
- resolve the daemon endpoint
- call
/api/services/*or/api/plugins/* - dispatch inside the current agent
2) service -> plugin points
Services 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_SERVER_HOST/DC_SERVER_PORTDC_CTX_SERVER_HOST/DC_CTX_SERVER_PORT- current project daemon metadata
- default
127.0.0.1:5314
Port and Instance Lifecycle
How console, agent, service, and plugin 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 services and plugins, and how shell injects environment