Carry the work across every world. The engineer sets the course.
Status: product foundation · Source-available (fair-code) · No release yet
Amaru is an engineering execution platform. In Andean tradition the amaru is the serpent that crosses the worlds and carries water between them; here it carries work between humans, AI agents, tools and environments, and the engineer decides where it flows.
Amaru coordinates humans, AI agents, tools, knowledge, workflows and execution environments across the software development lifecycle. Humans set intent, scope, quality criteria and approval boundaries; agents carry out delegated work inside explicit policies; workflows coordinate multi-step activities; and every result, decision and piece of evidence stays observable and auditable.
Amaru does not replace Git, GitHub, issue trackers, IDEs, CI or specialized engineering tools. It integrates with them and orchestrates work across them.
Status: M3 Platform core in progress; no release yet. M2 contracts and the generated SDK are merged, and parts of the Platform core have recorded local evidence. The Platform remains incomplete; Web, Desktop, Cloud and Self-hosted delivery are planned. Follow the GitHub Project, roadmap and issue evidence for completion and validation limits. There is no ready-to-install product release.
Work delegated to AI agents and tools is scattered across terminals, chats, CI logs and scripts. There is rarely one record of what an agent was asked, with which context, what it changed and who accepted it; permissions and approvals differ per tool; multi-step work is stitched together by hand and lost on a crash; specialized tools are stuck on specific machines; and workflows get written against a single agent vendor. Details: PRD §2.
- Human authority: consequential actions require explicit, recorded human authorization (ADR-0006).
- Evidence over claims: results carry the context, inputs, outputs and approvals that produced them.
- Orchestrate, don't replace: your repositories and tools stay authoritative.
- Vendor-neutral: workflows reference capabilities, not vendors.
- Incremental: infrastructure is added when evidence demands it, not in advance.
Intended users: individual engineers working with AI agents first; team leads, self-host operators and plugin authors later (PRD §3).
| Surface | What it is | Status |
|---|---|---|
| Amaru Platform | The deployable system: domain model, API contracts, policies, execution coordination. | Partially implemented; M3 incomplete, with local evidence and outstanding integration/validation |
| Workers | Run Steps in local or remote Execution Environments (Linux, Windows workstations, sandboxes). | Embedded interface partially implemented (M3); remote execution planned (M5) |
| Amaru Web | Browser client served by the Platform; the Local MVP client. | Proposed (M4) |
| Plugins | TypeScript UI and logic, services, Worker and local adapters, with declared permissions. | Proposed (M6) |
| Amaru Self-hosted | The Platform, operated by you. | Proposed (M7) |
| Amaru Desktop | Native client wrapping the same UI (Tauri v2 thin Rust host, ADR-0018). | Proposed (M8) |
| Amaru Cloud | The Platform, operated as a managed service. | Proposed (M9) |
Manage execution in the GitHub Project using the delivery workflow. Milestones (no dates) are in the master roadmap; features in the feature catalog.
Cloud and Self-hosted are deployments of the same Platform, not separate products (ADR-0002). Clients never own execution state (ADR-0003).
flowchart LR
eng([Engineer]) --> clients[Clients<br/>Web · Desktop · CLI]
clients -->|versioned public API| platform[Amaru Platform<br/>state · policy · approvals · events]
platform --> workers[Workers<br/>local or remote environments]
workers --> providers[Providers<br/>agent CLIs · tools · remote APIs]
providers --> project[(Your repositories<br/>and tools)]
Full proposal and what is not built: docs/architecture/ARCHITECTURE.md.
.agents/skills/ canonical agent Skills (.claude/skills/ holds symlinks to them)
docs/product/ PRD, feature catalog, non-functional requirements, glossary
docs/architecture/ architecture hub and views, roadmap, work packages, decisions (adr/), open questions
docs/engineering/ conventions, repository layout, validation, agent instructions
docs/security/ security model
tools/doccheck/ offline documentation checker (Go, standard library only)
packages/contracts/ versioned API, event, Provider and Worker contracts (OpenAPI, JSON Schema, Protobuf) shared fixtures and the route-drift guard
packages/sdk/ TypeScript SDK generated from the OpenAPI contract, with an event-stream client (cursor resume)
services/platform/ partial Platform core; M3 acceptance and validation remain in progress
Application, service and package directories are added only when they have real content (repository layout).
Requirements: Git and Go 1.27 or newer (Go 1.21+ with the default GOTOOLCHAIN=auto downloads 1.27 automatically). On Windows, clone with symlinks enabled: git clone -c core.symlinks=true … (why).
make check # gofmt, go vet, unit tests and documentation checks
make docs-check # documentation checks onlySee validation for the full tool requirements and checks, including contract/SDK and Platform tests. Start reading at the PRD, then the architecture and the roadmap.
- Product: PRD · Feature catalog · NFRs · Glossary
- Architecture: Architecture · Roadmap · Work Packages · Decisions · Open questions · all documents
- Engineering: Conventions · Validation · Agent instructions
- Security: Security model
The project is at the foundation stage and is not yet accepting external contributions. The CLA text (CLA.md) and signing process (CONTRIBUTING) are in place; the root LICENSE is in effect since 2026-10-26 (ADR-0026). For maintainers and agents: follow AGENTS.md and the conventions, record significant decisions as ADRs, and run make check before proposing a change.
The root LICENSE is the Amaru Community License 1.0 (fair-code, source-available; Rights Holder LUDERS TECNOLOGIA LTDA), in effect since 2026-10-26 as decided in ADR-0026. It permits personal use, Internal Use (including commercial organizations), self-hosting and non-commercial forks; resale, commercial sublicensing and Hosted Services require a separate written commercial license. External contributions require the CLA. Contracts and SDKs will be Apache-2.0, with a LICENSE file added in each package when it is created; until then they carry no separate license. Read the license text for the exact terms. Amaru is not OSI-approved open source and should not be described as such.