Developer Guide
This guide captures the implementation direction for Agent-Up. The Server owns orchestration and runtime state. Desktop, CLI, and MCP clients stay thin.
Agent-Up is a workspace manager, not an application framework. Every implementation decision should preserve framework agnosticism, zero application source changes, and multiple concurrent isolated workspaces.
MCP servers
orchestration
browser
audit
commits
verification
MCP is a protocol, not a slice. Each slice General lists that slice's tools and routes.
Those endpoints accept loopback connections anonymously, because on loopback the network restriction is the authentication. Any other address is answered with 404 unless AGENTUP_MCP_REMOTE_ENABLED=true and externalBearer is configured; see Workspaces for the permission floor each endpoint requires and what a remote caller without a usable token sees.
Start here
- Repo covers architecture rules, packaging, CI,
au-debug, design-system consumption, and telemetry. - Testing sets out how tests are written: builders, shared domain data, and setup that stays in the test.
- Mobile store release documents Mobile CI smoke builds and the dispatched Android and iOS store pipeline.
- Slice Generals use the same labels as User Docs: Workspaces, Applications, Git, Commits, Agents, Browser, Diagnostics, Verification, Configuration.
The Commit merge queue assessment and Desktop application hosting assessment are design notes, not the current contract.