Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.voight.xyz/llms.txt

Use this file to discover all available pages before exploring further.

Voight works with any agent stack — coding assistants, autonomous frameworks, and custom runtimes. Pick the install path that fits yours; the dashboard, the privacy model, and the API are identical on every path.

​
Step 1 — Install

​
A · Coding agent (Claude Code, Cursor, Codex…)

A wizard writes the right hooks and env into your IDE’s config. No code changes. 
npx -y @voightxyz/sdk setup
Verified today for Claude Code. Cursor and Codex targets are scaffolded — see SDK targets.

​
B · Autonomous agent (ElizaOS, Solana Agent Kit, custom)

Install the SDK as a library and call voight.log() from your agent code. 
npm install @voightxyz/sdk

import { voight } from '@voightxyz/sdk'

voight.init({ key: process.env.VOIGHT_KEY })

await voight.log({
  kind: 'decision',
  agentId: 'my-trading-bot',
  input: 'should I rebalance?',
})
Full reference in Library mode.

​
C · Any language over HTTP

For Python, Go, Rust, or anything that speaks JSON — POST events directly, no SDK required. 
curl https://voight-production.up.railway.app/v1/events \
  -H "authorization: Bearer $VOIGHT_KEY" \
  -H "content-type: application/json" \
  -d '{ "kind": "decision", "agentId": "my-agent", "input": "hello" }'
Full schema in the HTTP API reference.

​
Step 2 — Pick your privacy level

For path A the wizard prompts you. For paths B and C you pass it on voight.init({ privacy: 'standard' }) or per-request.
  • Minimal — metadata only. No prompts, responses, file paths, cwd, or git context leave your machine.
  • Standard ★ — full content with local PII scrubbing. Credentials and personal info redacted before transmission.
  • Full — everything captured as-is.
The privacy overview breaks down what each level keeps, scrubs, or drops, field by field.

​
Step 3 — Generate your API key

When the wizard asks for a key — or before you initialize the library / send your first request — open voight.xyz/dashboard/settings and click + Generate key. Copy the vk_... secret. You’ll only see it once, so save it to a password manager. Paste it into the wizard, or set it as VOIGHT_KEY in your runtime environment.

​
Step 4 — You’re connected

Open voight.xyz/dashboard. Within seconds you should see:
  • A new agent in the Agents list (auto-named from your install path, renameable)
  • Events streaming in Overview and Audit log
  • Token counts, cost USD, and model tags on each event
  • A per-event privacy chip (MIN / STD / FULL) confirming which level captured it

​
Non-TTY install for path A

If stdin isn’t an interactive TTY (running the wizard from inside a chat agent, CI, or any non-interactive shell), setup runs in 3-step progressive mode instead of an interactive prompt: 
# See the menu
npx -y @voightxyz/sdk setup

# Pick a privacy level
npx -y @voightxyz/sdk setup --privacy=2

# Paste your key
npx -y @voightxyz/sdk setup --privacy=2 --key=vk_YOUR_KEY
Each step prints instructions and exits cleanly. The chain reads naturally for both humans and AI agents.

​
Troubleshooting

  1. Confirm the SDK version: npx -y @voightxyz/sdk@latest --version (should be 0.4.2 or higher).
  2. For path A — check your IDE’s settings file (~/.claude/settings.json for Claude Code): env.VOIGHT_KEY should be set and hooks should contain entries calling npx -y @voightxyz/sdk hook. Restart your IDE afterwards — hooks are read on startup.
  3. For path B / C — confirm your code is actually calling voight.log() or POSTing, and that VOIGHT_KEY is set in the runtime environment.
  4. Check the dashboard’s Audit log for the most recent events — they should appear within ~2 seconds of being sent.
Force the latest with an explicit version:
npx -y @voightxyz/sdk@0.4.2 setup
Or clear the npx cache:
rm -rf ~/.npm/_npx
You’re probably on Minimal mode, which strips content fields by design. Re-run setup with Standard or Full:
npx -y @voightxyz/sdk setup --privacy=standard
Or for path B / C, pass the level on voight.init({ privacy: 'standard' }).
Some coding agents flag unfamiliar packages installed with -y for safety. The two-line copy block in your dashboard onboarding includes a framing line (“Set up Voight observability here:”) that gives the agent the intent it needs to skip the warning.

​
Next steps

Understand the data model

What an event, trace, and session are. How Voight groups them.

Pick the right privacy level

The 3-level model in detail, with examples of what each captures.

Library mode

Deep dive on path B — for autonomous agents you build yourself.

HTTP API

Deep dive on path C — for runtimes that don’t use npm.