Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@appautomaton/automaton) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

Automaton

Portable, stage-gated agentic-AI harness for Claude Code, Codex, and OpenCode.

An AI coding agent framework that gives LLM-powered development tools structured workflows for long-running tasks. Automaton installs markdown skills, lightweight startup integrations, and durable .agent/ state into a project so agent work survives context window limits, session restarts, and multi-step changes that would otherwise lose coherence.

Acknowledgement 致谢

🖤🤍💛 Thanks to Linux Do (https://linux.do/) for their vibrant AI development community. 🖤🤍💛

Why Use It

Keep project truth, current work, and handoff state outside the chat window.
Move larger changes through explicit frame, plan, execute, and verify stages.
Use the same workflow across Claude Code, Codex, and OpenCode.

Install

Run from the project you want to equip:

npx @appautomaton/automaton install --codex
npx @appautomaton/automaton install --claude
npx @appautomaton/automaton install --opencode

Install all supported host surfaces:

npx @appautomaton/automaton install --all

The target root is optional and defaults to the current directory. To install into another project, pass its path as the final argument.

What It Adds

.agent/ durable project state, steering, work artifacts, and runtime files
host skills under .codex/skills, .claude/skills, or .opencode/skills
host hooks/plugins for context injection

Automaton is copy-based: installed skills are local plain markdown files that are refreshed from source on reinstall and can be inspected in the target project.

Workflow

office-hours -> frame -> product review -> plan -> engineering review -> execute -> verify -> verified

Most changes start at auto-frame, move through auto-plan, then continue with auto-execute and auto-verify. A full verification pass closes the change as verified (terminal). Use auto-onboard when project steering is missing or stale, auto-office-hours when the objective is still too broad, and auto-resume to re-enter existing work from a fresh session at any point.

Useful Commands

Run package commands through npx @appautomaton/automaton:

npx @appautomaton/automaton status
npx @appautomaton/automaton validate
npx @appautomaton/automaton install --uninstall --codex

Contributor Docs

Contributor-only design and runtime notes live in the repository docs/ directory; they are not included in the npm package payload.

License

MIT

@appautomaton/automaton