Operator reference

Run and maintain Iranti.

The operator surface covers health checks, instance lifecycle, project binding, key management, and conflict resolution. Most of the time you will not need it — but when something breaks, this is where you fix it.

Repair workflow

When a project cannot talk to Iranti, run these in order:

$
iranti doctor
iranti status
iranti configure instance local --interactive
iranti configure project . --interactive

Health

$
iranti doctor

Validate the database, API key, and LLM provider. Run this first when something feels wrong.

$
iranti status

Show known instances and project bindings for the current machine and directory.

$
iranti doctor --debug

Print extra diagnostics, structured error details, and stack traces.

Lifecycle

$
iranti run --instance local

Start the Iranti API server for a named instance.

$
iranti upgrade --check

Check whether a newer version is available without applying it.

$
iranti upgrade --yes

Apply all available upgrades. Add --restart --instance local to restart immediately.

Interactive shell

$
iranti chat

Open an interactive chat shell for querying and writing memory directly. Useful for sanity-checking state.

Project binding

$
iranti project init . --instance local

Bind the current directory to a running instance. Writes .env.iranti.

$
iranti configure project . --interactive

Update an existing binding interactively.

$
iranti project unbind .

Remove the binding. Add --keep-integrations to leave MCP and Claude scaffolding in place.

API keys

$
iranti auth create-key --instance local --key-id my_app --owner "My App" --scopes "kb:read,kb:write,memory:read,memory:write"

Create a scoped key for an agent or service.

$
iranti auth list-keys --instance local

List all active keys for an instance.

$
iranti auth revoke-key --instance local --key-id my_app

Revoke a key by ID.

Operating rules

$
iranti list-rules

Show all user-defined operating rules with their triggers, enforcement level, and scope.

$
iranti delete-rule <rule-id>

Remove a rule by entity ID.

Conflict resolution

$
iranti resolve

Walk through escalated conflicts the Librarian could not auto-resolve.

Uninstall

$
iranti uninstall --dry-run

Preview what would be removed without touching anything.

$
iranti uninstall --all --yes

Remove runtime, project bindings, MCP entries, and Claude scaffolding. Use --dry-run first.

Inside iranti chat

The interactive shell exposes slash commands for direct memory operations. Useful for checking state without writing code.

/memory

Show current memory summary

/search <query>

Hybrid search across all facts

/history <entity> <key>

Full version history for a fact

/write <key> <value>

Write a fact directly

/relate <from> <to> <type>

Create a relationship

/related <entity>

List related entities

/confidence <entity> <key> <n>

Update confidence score

/resolve

Walk through escalated conflicts