Acahti
EN中文GitHubSelf-host

Delivery control plane for coding agents

Agents ship. You watch.

Acahti is self-hosted Git, pull requests, CI checks, package registries and the work around them (projects, iterations, tickets, knowledge and tests) behind one identity and one MCP endpoint. Your coding agent pushes, waits on checks, repairs failures and merges when the pipeline is green; Aidy plans and reports with you inside the app.

Connect your agent

Plugin, skill, and MCP. Replace https://acahti.example.com with your instance.

Plugin (Cursor)
/add-plugin acahti@https://github.com/acahti-ai/acahti-plugin
Skill
Install https://acahti.benchyard.com/skill.md
Benchyard
npm install -g @acahti-ai/acahti
# Set ACAHTI_ROOT_URL and ACAHTI_TOKEN in Benchyard Secrets
acahti whoami
acahti inbox

One loop, start to merge

The agent decides and repairs. Acahti supplies authenticated operations and structured results.

repo_get → branch_list → edit and push
                           ↓
                     checks_wait
                      ↙       ↘
           failed-step logs    green checks
                ↓                   ↓
            fix / rerun       review → pr_merge

Your agent

  • Connects with a personal Access Token over MCP or the CLI
  • Pushes, waits on checks, reads only the failed logs
  • Opens pull requests and merges when the latest pipeline is green
  • Publishes npm and PyPI packages as you

You

  • Invite members and set branch protection
  • Own pipeline secrets; values never come back out
  • Watch the Board and the Inbox of failed runs and ready PRs
  • Approve gated deploys and the changes Aidy proposes

Built for agents, run by you

One identity, checked merges, planning both can read, and infrastructure you own.

  • One identity

    The same account and token for Git, MCP, the REST API, npm, and PyPI. Commits carry the identity the instance hands the agent.

  • Checked merge

    pr_merge succeeds only when the newest pipeline on the head commit is green. No green, no merge.

  • Shared planning

    Projects, iterations with a scope baseline, deliveries that name their todos, and one brief the app and agents read alike.

  • Any agent

    Claude Code, Codex, Cursor, or any MCP client. Shell agents and CI jobs use the acahti CLI; Aidy works inside the app.

  • Your infrastructure

    One public gateway in front of Forgejo and Woodpecker, which stay private. Pipelines run on a separate Runner.

  • Open source

    Apache-2.0. Git data lives in a standard forge you can export at any time.

Self-host in one command

On any Linux host. The installer installs Docker if needed, pulls the release image, generates secrets, and starts the instance. Run it again to upgrade.

On your server
curl -fsSL https://acahti.benchyard.com/install.sh | bash -s -- --domain acahti.example.com
Or let your coding agent do it over SSH
Install https://acahti.benchyard.com/install.md

Needs 2 GiB RAM and a public HTTPS hostname; add --runner user@host for CI on a second machine. Install guide

Product here, instances there

This site is the product; each team runs its own instance.

This site is Acahti: the docs, the agent skill, the install guide. Each team runs its own instance, such as https://acahti.example.com, which serves the web app, MCP at /mcp, and Git. Agents install the skill once and learn everything instance-specific from whoami.

How Acahti compares to GitHub, GitLab, and Forgejo →