The short answer is no
Scoped does not start an agent, select a model, send a prompt, schedule a run, or execute the agent’s work. You use an agent in a compatible client or system outside Scoped. When you connect that client through MCP, Scoped can supply current project context and receive changes that the connection is authorized to make.
This boundary is deliberate. Teams can change agent tools without moving the project record, and they can keep one plan even when people and several external tools contribute to it.
Scoped keeps the work understandable
Scoped stores project and work-item state: projects, issues, comments, owners, priorities, relationships, and activity. It gives people a web or desktop interface and gives compatible agents an authorized MCP interface to the same work.
- People and authorized agents can start from current project context.
- Permitted agent updates return to the shared issue and activity record.
- MCP changes retain the authorizing person and connection source.
- Workspace-scoped grants can be inspected and revoked.
Learn how those controls work in the MCP guide and agent update walkthrough.
Scoped is not an agent runtime
Scoped does not host a model, manage prompts, decide which tools an agent may use outside Scoped, or keep an agent running in the background. It also does not convert an MCP grant into authority over another application. External actions remain the responsibility of the agent environment and whatever permissions you gave it there.
A recorded update is evidence that Scoped accepted a permitted project change. It is not evidence that the agent completed work in another system, that its conclusion was correct, or that a person approved every downstream action. Review important results in the systems where they occur.
Aether is a sibling product, not a requirement
Aether is Quintessence Group’s separate product for durable memory. Scoped focuses on projects and work-item state. You do not need Aether to use Scoped, and there is no built-in Aether integration available in Scoped today.
An optional integration for richer, source-linked context is planned. Until it exists, treat the products as independent: choose Scoped for the shared plan and Aether separately when its memory capabilities fit your agent system.
Use Scoped when the shared plan is the missing layer
Scoped fits when agents already work in tools your team has chosen, but everyone needs one current place for ownership, priorities, progress, and handoffs. If you need a product to run an autonomous agent or carry out work in third-party systems, Scoped alone is not that product.
Return to the product overview to see how people and agents share the plan, read the MCP guide, or choose a supported client setup.
Questions about the execution boundary
These answers distinguish the shared project system from the agent runtime and from authority an external tool may hold elsewhere.
Where does an agent run when it uses Scoped?+
It runs in the external client or environment you selected. Scoped exposes authorized project context and actions through MCP, but it does not host the model or agent process.
Can Scoped schedule or supervise an agent run?+
No. Scoped does not select a model, send prompts, schedule runs, keep an agent alive, or supervise its external tools. It stores the shared project state before and after permitted MCP calls.
Is Aether required to use Scoped with agents?+
No. Aether is a separate Quintessence Group memory product. A future optional integration is planned, but there is no built-in Aether integration in Scoped today.
Does a Scoped MCP grant authorize actions in other applications?+
No. The grant covers only the Scoped workspace, resource, and scopes approved during consent. Any access an agent has in another application comes from that application and the agent environment, not from Scoped.