Product Positioning
What Aboard Nexus is, what it solves, and what it deliberately does not do yet.
Aboard Nexus is a local-first, Workspace-centric AI workbench driven by Agents and extended through Plugins and Providers.
Its core loop is:
Workspace -> Context -> Agent -> Provider -> Tool -> Approval -> Run -> Artifact -> EvidenceCurrent boundary
- Implemented: multiple Workspaces, Workspace-scoped Plugin lifecycle, declarative UI contributions, basic streaming AI Runtime protocol, capability discovery, and read-only Docs MCP.
- Partially implemented: Provider selection, Agent Profiles, Workflow/Knowledge resources, page generation, and Handoff.
- Designed / not complete: Host-owned Tool Registry, complete Tool execution loop, Tool Approval resumption, Durable Runs, Provider capability contracts, and Worker isolation.
- Future reserved: Managed Agent Platform authority migration, external Plugin distribution, and isolated third-party applications.
- Deferred: implicit Provider fallback, side-effect execution from the documentation site, arbitrary third-party React injection, Marketplace, and dual-write synchronization.
Design goals are not current runtime capabilities. Use the Host runtime snapshot and page status markers as authority.
Non-goals
Aboard is not currently just a chat client, a model aggregator, an unconstrained script runner, or a cloud collaboration SaaS.
How is this guide?