AIOS Project System

Overview

Use this skill as the repository map for aios. It explains where state lives, how automation actually runs, and which files are authoritative before you edit tasks, workflows, or browser operations.

Core Topology

• CLAUDE.md: project-level behavior contract and architecture overview.
• memory/skills/*.json: operational playbooks for recurring tasks (not deterministic executors).
• memory/specs/*.json: safety constraints and limits.
• tasks/{pending,done,failed}: task queue and outcomes.
• scripts/run-browser-use-mcp.sh: default browser MCP launcher (bridges to ai-browser-book/mcp-browser-use).
• mcp-server/: legacy Playwright MCP implementation retained for compatibility workflows.
• docs/plans/: design, implementation, and postmortem documents.

Runtime Truths (Do Not Skip)

• MCP server label may still be puppeteer-stealth, but default runtime now routes to browser-use tools (chrome.launch_cdp, browser.connect_cdp, page.*) via scripts/run-browser-use-mcp.sh.
• mcp-server/src/index.ts still exposes Playwright browser_* tools, but treat that path as legacy/compatibility.
• If both puppeteer-stealth and chrome-devtools are available, use puppeteer-stealth for normal browser automation and reserve chrome-devtools for debugging only.
• For interactive runs, explicitly prefer chrome.launch_cdp { port: 9222, user_data_dir: '~/.chrome-cdp-profile' }, then browser.connect_cdp.