@agentify/cli 0.1.0 → 0.2.0

package/README.md

@@ -1,282 +1,69 @@
-# Agentify CLI
+# @agentify/cli
 
-Agentify CLI helps you capture agent sessions, publish privacy-reviewed replays, ask for help with evidence, and run reusable workflows from your terminal.
+The Agentify CLI pairs a local workspace with Agentify Chat.
 
-## Install
-
-Run without installing:
-
-```bash
-npx -y @agentify/cli --help
-```
+Agentify Chat lets you send encrypted prompts from `chat.agentify.sh` to a coding agent running on your own computer. The server routes ciphertext only; the workspace key and runner tokens stay local.
 
-Install globally:
+## Install
 
 ```bash
 npm install -g @agentify/cli
 agentify --help
 ```
 
-Requirements:
-
-- Node.js 18 or newer for the npm launcher.
-- macOS, Linux, or Windows on x64 or arm64.
-- An Agentify account for publishing, attaching, and private account actions.
-
-## Sign In
-
-Use browser/device login for the normal flow:
-
-```bash
-agentify auth login
-agentify auth whoami
-agentify auth status
-```
-
-For scripted environments, you can use password login:
-
-```bash
-agentify auth login --method password --email you@example.com
-```
-
-Sign out locally:
-
-```bash
-agentify auth logout
-```
-
-## Ask For Help
-
-Create an Ask post from the terminal:
-
-```bash
-agentify ask new \
-  --title "Why is this browser automation test flaky?" \
-  --summary "The Playwright run fails after login only in CI."
-```
-
-Attach a transcript or log file as evidence:
-
-```bash
-agentify ask new \
-  --title "Debug slow agent run" \
-  --summary "The run stalls after dependency install." \
-  --chat-file ./session.log
-```
-
-Attach an already published replay:
-
-```bash
-agentify ask new \
-  --title "What caused this agent to loop?" \
-  --summary "Replay shows the loop and the failed edits." \
-  --replay replay-pzsp7soo
-```
-
-Browse and answer questions:
-
-```bash
-agentify ask list
-agentify ask list --mode recent --page 2
-agentify ask open q_123
-agentify ask answer q_123 --text "The failure is caused by a stale selector."
-```
-
-Useful Ask flags:
-
-- `--json` prints machine-readable output.
-- `--chat-log` attaches inline transcript text.
-- `--chat-file` attaches a transcript file.
-- `--chat-retention 7d` sets transcript retention.
-- `--space @public` chooses the posting space.
-
-## Publish Replays
-
-A replay is a shareable record of an agent or terminal session. The CLI can publish plain text, JSON, JSONL, or Codex session logs.
-
-Preview before publishing:
-
-```bash
-agentify replay preview --file ./session.jsonl
-agentify replay preview --latest-codex-session
-```
-
-Publish a replay:
-
-```bash
-agentify replay publish \
-  --file ./session.jsonl \
-  --title "Debugging a flaky CI failure"
-```
-
-Publish the latest Codex session:
-
-```bash
-agentify replay publish \
-  --latest-codex-session \
-  --title "Refactoring the replay player"
-```
-
-Keep a replay private or set an expiry:
-
-```bash
-agentify replay publish --file ./session.jsonl --private
-agentify replay publish --file ./session.jsonl --expires-in 7d
-```
-
-Attach a replay to an Ask question:
-
-```bash
-agentify replay attach replay-pzsp7soo q_123
-agentify replay publish --file ./session.jsonl --attach-request q_123
-```
-
-Record a wrapped terminal command:
-
-```bash
-agentify replay record --name "install failure" -- npm install
-agentify replay stop
-```
-
-Manage replays:
-
-```bash
-agentify replay list
-agentify replay open replay-pzsp7soo
-```
-
-Replay input sources:
-
-- `--file ./path` reads a transcript, JSON, or JSONL file.
-- `--text "..."` uses inline text.
-- `--stdin` reads piped input.
-- `--codex-session <id-or-path>` selects a Codex session.
-- `--latest-codex-session` selects the newest matching Codex session.
-- `--workspace ./repo` scopes Codex session lookup to a workspace.
-
-## Workflows
-
-Workflows are reusable local automation specs that can be verified, run, published, and pulled.
-
-Verify and run a local workflow:
-
-```bash
-agentify workflows verify --in ./workflow.json
-agentify workflows run ./workflow.json --set target=release
-```
-
-Browse and open workflows:
+The hosted setup flow at `https://chat.agentify.sh` can also install the CLI for a single user account without a global npm install.
 
-```bash
-agentify workflows list
-agentify workflows list --q browser --tag playwright
-agentify workflows open wf_123
-```
-
-Publish and download:
-
-```bash
-agentify workflows publish wf_123
-agentify workflows pull wf_123 --out ./workflow.tgz
-```
-
-Useful workflow flags:
-
-- `--json` prints machine-readable output.
-- `--cwd ./repo` runs a local workflow from a specific directory.
-- `--out ./runs` controls local workflow output.
-- `--include-drafts` includes drafts in workflow listings.
-
-## Health Checks
-
-Run doctor when setup, auth, or local replay state looks wrong:
+## Main Commands
 
 ```bash
+agentify chat pair --pairing-ticket <ticket> --workspace "$PWD" --label "$(basename "$PWD")"
+agentify chat daemon --runner codex
+agentify chat daemon --runner claude
+agentify chat daemon --runner gemini
 agentify doctor
-agentify doctor --json
 ```
 
-Doctor checks local config, auth state, API reachability, workspace state, active replay recordings, and available Codex sessions.
-
-## API And Automation
+`agentify chat pair` registers this machine as the local decrypting device for a workspace. `agentify chat daemon` polls for encrypted jobs and runs the selected local CLI in the configured workspace with V1 review-mode guardrails.
 
-Most commands accept:
+## Security Model
 
-- `--api-base https://api.agentify.sh/api/v1`
-- `--api-key <key>`
-- `--bearer-token <token>`
-- `--json`
+- Prompt and result payloads are encrypted before they leave the browser or local runner.
+- The server does not receive the workspace encryption key.
+- Poll tokens stay on the local machine.
+- Browser enqueue tokens and approval state stay in the browser.
+- V1 runners are review-mode only. Patch/apply/full-control modes are not enabled.
+- Local logs stay on the paired computer.
 
-Prefer stored auth from `agentify auth login` for local use. Use API keys or bearer tokens only in automation.
+## Experimental Commands
 
-## Privacy Notes
+The CLI also includes experimental surfaces for `ask`, `replay`, and `workflows`. They are available for advanced users, but Agentify Chat is the primary launch surface.
 
-Replays and Ask evidence can contain secrets. Preview and redact logs before publishing.
+## Local Development
 
-The replay publisher includes redaction checks for common high-risk patterns such as private keys, bearer tokens, API keys, npm tokens, GitHub tokens, Slack tokens, Stripe keys, JWTs, emails, URL query strings, and local home paths.
-
-## Troubleshooting
-
-If the command is installed but cannot find a platform binary, reinstall the package:
-
-```bash
-npm install -g @agentify/cli
-```
-
-If auth looks stale:
+To exercise the npm wrapper against a local Rust build:
 
 ```bash
-agentify auth logout
-agentify auth login
-agentify doctor
-```
-
-If a replay input fails, first preview it:
-
-```bash
-agentify replay preview --file ./session.jsonl
-```
-
-For command-specific options:
-
-```bash
-agentify <command> --help
-agentify replay publish --help
-agentify ask new --help
+AGENTIFY_CLI_BIN=/absolute/path/to/agentify node ./bin/agentify.js --help
 ```
 
-## Development
-
-Build and test the Rust CLI:
+To stage the current Rust binary into the npm package layout:
 
 ```bash
-cargo test
 cargo build --release
+npm run stage:bin -- --force
+node ./bin/agentify.js --help
 ```
 
-Run npm wrapper tests:
-
-```bash
-npm run test:npm
-```
-
-Exercise the npm launcher against a local Rust build:
-
-```bash
-AGENTIFY_CLI_BIN=/absolute/path/to/agentify node ./bin/agentify.js --help
-```
-
-Stage a local binary into the package layout:
+To verify release readiness:
 
 ```bash
-npm run stage:bin -- --force
-npm run verify:package
+npm run release:check
 ```
 
-Run local release checks while not all platform binaries are staged:
+During local incubation, when only some platform binaries are staged, use:
 
 ```bash
 npm run release:check -- --allow-missing-targets
 ```
 
-Strict publish checks require all supported platform binaries and run automatically through `prepublishOnly`.
+Do not publish until the packed artifact has been inspected and the release check passes.

package/package.json

@@ -1,9 +1,16 @@
 {
   "name": "@agentify/cli",
-  "version": "0.1.0",
-  "description": "Agentify CLI for Ask, Replay, workflows, and local agent session tooling",
-  "license": "MIT",
+  "version": "0.2.0",
+  "description": "Agentify CLI for secure local Agentify Chat runners",
+  "license": "MPL-2.0",
   "homepage": "https://agentify.sh",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/agentify-sh/cli.git"
+  },
+  "bugs": {
+    "url": "https://github.com/agentify-sh/cli/issues"
+  },
   "type": "commonjs",
   "bin": {
     "agentify": "bin/agentify.js"
@@ -34,8 +41,8 @@
   "keywords": [
     "agentify",
     "cli",
-    "agentic",
-    "replay",
-    "workflows"
+    "chat",
+    "local-first",
+    "coding-agent"
   ]
 }