nightCrawl

The user's digital twin browser — a persistent headless Chromium that inherits their real Arc/Chrome cookies and browses the web as them. Use nightcrawl whenever the user wants to interact with a website as themselves: "go to", "open this site", "navigate to", "read this page", "search on [site]", "log in to", "download from", "scrape", "crawl", "what does this page say", "fill out this form", "check if this site blocks us", or any task involving a URL or web page. Also use it to LOG THE USER IN as themselves — "log me in", "sign in as me", "use my saved password", "get me into my account" — via `autofill-login`, which submits the browser's OWN saved password through Engine R (the real Arc browser) without ever reading it; and to FILL FORMS — "fill in my details/email/address", "autofill this signup" — via `autofill` from a local non-secret profile vault. Cookies already imported from the user's real browser persist across sessions in ~/.nightcrawl/ — never re-import. Stealth (CDP patches, UA, optional CloakB

Load task PRD and project specs before writing code. Use before implementation, refactors, or harness changes.

Post-bug-fix retrospective — classify root cause, identify prevention, write the lesson into specs. Use after fixing any non-trivial bug, when a task involving 'fix', 'bug', 'debug', or 'diagnose' is being finished, or when the user asks 'what went wrong', 'why did this break', 'root cause', or 'lessons learned'. Also use when the lifecycle hook reminds you to run break-loop.

Verify recent Codex harness or project changes against task requirements, specs, tests, and rollout checks.

Resume the current Codex harness task. Use when returning to a task, when the user asks what state we are in, or when the conversation has shifted between planning, implementation, and checking.

Finish a Codex harness task after implementation, checking, spec updates, and rollout verification.

Analyze a codebase and generate durable spec files from existing patterns, architecture, and conventions. Use to initialize or refresh .codex/spec/ for a project. Also use when the lifecycle hook reminds you to run spec-bootstrap, when a project has empty or template-only specs, when the user says 'generate specs', 'initialize specs', 'bootstrap specs', or 'make the codebase context durable'.

Update durable project specs/docs when implementation changes architecture, workflow, conventions, or recurring lessons.

Brainstorm engine — interview the user about a plan/design, auto-write PRD and context manifests as answers resolve. Use when the user wants to stress-test a plan, brainstorm a feature, design architecture, or says 'grill me', 'brainstorm', 'let's plan', 'design this', or describes a new feature they want to build. Also use when the workflow phase is 'planning' and a task is active.