No description
- Python 92.5%
- JavaScript 5.9%
- CSS 0.8%
- Just 0.3%
- HTML 0.2%
- Other 0.2%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
- check_run.py, test_cure_loop.py: the cure-loop suite runs once on a push, its four planted faults only when the change touches the cure-loop folder or its suite, or when every file is judged; the duplicate plain step goes (52 steps). A typical push's full run fell from 1,098 seconds to 603 on the build home's machine. - shopify/run.py, mcp/index.js: `query --pages <N|all>` follows the one connection's endCursor into one joined answer; every read waits 2 s, then 4 s, when Shopify throttles it, and a write is never retried; the read server passes pages through. - doctor.py, onboarding.md: the doctor checks mise's shims folder is first on the saved PATH, so a bare `just` works in every shell an agent opens, and `just setup` puts it there on Windows; a Windows host line names the onboarding guide's new "Working on a Windows host". - docwright: `just doc shot` captures a rendering, a phone view, the whole page or a diagram as a PNG a session can read, through the one headless launch printing now shares, a fresh profile each run. Field reports from an instance, 2026-10-24. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01K8NthYxoZ2iNYCLdHfc2AU |
||
| .devcontainer | ||
| .github/workflows | ||
| aos | ||
| .gitattributes | ||
| .gitignore | ||
| .mise.toml | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| justfile | ||
| README.md | ||
os-template
The clean origin of every agent-os instance: a repo-native, model-agnostic, rule-based operating system for coding agents. Machinery and the default constitution only - zero accounts, zero secrets, zero company data by construction (the cleanliness meta-rule proves it on every check run).
- New here: read
aos/onboarding.md- the layered guided install, from a bare machine (Linux, macOS or Windows) to a born, green instance: what you will need and when, every command with its expected output, a fast path for operators who know their way - Layout: the operating-system layer lives under
aos/(machinery, rules, registry); the repository root carries only the connective set (continuous integration, devcontainer, toolchain, compiled agent context) - everything a company adds on top sits in its own folders besideaos/, which the template will never claim, with its own recipes ininstance.justand its own tool pins inmise.toml(aos/system/lib/layout.py says what the template owns) - Bare machine: run
aos/bootstrap.sh(Linux/macOS) oraos/bootstrap.ps1(Windows) with the instance's git address - it installs git + mise, clones, installs the pinned toolchain, and runsjust setup, whose doctor walks everything else (Docker, secrets) to a green check run. mise does not putjuston PATH: everyjust <recipe>here meansmise exec -- just <recipe> - Reference execution tier - optional for a green check run; everything
above runs natively in your own shell (PowerShell on Windows). The
devcontainer (.devcontainer/) is one Linux container definition for
any host system. When: any time after
just setup, oncejust doctorshows the docker row OK (Windows: Windows Subsystem for Linux, then Docker Desktop - the doctor names both install commands). How:aos/onboarding.mdstep 8 owns both routes with their exact commands - the terminal route (default) and the Visual Studio Code Dev Containers route (restating one route here had already drifted from that step, fix-campaign 2026-09-01) just brain-map scan <name>thenview: a read-only map of what this repository contains, browsed as a page from disk (nothing scans automatically, nothing spends)just doctorany time: checks every prerequisite in order and names the exact cure for your system for anything still missing- Birth an instance:
mise exec -- python -m aos.system.template.init_instance --company <slug> --operator <your-personal-slug> --out <dir> - Update an instance from here:
just os-update(inside the instance) - updates land as a checked three-way diff from the instance's recorded template version; a red check run rolls back, and instances may decline - The whole check run:
just check- the step list's one fact home is aos/system/eval/check_run.py (fixtures, compiled-context verification, registry, gateway, cleanliness, self-checks)