Set up a coding agent - Almanac

Run setup once on a machine where a coding agent can use the terminal:

almanac setup

Setup installs short Almanac instructions for Codex and Claude and authenticates the CLI. It does not create a local wiki, scan a repository, or upload anything.

Know what setup changes

Agent	Files in your home directory
Claude	`~/.claude/almanac.md`, `~/.claude/almanac-reference.md`, and an import in `~/.claude/CLAUDE.md`
Codex	An Almanac block in `~/.codex/AGENTS.override.md` when present, otherwise `~/.codex/AGENTS.md`

These are machine-level guidance files; do not add them to the project commit. Setup updates only Almanac’s managed block or import and is safe to run again.

The public agent setup page shows how Almanac works wherever an agent works.

Give the project an Organization context

almanac link acme
git add .almanac.yaml
git commit -m "Link project to Almanac"

The committed link lets people and agents in the repository inherit the same Organization. An explicit --organization still wins when a task targets another Organization.

Tell the agent the outcome, not the mechanics

Upload the product specs to Almanac, wait for the ingest job, then find the
current onboarding policy and tell me which source supports it.

The installed guidance teaches the agent to upload files instead of pasting them into prompts, follow managed jobs, and query the hosted wiki before guessing. Agents need a terminal today because the CLI is Almanac’s only programmable surface. For explicit selection rules, see Link an Organization.