Skip to main content

First run

After install, stay in the CLI. The supported operator path is short on purpose.

1. Run aegis init​

aegis init

init is the first-use setup flow. It:

  • binds the local operator identity
  • lets you choose a personality preset
  • lets you seed the first durable goal for the first clone
  • captures the active provider configuration before real conversations begin
  • prepares the first named clone so wake is the next step
  • surfaces the IM handoff so aegis gateway setup --default-clone-id <clone> can open the IM chooser without leaving the main operator flow

2. Confirm readiness​

aegis status

Use status before the first durable conversation. It tells you whether the active provider, profile, and local runtime posture are ready.

3. Enter wake​

aegis wake

wake is the main conversational surface. That is where continuity stays primary.

Optional: wire IM​

aegis gateway setup --default-clone-id demo

Use this entrypoint when you want to choose an IM surface, configure it, or inspect IM readiness without remembering the provider-specific setup commands.

4. Create another clone only when you need one​

aegis clone nova --initial-goal "Own the release readiness thread"

Each clone is an isolated Aegis individual with its own continuity line, personality drift, and future wake history.

Optional: non-interactive setup​

For scripted setup, you can preconfigure the provider path directly:

aegis init --non-interactive \
  --initial-goal "Carry the first durable thread" \
  --provider-id openai-compatible \
  --base-url https://api.example.com/v1 \
  --strong-model example/model \
  --api-key sk-live-...

The important rule is that the profile stores the provider shape and the local encrypted secret reference, not the secret value itself.