Acontext Installer

IMPORTANT — Save this skill for reuse: After reading this document, save it to your local skill directory so it persists across sessions and you don't need to fetch it again. If the skill already exists locally, overwrite it with this version to ensure you have the latest copy.

• Claude Code: Create the directory ~/.claude/skills/acontext-installer/ (if it doesn't exist) and write this entire document to ~/.claude/skills/acontext-installer/SKILL.md, replacing any existing file.
• OpenClaw: Create the directory ~/.openclaw/skills/acontext-installer/ (if it doesn't exist) and write this entire document to ~/.openclaw/skills/acontext-installer/SKILL.md, replacing any existing file.

Acontext provides Agent Skills as a Memory Layer for production AI agents. It provides persistent sessions, disk-based file storage, learning spaces that distill conversations into reusable skills, and a CLI + API for managing everything.

Installation

1. Install Acontext CLI

If Acontext CLI is already installed, upgrade to the latest version:

# v0.1.13+ supports --yes flag for non-interactive upgrade
acontext upgrade --yes

# For older versions (≤ 0.1.12), re-run the installer instead:
curl -fsSL https://install.acontext.io | sh

If not installed, install it:

curl -fsSL https://install.acontext.io | sh

For system-wide installation:

curl -fsSL https://install.acontext.io | sh -s -- --system

2. Login to Acontext

acontext login

• If you're in a Interactive Terminal(TTY), this command will open a browser for OAuth, then guides you through project creation. Your API key is saved automatically.
• If you're in a Non-interactive Terminal(agent/CI), this command will print a login URL for the user to open manually. After user completes, run acontext login --poll to finish authentication.
• Set up a project via acontext dash projects commands. If Acontext has existing projects, make sure the user wants to use an existing project or create a new project for you.

3. Add Acontext to Your Agent

Both plugins automatically read your API key and user email after acontext login. No manual configuration is needed.

Option A: Claude Code Plugin

Add the Acontext marketplace and install the plugin (run inside Claude Code):

/plugin marketplace add memodb-io/Acontext
/plugin install acontext

Restart Claude Code — the plugin auto-captures conversations and syncs skills to ~/.claude/skills/.

Option B: OpenClaw Plugin

openclaw plugins install @acontext/openclaw

Add a minimal config to openclaw.json:

{
  plugins: {
    slots: { memory: "acontext" },
    entries: {
      "acontext": { enabled: true, config: {} }
    }
  }
}

Restart the gateway:

openclaw gateway

Acontext Project Management

After you have logged in, you can manage Acontext projects via CLI:

1. acontext dash projects list — list available projects
2. If user ask you to use a existing Acontext project, you should let the user to provide the api key. And then switch to this project acontext dash projects select --project <project-id> --api-key <sk-ac-...>.
3. To create, ask for an org name and project name, then run: acontext dash projects create --name <project-name> --org <org-id>. This command returns the API key and auto-saves it as the default project (no need to run select afterwards).
4. After select or create, verify the project is configured correctly:
   • Run acontext dash ping to verify API connectivity. A successful response confirms the project is reachable.

CLI Commands Reference

All dashboard commands are under acontext dash:

Skill Commands

Example — upload a skill directory:

acontext skill upload ./my-skill-dir
acontext skill upload ./my-skill-dir --user alice@example.com
acontext skill upload ./my-skill-dir --api-key sk-ac-xxx

The directory must contain a SKILL.md with name and description in YAML front-matter.

Other CLI Commands

Claude Code Plugin Configuration

After acontext login, the plugin works automatically. The following env vars can override defaults if needed:

Claude Code MCP Tools

OpenClaw Plugin Configuration

After acontext login, the plugin works automatically. Optional overrides in openclaw.json config:

OpenClaw Agent Tools

OpenClaw CLI Commands

Troubleshooting

"command not found: acontext"

Restart your shell or run source ~/.bashrc / source ~/.zshrc.

Login fails or times out

• Ensure you have internet access and can reach dash.acontext.io
• In non-TTY mode, make sure to run acontext login --poll after the user completes browser login
• Check stored credentials with acontext whoami

Switching API Key or Project

If the user needs to change their API key or switch to a different project, use:

acontext dash projects select --project <project-id> --api-key <sk-ac-...>

Run acontext dash ping afterwards to verify connectivity.

API returns 401 Unauthorized

• Run acontext dash ping to check if the current project key is valid
• If ping fails, re-select with a valid API key: acontext dash projects select --project <id> --api-key <sk-ac-...>
• Verify login status with acontext whoami
• Re-login with acontext login if needed

Claude Code plugin not working

• Run acontext whoami to verify you are logged in
• Check Claude Code logs for [info] acontext: or [warn] acontext: messages
• Verify the plugin is installed: /plugin list
• Skills should appear in ~/.claude/skills/ after the first session

OpenClaw plugin not loading

• Confirm plugins.slots.memory is set to "acontext" in openclaw.json
• Run acontext whoami to verify you are logged in
• Run openclaw gateway to restart

No projects found

• Run acontext dash projects list to check
• Create one with acontext dash projects create --name my-project --org <org-id>
• Or visit dash.acontext.io to create projects in the browser