v1.3.0 — Execution Flow and Audit Log

Autopilot v1.3.0 — Execution Flow & Audit Log

Two major improvements to how Autopilot executes tasks and tracks what it does.

Execution Flow Protocol (replaces Startup Protocol)

The agent no longer pauses between steps to ask what to do next.

Two flows based on task complexity:

• Flow A (simple tasks) — single service, Level 1-2: executes immediately with brief status updates, no plan or confirmation needed.
• Flow B (complex tasks) — multi-step, multi-service, or Level 3+: presents a numbered plan, waits for one "proceed", then executes everything end-to-end without stopping.

The No-Pause Rule: once execution starts, the agent runs to completion. It only stops for genuine blockers (2FA codes, missing credentials, Level 4+ decisions). "What should I do next?" is no longer in its vocabulary.

Project-Local Execution Log

Every action is now automatically logged to:

{your-project}/.autopilot/log.md

Each session gets a timestamped table with:

• Step number
• Timestamp
• What was done
• Decision level (L1-L5)
• Which service
• Result (done, failed + error)

This is especially useful for Level 1-2 actions that execute silently — the log is the only record of what happened. If something breaks at step 5 of 8, open the log to see exactly what steps 1-4 did, where step 5 failed, and what steps 6-8 were supposed to do.

The log lives in the project directory, not in the autopilot system files. Each project has its own audit trail. Credential values are never logged.

Example

User: Set up Supabase and deploy to Vercel
Autopilot: Here's the plan:
  1. Install Supabase CLI
  2. Create project
  3. Run migrations
  4. Deploy to Vercel preview
  5. Set environment variables
Proceed?

User: yes

Autopilot: [1/5] Supabase CLI already installed
           [2/5] Creating project... done
           [3/5] Running migrations... 2 tables created
           [4/5] Deploying... https://myapp.vercel.app
           [5/5] Env vars set

Done. All actions logged to .autopilot/log.md