AIMAKE FOR AGENTS

Your agents.
One shared record.

Your agent can build. AIMake keeps the project knowledge it needs between sessions.

Connect your agent Read the skill

Agent access on every paid plan.

Claude Codex Your agent

PROJECT RECORD

CURRENT WIN

Ship the next release.

Context: GitHub · source · AGENTS.md
Decisions: Why this approach
Next action: Review the release evidence
Proof: Pull request · tests · built review

RETAINED BETWEEN SESSIONS

ILLUSTRATIVE PROJECT

CONNECTION STANDARD

MCPOAuth + PKCEProject-scoped access

01 / WHAT SURVIVES

A project that
carries forward.

Saved in AIMake, available to your next authorized agent.

Make the connection

01
Knowledge
Repository context and durable operating notes.
02
Decisions
Choices, constraints and their rationale.
03
Progress
Wins, tasks, blockers and follow-ups.
04
Evidence
Saved approvals, proof links and activity.

02 / CONNECT

Connect once.

Use a client supporting Streamable HTTP and OAuth.

Create an AIMake workspace; open your repository in your harness.
Give your agent the setup prompt below.
Authorize the organization, projects and permissions.
Let your agent save the project instructions, then describe your work normally.

Connection skill

ONE-TIME REPOSITORY SETUP

Set up AIMake for this repository. Read https://www.aimake.dev/skills/aimake-mcp/SKILL.md and follow its one-time setup instructions. Connect https://api.aimake.dev/mcp using your supported OAuth flow if needed. List my AIMake projects and help me select the project for this repository.
Preserve existing repository instructions. Save the verified project ID and a pointer to the skill in the persistent repository instructions this harness actually loads. Do not store tokens or set a global project default. If this repository is already bound to a different project, ask before replacing it. If persistence is unsupported, explain that and retain a manual recovery brief.
Read back the saved instructions and call prepare_work to verify project access. Report the file changed and what was verified; do not claim a fresh-session test unless performed. In later user-started sessions, load the binding and skill, prepare the user's requested work, and inspect continuation candidates when no win is selected. Prepare the matching win to recover its full saved reviews before acting; clarify ambiguous work and preserve human approvals. Continue only work I authorize. Finish the setup session with its verified outcome. After setup, I should be able to describe a change or say "Continue with my AIMake feedback" without another copied prompt.

MANUAL SETUP · MCP ENDPOINT

Requires a harness that loads persistent repository instructions. Your agent verifies setup; copying alone does not complete it. Keep access tokens out of prompts.

03 / YOUR CONTROL

Delegate execution.
Keep judgment.

YOUR HARNESS

Execution

Supplies the model, edits code and runs tools.

AIMAKE

The system

Work through your harness; use AIMake’s web UI to see and govern the work.

YOU

Judgment & review

Set priorities, grant access and judge the evidence.

What does AIMake control?

AIMake checks permissions, preparation and required proof for its records. Your harness controls code execution. MCP accepts HTTPS proof links; upload files through the web.

04 / CHOOSE YOUR GUIDE

Start with your harness.

See pricing

Your agents.One shared record.

Ship the next release.

A project thatcarries forward.

Knowledge

Decisions

Progress

Evidence