Vision Land companion

The local companion for Vision Land. It connects your Codex and Claude Code sessions to your land, and — when the vision provider is selected — acts as the Vision bridge: this computer reads the Vision portfolio with a credential that never leaves it and pushes what it saw to Vision Land.

Pair this computer

Create a one-time code in Vision Land (Settings → Companions), then:

npx vision-land@latest pair <pairing-id.code>

Providers

npx vision-land@latest start --providers codex
npx vision-land@latest start --providers claude-code
npx vision-land@latest start --providers codex,claude-code
npx vision-land@latest start --providers vision
npx vision-land@latest start --providers codex,vision
npx vision-land@latest start --providers claude-code,vision
npx vision-land@latest start --providers codex,claude-code,vision

Run npx vision-land@latest install-claude once before selecting Claude Code.

The Vision bridge

Before starting the vision provider, save your Vision API key once:

npx vision-land@latest vision-key

It prompts for the key (no echo), validates it against Vision, and stores it in this computer's macOS Keychain. vision-key show displays the configured key and its source, vision-key test re-validates it, and vision-key clear removes it. The Vision address defaults to the production deployment; VISION_BASE_URL and VISION_API_KEY in the environment override the defaults (and are the way to run on platforms without the macOS Keychain).

The key stays on this computer. The companion sends Vision's response payloads (or an honest failure report) — never the key itself.

How often it talks to Vision Land

The companion wakes only when a loop is due, at most twice a minute, and sleeps in between.

| Loop | Interval | What travels | | --- | --- | --- | | Heartbeat | 30 s | Provider health and this table's intervals; the reply carries any pending commands (status requests, open session), so nothing polls for them | | Session snapshot | checked every 30 s | Codex and Claude Code sessions, pushed only when something changed | | Vision portfolio (bridge) | 5 min | Portfolio health and Theme Factory runs | | Vision people sweep (bridge) | 30 min | One read per Team plus the directory, ten Teams per push | | Project discovery, run collection | 30 min | Local scans only; the result rides the next snapshot |

Vision Land's operator console lists these under Sync status per paired computer, as this companion reports them. The intervals are built in; a newer package changes them, a running companion does not upgrade itself.