IASDocs
ias.dev

Start

First run

Check your provider, run a local read-only goal, steer it while it runs, and resume it later.

This walkthrough assumes the requirements are in place and ias is on your PATH.

1. Prepare your provider

Install Claude Code or Codex and sign in through that provider's own CLI. Local IAS runs use that login and do not require ias login, a Lucentive One account or the hosted IAS API.

2. Check what can run

Terminal
ias doctor

doctor starts the local IAS service if it is not running yet and reports the state directory, scheduler, provider capabilities and reasons a provider is unavailable. A successful probe does not verify login, remaining quota or whether the provider accepts a requested model.

3. Run a read-only goal

Open a Git repository you know well. Give IAS one quoted goal and the files it should read.

Terminal
cd ~/code/invoice-service
ias run 'Find stale setup steps.' \
  --executor claude \
  --source docs/onboarding.md

The run is read-only. IAS passes the goal, the repository's AGENTS.md when there is one, and the selected sources to Claude Code, which works inside containment. Progress streams to your terminal. Each --source path is relative to the repository root and can be repeated.

4. Steer while it runs

While the run is in your terminal, type a correction and press Enter:

Text
Skip deployment. Focus on local setup.

The run takes the correction and keeps going on the same record. Press Ctrl-C to stop the current turn.

5. Inspect your runs

Terminal
ias status
ias status <run-id>

Without an ID, status lists your recent local runs. With an ID, it shows that run and its outcome. One-owned runs require their owning identity; without a valid session, their IDs and details stay hidden and the listing shows only their count.

6. Resume later

Terminal
ias resume <run-id> \
  --message 'Draft the fixes.'

resume continues the same intent on the same durable record, and --message adds a correction before it continues. A completed run continues only with a correction.

7. Let IAS write

Writing is an explicit choice, and it starts from a clean, committed checkout:

Terminal
ias run 'Fix the stale steps.' \
  --executor codex \
  --mode workspace-write \
  --source docs/onboarding.md

With --mode workspace-write, IAS creates an isolated worktree for the run at workspaces/<run-id> in your state directory, on the branch ias/<run-id>. Your own checkout stays as it was, and you review the changes in that worktree before merging anything.

8. Reconcile uncertain effects

If a run stops while the outcome of an effect is uncertain, IAS keeps that effect open instead of guessing. Check the actual state yourself, then record what you found:

Terminal
ias reconcile <run-id> \
  --note 'Checked: guide is updated.'

The note is required. An unresolved effect can also block admission of new work, including when it belongs to another identity. Its owner must reconcile it. After reconciliation, inspect the run and use ias resume when it is eligible to continue.

Connected work

ias login is for One-owned and connected work. It needs both browser sign-in and admission by the hosted IAS API. If that API is unavailable, login cannot save a session; local work remains available. Signing in does not adopt your local runs into One. See commands for connected operations.

Next