@autonomos/cli
v0.6.0
Published
CLI tool for the Autonomos Agent Protocol
Downloads
620
Maintainers
Readme
@autonomos/cli
A command-line interface for managing the Autonomos Agent Protocol.
Installation
# Locally in your project
pnpm add -D @autonomos/cli
# Or globally
pnpm add -g @autonomos/cliCommands
init
Initialize the Agent Protocol in the current directory.
autonomos init
autonomos init --dry-runupdate
Update the project's Protocol to the latest version embedded in the CLI.
autonomos updatestatus
Show project status and a summary of tasks from TASKS.md.
For projects using the protocol version bundled with the CLI, status also verifies
that PROTOCOL.md and installed harness workflows match their canonical published
content. Drift is reported with the affected paths and can be repaired with
autonomos update; artifacts from other protocol versions are reported as
unverifiable rather than incorrectly judged against the current release.
autonomos statusagents
List all AGENT.md files in the project.
autonomos agents # Search from current directory
autonomos agents --all # Search from project rootversion
Show current CLI and Protocol versions.
autonomos --versionHow it works
The CLI manages the .autonomos/ directory in your project, which contains:
manifest.json: Protocol metadata and versioning.PROTOCOL.md: The read-only specification for the declared protocol version.TASKS.md: Your project's task registry.ISSUES.md: An optional intake registry, created on first use when a problem or proposal needs triage.worklogs/: Directory for session logs.
It also creates a root AGENT.md file if it doesn't exist, which serves as the primary context for AI agents.
Optional project-owned .autonomos/specs/ and .autonomos/decisions/ directories
are first-use artifacts, not empty directories created by init. update
refreshes managed protocol files and harness workflows while preserving those
directories, AGENT.md, TASKS.md, ISSUES.md, worklogs, and user documentation.
For semantic migration of an existing project's scattered knowledge, use the
installed /adopt workflow: it proposes a source-to-destination map, waits for
user approval, writes draft/proposed records, and leaves historical records
unchanged. Follow it with /reconcile.
License
MIT
