@mifune/agro 0.10.0 → 0.12.0

package/README.md

@@ -1,9 +1,9 @@
 # @mifune/agro
 
-The **AGRO CLI** (`agro`) — create an [Open Harness](https://agro.mifune.dev)
+The **AGRO CLI** (`agro`) — create an [AGRO](https://agro.mifune.dev)
 Docker sandbox for coding agents and drive its lifecycle from the command line.
 
-Open Harness is a portable harness for running coding agents (Claude Code, Codex, Pi,
+AGRO is a portable harness for running coding agents (Claude Code, Codex, Pi,
 and others) in an isolated Docker sandbox, with the agent's identity, skills, and crons
 versioned in git. This package is the standalone `agro` CLI that creates sandboxes and
 manages their lifecycle.
@@ -57,19 +57,21 @@ same files.
 Create a sandbox from any directory — no project checkout needed:
 
 ```bash
-agro sandbox install docker   # wizard, then boot; writes ~/.oh/sandboxes/<name>/
-agro sandbox list             # name, runtime, status, repo
+agro sandbox install docker   # wizard, then boot; writes ~/.agro/sandboxes/<name>/
+agro sandbox list             # name, runtime, status, checkout
 agro shell <name>             # open a zsh shell in the running container
 ```
 
-To bind one of your own checkouts into the sandbox, equip it and pass `--repo`:
+To bind one of your own checkouts into the sandbox, equip it and pass `--checkout`:
 
 ```bash
 cd your-project
 oh update                                       # vendor .agro/ + crons/ — and nothing else (compatibility window)
-agro sandbox install docker --repo "$PWD" --name your-project
+agro sandbox install docker --checkout "$PWD" --name your-project
 ```
 
+`--repo` remains a supported alias for `--checkout`.
+
 Add an agent harness or a tool at any point — this needs no rebuild. The verb is
 the only door; nothing installs at boot:
 
@@ -96,8 +98,8 @@ with `OH_EXECUTION_TARGET=local` or `OH_EXECUTION_TARGET=docker-compose`.
 
 | Command | What it does |
 |---|---|
-| `agro sandbox install <runtime>` | Create a sandbox: run the wizard, write the registry entry under `${OH_HOME:-~/.oh}/sandboxes/<name>/`, materialise the compose files and wrapper into it, and boot the container. Flags: `--name`, `--repo <dir>`, `--yes`, `--image[=<ref>]`, `--no-build`, `--print-argv`. `docker` is provisionable; `microsandbox` is planned and refuses with a pointer at the runtime RFC. |
-| `agro sandbox list [--json]` | List the registry entries with name, runtime, container status, and bound repo. |
+| `agro sandbox install <runtime>` | Create a sandbox: run the wizard, write the registry entry under `${AGRO_HOME:-~/.agro}/sandboxes/<name>/`, materialise the compose files and wrapper into it, and boot the container. Flags: `--name`, `--checkout <dir>` (alias `--repo <dir>`), `--home-mount <dir>`, `--yes`, `--image[=<ref>]`, `--no-build`, `--print-argv`. `docker` is provisionable; `microsandbox` is planned and refuses with a pointer at the runtime RFC. |
+| `agro sandbox list [--json]` | List the registry entries with name, runtime, container status, and bound checkout. |
 | `agro shell [name]` | Open a `zsh` shell in the running sandbox container. |
 | `agro stop [name]` | Stop the sandbox, preserving volumes. |
 | `agro restart [name]` | Restart the sandbox service. |
@@ -115,7 +117,6 @@ with `OH_EXECUTION_TARGET=local` or `OH_EXECUTION_TARGET=docker-compose`.
 | `agro harness <list\|install\|status>` | Install and inspect agent CLI harnesses. `install` is the only door: it probes the running sandbox, installs into the persistent home volume, and reports. It reads and writes no `agro.json` field, and needs no rebuild. |
 | `agro tool <list\|install\|status>` | Install and inspect sandbox tooling that is not an agent CLI. `herdr`, `cloudflared`, `agent-browser`, `microsandbox`, and `tailscale` are `installable`; `gh` and the Docker CLI are `baked-in` and cannot be installed. Nothing installs at boot. A large download is confirmed first, and `--yes` accepts it. |
 | `agro gateway <args…>` | Manage a messaging client session (Slack bridge for `pi`/`hermes`). |
-| `agro cloud <args…>` | Configure credentials and manage OpenHarness Cloud SSH keys and nodes. |
 | `agro --version` | Print the CLI version. |
 | `agro --help` | Show help; every subcommand also accepts `--help`. |
 
@@ -138,39 +139,12 @@ writes nothing else and never prompts. `agro update` rejects those flags and poi
 `oh update`. `oh update` prefers the payload bundled into the CLI itself; with `--from-remote`
 (or no payload at all) it shallow-clones the public OpenHarness repo into a temp dir and
 removes it after the run (`--ref <ref>` pins it). Root `docs/` remains project-owned and is
-not part of that payload. Catalog and help output therefore links to the Open Harness source
+not part of that payload. Catalog and help output therefore links to the AGRO source
 documentation instead of a path inside the equipped project.
 
 The CLI writes no scaffold. It creates no `AGENTS.md`, no provider configuration, and no
 `.gitignore` line beyond the `.env` line `agro secret set` adds inside a git checkout.
 
-## OpenHarness Cloud
-
-`agro cloud` is an Apache-2.0 licensed client that talks to a proprietary hosted service.
-Configure the Cloud API once, then use `agro cloud` instead of hand-writing authenticated HTTP
-requests:
-
-```bash
-agro cloud config  # securely prompts for the current provisioner key
-agro cloud ssh-keys create --name laptop --public-key-file ~/.ssh/openharness_node.pub
-agro cloud nodes create --name demo --ssh-key-id <ssh-key-id>
-agro cloud nodes watch <node-id>
-```
-
-Both settings are repository-local. `agro cloud config` writes the API base URL to `cloud.apiUrl`
-in the tracked `agro.json` and, until OpenHarness Cloud issues user API tokens, stores the
-user-provided provisioner key as `OH_CLOUD_PROVISION_KEY` in the gitignored root `.env`
-(mode `0600`). The key is never printed; `agro cloud config show` redacts it. Nothing is written
-under `$HOME`.
-
-`OH_CLOUD_API_URL` and `OH_CLOUD_PROVISION_KEY` (`OH_PROVISION_KEY` and `PROVISION_KEY` are
-still accepted) provide non-persistent overrides for automation. Because the settings live in
-the repository, `agro cloud` runs inside an OpenHarness-equipped repo; outside one, pass
-`--api-url` and `--provision-key`. On the first `agro cloud` run in a repo, a legacy
-`~/.config/openharness/cloud.json` is migrated into these two homes and then reported as no
-longer read — it is left on disk for you to delete. Run `agro cloud --help` for the complete
-SSH-key and node lifecycle command set.
-
 ## Documentation
 
 - **Docs:** https://agro.mifune.dev