Integrate

AlienMonster gives your coding agent strategic context. Your agent reads your strategy repo before making non-trivial changes and takes recorded decisions and assumptions into account.

What lives on disk

Running npx alienmonster init writes a .alienmonster/ directory to your repo, plus five agent config files at the repo root. The directory starts nearly empty — your first strategy session is what fills it.

export, sync, and watch copy your strategy from the AlienMonster server down to .alienmonster/ so that agents reading local files can access it.

Read more in The .alienmonster/ directory.

How agents know to use it

Five agent config files at your repo root tell coding agents where the strategy lives and when to consult it:

• CLAUDE.md, AGENTS.md, and .cursorrules — each contains a managed section with strategy context and instructions.
• .claude/settings.json — adds a PreToolUse hook that runs alienmonster status before each tool call.
• .cursor/rules/alienmonster.mdc — Cursor's rule file.

Read more in Agent config files.

Supported agents

Sync model

Your strategy lives authoritatively on the AlienMonster server. The .alienmonster/ directory on disk is a cache that mirrors it. status shows whether your cache is current. sync refreshes it if it is not. watch keeps it live via server-sent events.

Read more in Sync model.