Editor plugin

The Acahti plugin packages everything an editor agent needs in one install: the skill, the MCP server configuration, and rules that apply only to Acahti remotes. It adds no tools of its own; editor operations use the instance through MCP. The CLI stays for shells and Benchyard tasks.

Install#

Cursor: in the agent input, run:

/add-plugin acahti@https://github.com/acahti-ai/acahti-plugin

Then set ACAHTI_ROOT_URL under Customize → Acahti → Configure (no trailing slash). Or copy the package directly:

cp -R cursor ~/.cursor/plugins/local/acahti

Codex: install from the repository's marketplace (or curl the skill into ~/.codex/skills/acahti), then add and authenticate the MCP server. No CLI install:

codex mcp add acahti --url https://acahti.example.com/mcp
codex mcp login acahti
# or: codex mcp add acahti --url https://acahti.example.com/mcp --bearer-token-env-var ACAHTI_TOKEN

Workspace packages already bundle the connection: run their setup skill and complete OAuth. In Benchyard shell tasks, use ACAHTI_ROOT_URL and ACAHTI_TOKEN in Secrets with the CLI; no browser callback is needed. Do not also add acahti to the editor's own MCP file; one connection per instance.

What it adds#

• Skill: a small bootstrap that calls whoami and follows whoami.skill_url, so the full skill always comes from this site.
• Rules: Git author checks for commits bound for Acahti, and protected-branch and post-push CI habits. Other remotes are untouched.
• Codex hooks (optional): reminders only; they never block Git or change its configuration.

Verify#

Run setup after installation. The agent guides OAuth for native plugins or Secrets for Benchyard shells, then calls whoami and inbox over MCP or CLI. Logging into the website alone does not connect MCP.

For an organization#

A workspace build can bundle a fixed instance URL, so members authorize the bundled OAuth connection. It never bundles credentials. See the plugin repository's distribution guide.