Agent Mate overview

Purpose

Agent Mate helps a user bring an existing software project into AIOS, understand its current state, and move it forward. Projects may include repositories, local code, databases, APIs, images, deployment environments and communication channels. It uses the existing AIOS execution machinery.

Read the designs separately

Each linked artifact owns one area. Changes to credentials belong in Connections; task recovery belongs in Execution. The MCP artifact remains the detailed plan for project-scoped tools.

Architecture and runtime integration — How Agent Mate uses the existing runtime without depending on dashboard lifetime.
Project onboarding and discovery — Bring existing projects in and build an evidence-based understanding with the user.
Connections, credentials, and permissions — Shared connection ownership, project grants, key handling and revocation.
Chat experience and interactive controls — Discovery, questions, settings and tool activity in the familiar chat experience.
Execution, recovery, and progress tracking — Independent tasks, cancellation, uncertain outcomes and durable progress.
Project-scoped MCP for Agent Mate — The existing seven-task MCP plan: grants, bridge integration, revocation and acceptance.

Current position

The shadow environment has Agent Mate chat and an independently owned runtime host, plus Connections management. Four installed MCP services have passed representative connection and tool checks. Project-scoped MCP execution is still planned. Neither those checks nor the existence of a UI proves the entire onboarding-to-delivery workflow works.

These status notes summarize the recorded handoff and recent tests; this documentation split does not run or validate the whole product.

Delivery order

Prove the scoped MCP runtime and task-identity contract.
Implement connection bindings, grants and enforcement.
Connect that capability to project onboarding and chat controls.
Verify task activity, recovery and authorized result access.

Review rule

Each area records its scope, decisions, open questions, tasks and acceptance evidence. Keep the overview short; link to the detailed artifact instead of repeating its requirements.