Skip to main content

Continuity and agent runs

Aegis is not just a fresh chat on every launch. The current wake path already uses durable profile, clone, session, memory, planning, and context state.

What persists now​

  • the active clone and its session lineage
  • durable memory records and corrections
  • durable goals and next-step decisions
  • recovered context summaries when you re-enter wake
  • agent-run checkpoints when a multi-step tool loop needs to resume later

What long-horizon execution means today​

Aegis can already checkpoint multi-step tool loops instead of dropping them when one foreground turn ends. If a run has to stop because of loop budget or lack of progress, the runtime can resume from a durable checkpoint on a later turn.

That makes long-horizon work materially stronger than a single prompt loop, but it is still not a background autonomous worker that runs for hours on its own without an active surface.

How to inspect continuity​

Use the normal conversation first. When you need to inspect the durable state, stay inside wake and use:

  • /status
  • /profile
  • /activity
  • /memory
  • /procedure
  • /audit

These slash commands are the public inspection surfaces for the current continuity line.