@apralabs/apra-fleet 0.2.2

package/LICENSE

@@ -0,0 +1,182 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship made available under
+      the License, as indicated by a copyright notice that is included in
+      or attached to the work (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean, as submitted to the Licensor for inclusion
+      in the Work by the copyright owner or by an individual or Legal Entity
+      authorized to submit on behalf of the copyright owner. For the purposes
+      of this definition, "submitted" means any form of electronic, verbal,
+      or written communication sent to the Licensor or its representatives,
+      including but not limited to communication on electronic mailing lists,
+      source code control systems, and issue tracking systems that are managed
+      by, or on behalf of, the Licensor for the purpose of discussing and
+      improving the Work, but excluding communication that is conspicuously
+      marked or otherwise designated in writing by the copyright owner as
+      "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any Legal Entity on behalf of
+      whom a Contribution has been received by the Licensor and subsequently
+      incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by the combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a cross-claim
+      or counterclaim in a lawsuit) alleging that the Work or any Contribution
+      incorporated within the Work constitutes direct or contributory patent
+      infringement, then any patent licenses granted to You under this License
+      for that Work shall terminate as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or Derivative
+          Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, You must include a readable copy of the
+          attribution notices contained within such NOTICE file, in
+          at least one of the following places: within a NOTICE text
+          file distributed as part of the Derivative Works; within
+          the Source form or documentation, if provided along with the
+          Derivative Works; or, within a display generated by the
+          Derivative Works, if and wherever such third-party notices
+          normally appear. The contents of the NOTICE file are for
+          informational purposes only and do not modify the License.
+          You may add Your own attribution notices within Derivative
+          Works that You distribute, alongside or as an addendum to
+          the NOTICE text from the Work, provided that such additional
+          attribution notices cannot be construed as modifying the License.
+
+      You may add Your own license statement for Your modifications and
+      may provide additional grant of rights to use, copy, modify, merge,
+      publish, distribute, sublicense, and/or sell copies of the
+      Contribution, either on its own or as part of the Work.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or reproducing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or exemplary damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or all other
+      commercial damages or losses), even if such Contributor has been
+      advised of the possibility of such damages.
+
+   9. Accepting Warranty or Liability. While redistributing the Work or
+      Derivative Works thereof, You may choose to offer, and charge a fee
+      for, acceptance of support, warranty, indemnity, or other liability
+      obligations and/or rights consistent with this License. However, in
+      accepting such obligations, You may offer such obligations only on
+      Your own behalf and on Your sole responsibility, not on behalf of
+      any other Contributor, and only if You agree to indemnify, defend,
+      and hold each Contributor harmless for any liability incurred by,
+      or claims asserted against, such Contributor by reason of your
+      accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   Copyright 2026 Apra Labs
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,324 @@
+# Apra Fleet
+
+[![CI](https://github.com/Apra-Labs/apra-fleet/actions/workflows/ci.yml/badge.svg)](https://github.com/Apra-Labs/apra-fleet/actions/workflows/ci.yml)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
+[![Platform](https://img.shields.io/badge/platform-macOS%20%7C%20Linux%20%7C%20Windows-lightgrey.svg)](https://github.com/Apra-Labs/apra-fleet/releases)
+[![MCP](https://img.shields.io/badge/MCP-compatible-8A2BE2.svg)](https://modelcontextprotocol.io)
+
+### One goal. A team of AI agents that plan, execute, and review each other's work, and run across every machine you own.
+
+Apra Fleet is an open-source **MCP server** that turns AI agents (Claude
+Code, Antigravity, Codex, Copilot, Gemini) into a coordinated team instead of a lone
+assistant. Any job that needs more than one agent -- software sprints,
+customer-support triage, cost and operations-efficiency analysis,
+infrastructure surveys -- becomes a fleet you direct in plain conversation.
+Need more horsepower? Fleet reaches across every machine on your network
+over SSH -- no dashboards, no orchestration YAML.
+
+**The agents need not share a vendor.** A Claude agent and an Antigravity agent can
+work the same sprint -- one writes, the other reviews -- so a different model,
+with different blind spots, checks every change. Cross-provider collaboration is
+a built-in quality mechanism, not an afterthought.
+
+> A *member* is one working folder plus one LLM CLI -- local or remote.
+> A fleet is however many of those you register, working in concert.
+
+### Watch a real run (3 min)
+
+[![Apra Fleet -- a doer-reviewer sprint, start to finish](https://img.youtube.com/vi/SGdHvIkSbY8/hqdefault.jpg)](https://youtu.be/SGdHvIkSbY8)
+
+Two agents ship a feature end to end: one plans and writes, the other reviews,
+findings loop back, and a clean diff lands -- driven by the **PM skill**. That is
+*one* of the workflows Fleet makes possible; the rest are below.
+
+---
+
+## See it in one example
+
+```
+/pm add 2 local members at c:\projects cloned from <git-url> -- a developer and a reviewer -- and pair them
+/pm init project_icarus
+/pm plan ./feature.md
+/pm start the implementation sprint
+/pm status
+```
+
+You describe the goal, approve the plan once, and Fleet runs the doer-reviewer loop to a reviewed PR.
+
+## Quick start
+
+### Option A -- npm (all platforms, requires Node.js 22+)
+
+```bash
+npm install -g @apralabs/apra-fleet
+apra-fleet install              # Claude Code (default)
+apra-fleet install --llm agy    # Google Antigravity CLI
+apra-fleet install --llm gemini # Gemini CLI
+apra-fleet install --llm codex  # OpenAI Codex CLI
+```
+
+Run `install` once per provider you want to support. After install, load the
+server in Claude Code using `/mcp`, or restart your CLI for other providers.
+
+### Option B -- standalone binary (no Node.js required)
+
+Copy-paste the one-liner for your platform:
+
+**macOS (Apple Silicon)**
+```bash
+curl -fsSL https://github.com/Apra-Labs/apra-fleet/releases/latest/download/apra-fleet-installer-darwin-arm64 -o apra-fleet-installer && chmod +x apra-fleet-installer && ./apra-fleet-installer install
+```
+
+**Linux (x64)**
+```bash
+curl -fsSL https://github.com/Apra-Labs/apra-fleet/releases/latest/download/apra-fleet-installer-linux-x64 -o apra-fleet-installer && chmod +x apra-fleet-installer && ./apra-fleet-installer install
+```
+
+**Windows (x64)** -- run in PowerShell:
+```powershell
+Invoke-WebRequest -Uri https://github.com/Apra-Labs/apra-fleet/releases/latest/download/apra-fleet-installer-win-x64.exe -OutFile apra-fleet-installer.exe; .\apra-fleet-installer.exe install
+```
+
+> Installing for **Antigravity**, Codex, Copilot, or Gemini instead of Claude? Add the
+> `--llm` flag -- see
+> [Install for other providers](docs/install.md#install-for-other-providers-antigravity-codex-copilot-gemini).
+
+Then load it in your favorite LLM CLI (claude, agy, gemini, ...) using `/mcp`.
+
+Now register your first members:
+
+> "Register a local member called `doer`. Register another called `reviewer`.
+> Pair them."
+
+Verify it worked:
+
+> "Show me fleet status."
+
+You should see both members listed with status online or idle.
+
+Add remote machines whenever you are ready:
+
+> "Register 192.168.1.10 as `build-server`. Username akhil, work folder
+> `/home/akhil/projects/myapp`."
+
+Fleet securely collects the machine's password out-of-band -- you type it into a
+separate terminal, never the chat -- uses it once to set up SSH key-based auth,
+then forgets it. Every connection after that is key-based.
+
+Intel Mac users: build from source -- see [Development](#development).
+Install details (what it writes, the `--skill` flag, uninstall) are in
+[docs/install.md](docs/install.md).
+
+**Staying current is one command.** `apra-fleet update` checks GitHub for the
+latest release and installs it in place -- or tells you that you are already up
+to date. See [keeping Fleet updated](docs/features/update.md).
+
+## How it works
+
+```mermaid
+sequenceDiagram
+    actor You
+    participant PM as PM (orchestrator)
+    participant Doer
+    participant Reviewer
+    You->>PM: "Add a note sharing system, have it reviewed"
+    loop Plan: revise until the reviewer signs off
+        PM->>Doer: draft / revise the plan
+        Doer-->>PM: plan
+        PM->>Reviewer: review the plan
+        Reviewer-->>PM: rejected with fixes, or signed off
+    end
+    PM-->>You: plan for approval
+    You-->>PM: approved
+    loop Build: revise until the review is clean
+        PM->>Doer: execute / fix the task
+        Doer->>Doer: write code, commit, reach checkpoint
+        PM->>Reviewer: review the changes
+        Reviewer-->>PM: findings, or signed off
+    end
+    PM-->>You: reviewed code + PR
+```
+
+A sprint runs in two reviewed phases: the **plan** is drafted, reviewed, and
+approved by you before any code is written; then the **build** is executed and
+every phase of development is reviewed against all the project documents
+(requirements, plan, design, etc.). The PM orchestrator talks to members through Fleet's MCP
+tools; Fleet carries the work to each member -- locally as a child process, or
+remotely over SSH. Agents sync state through git (`PLAN.md`, `progress.json`,
+`feedback.md`), so progress survives restarts.
+
+## What you can build on top
+
+Fleet is a coordination layer. The **PM skill** is its reference workflow library
+and ships today; the rest are recipes you assemble with the same tools.
+
+| Workflow | What it does | Status |
+|----------|--------------|--------|
+| **Doer / Reviewer** | Two agents pair: one writes, one reviews against a quality bar. | Ships (PM skill) |
+| **Plan / execute / verify** | Break work into steps, approve the plan, agents pause at checkpoints. | Ships (PM skill) |
+| **Pipeline** | Agent A extracts, B transforms, C ships -- handoff by file. | Recipe |
+| **Specialist routing** | Route Python work to a py-agent, Rust to a rust-agent. | Recipe |
+| **Parallel exploration** | Three agents try three approaches; you merge the winner. | Recipe |
+| **Cross-machine** | Build on Linux, test on Windows, deploy from a Mac. | Recipe |
+
+To write your own skill, see [docs/writing-skills.md](docs/writing-skills.md).
+
+## Use cases
+
+- Run your test suite on a Linux box while you develop on macOS.
+- Have one agent build the frontend, another the backend, a third running tests
+  -- all in parallel.
+- Use a beefy cloud VM for compilation while coding from your laptop.
+- Spin up isolated workspaces on one machine without them stepping on each other.
+- Customer-support triage: agents classify, draft replies, and escalate
+  tickets in parallel.
+- Cost and operations-efficiency analysis: fan out data gathering across
+  sources, consolidate findings.
+- Infrastructure surveys, log triage, and patch fan-out across many
+  machines.
+
+## Cost
+
+Multi-agent tooling raises one question first: does coordinating several agents
+burn more tokens? In practice Fleet works to keep usage down -- and the core
+idea is the one Fleet was built on: **match the model to the task.**
+
+A plan is a list of tasks of widely varying difficulty. Running every one of
+them on a single premium model is the waste. Instead, Fleet assigns each task a
+model tier commensurate with its complexity:
+
+- **cheap** -- boilerplate, status checks, running tests, deploys
+- **standard** -- routine feature work, code, configuration
+- **premium** -- planning, review, hard architectural reasoning
+
+Only the work that genuinely needs a frontier model gets one; everything else
+runs on a lighter, cheaper tier. Two more mechanisms compound the savings:
+
+- **Shell over prompts** -- routine steps run through `execute_command` as plain
+  shell commands, which cost zero LLM tokens.
+- **Smart sessions** -- Fleet decides whether to resume an existing session
+  (reusing cached context) or start fresh, rather than re-sending history.
+
+**Token spend is measured, not estimated.** Fleet records token usage per
+member and per role -- PM, doer, reviewer -- so a team can see and analyze
+where their spend actually goes. Fleet's end-to-end CI suite exercises this
+in full: a complete reviewed sprint -- discover issues, plan, doer-reviewer
+loop, PR raised with green CI -- emits a per-role token breakdown (in one
+such run: PM ~6K, doer ~191K, reviewer ~19K, ~215K total). Those toy-repo
+figures are not a benchmark -- they show the measurement method works end
+to end. The point is the instrument: Fleet makes token cost something you
+can attribute and reason about, not guess at.
+
+Setup is a one-time cost; the recurring cost is the work itself. See the
+[FAQ](docs/FAQ.md) for the full breakdown.
+
+## Compare to alternatives
+
+| Tool | Overlap | Where Fleet differs |
+|------|---------|---------------------|
+| Single-agent coding assistants | AI writes code | Fleet adds a second agent that reviews before you do. |
+| CI self-hosted runners | Runs work on other machines | Fleet is conversational and stateful, not pipeline-triggered. |
+| SkyPilot / dstack | Multi-machine compute | Fleet coordinates *agents and their context*, not just jobs. |
+| Google A2A | Agent-to-agent messaging | Fleet is an opinionated workflow layer, not just a transport. |
+
+When *not* to use Fleet: a one-off single-file change needs no second agent.
+
+## Mix providers in one fleet
+
+Every member runs its own LLM backend, and they collaborate across vendors. Put
+a Claude doer with an Antigravity reviewer, or the reverse - the reviewer's model
+disagrees with the doer's by construction, so it catches issues a same-model
+review would wave through. Mix by role:
+
+| Role | Recommended | Why |
+|------|-------------|-----|
+| PM (orchestrator) | Claude Code or Antigravity (agy) | Both plan and orchestrate well - both support planning, background tasks, and premium models (e.g., Opus / premium-tier). |
+| Doer | Any provider | Sonnet, Antigravity, Codex, Copilot, Gemini - mix freely. |
+| Reviewer | Premium-tier models | Catches subtle issues smaller models miss. |
+
+A fleet that has run in production:
+
+```
+pm-1      Opus 4.7        orchestrator
+doer-1    Sonnet 4.6      feature work
+doer-2    Antigravity     large-context tasks
+reviewer  Opus 4.7        final review
+```
+
+Provider strengths, role recommendations, and gotchas:
+[docs/provider-guide.md](docs/provider-guide.md).
+
+## The PM skill
+
+The **PM skill** is Fleet's reference workflow for **software development**
+-- it ships today, fully built out. It is one skill on a general
+substrate: the same primitives -- members, tasks, git/SSH transport,
+doer-reviewer pairing -- coordinate agents for support triage, cost
+analysis, ops surveys, or any multi-agent job. PM is the worked example;
+the platform is the point.
+
+The Project Manager skill is installed by default and drives structured,
+multi-step work: planning with your approval, doer-reviewer loops, verification
+checkpoints, and git-synced progress. Task state persists across sessions via
+[**Beads**](docs/beads.md), the bundled open-source issue tracker (`bd` CLI, installed alongside Fleet) -- run `bd ready` any time to see
+what is in flight.
+
+| Command | Does |
+|---------|------|
+| `/pm init <project>` | Initialize a project folder and templates. |
+| `/pm pair <member> <member>` | Pair a doer with a reviewer. |
+| `/pm plan <requirement>` | Draft a plan for your approval. |
+| `/pm start <member>` | Begin execution; dispatches doer with plan and task harness. |
+| `/pm status <member>` | Check in-flight tasks, progress, and git log. |
+| `/pm resume <member>` | Resume after a verification checkpoint. |
+| `/pm deploy <member>` | Execute the project deployment runbook. |
+| `/pm recover <project>` | Re-orient after a PM restart; reads in-flight tasks and member state. |
+| `/pm cleanup <project>` | Finish the sprint, close tasks, and raise a PR. |
+| `/pm backlog` | Query and manage deferred items via Beads. |
+| `/pm tasks` | Show the current sprint task tree. |
+
+See [skills/pm/SKILL.md](skills/pm/SKILL.md) for the full command reference.
+
+Want to build your own skill on top of Fleet? See [docs/writing-skills.md](docs/writing-skills.md).
+
+## Documentation
+
+| Topic | Link |
+|-------|------|
+| Codebase wiki (architecture, internals, AI Q&A) | [DeepWiki](https://deepwiki.com/Apra-Labs/apra-fleet) |
+| Install, uninstall, the `--llm` flag | [docs/install.md](docs/install.md) |
+| Choosing a provider | [docs/provider-guide.md](docs/provider-guide.md) |
+| FAQ | [docs/FAQ.md](docs/FAQ.md) |
+| Troubleshooting | [docs/troubleshooting.md](docs/troubleshooting.md) |
+| Keeping Fleet updated (`apra-fleet update`) | [docs/features/update.md](docs/features/update.md) |
+| Secure credentials and passwords | [docs/features/oob-auth.md](docs/features/oob-auth.md) |
+| Enabling SSH on a remote machine (if it does not have it yet) | [docs/ssh-setup.md](docs/ssh-setup.md) |
+| Git authentication | [docs/design-git-auth.md](docs/design-git-auth.md) |
+| Cloud compute | [docs/cloud-compute.md](docs/cloud-compute.md) |
+| Architecture | [docs/architecture.md](docs/architecture.md) |
+
+## Community
+
+- Questions and ideas: [GitHub Discussions](https://github.com/Apra-Labs/apra-fleet/discussions)
+- Releases: [GitHub Releases](https://github.com/Apra-Labs/apra-fleet/releases)
+- Issues: [GitHub Issues](https://github.com/Apra-Labs/apra-fleet/issues)
+- What is planned next: [ROADMAP.md](ROADMAP.md)
+
+If Apra Fleet helped you ship faster with better quality, please
+[star the repo](https://github.com/Apra-Labs/apra-fleet) -- it helps others
+find it.
+
+## Development
+
+Build from source (also the path for Intel Macs):
+
+```bash
+git clone https://github.com/Apra-Labs/apra-fleet && cd apra-fleet
+npm install && npm run build && npm test
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) to contribute.
+
+## License
+
+Apache 2.0 -- see [LICENSE](LICENSE).

package/dist/cli/auth.d.ts

@@ -0,0 +1,2 @@
+export declare function runAuth(args: string[]): Promise<void>;
+//# sourceMappingURL=auth.d.ts.map

package/dist/cli/auth.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"auth.d.ts","sourceRoot":"","sources":["../../src/cli/auth.ts"],"names":[],"mappings":"AAcA,wBAAsB,OAAO,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,OAAO,CAAC,IAAI,CAAC,CAY3D"}