@arbidocs/cli 0.3.41 → 0.3.43

package/CHANGELOG.md

@@ -1,12 +1,20 @@
 # Changelog
 
-## v0.3.41
+## v0.3.43
 
-[compare changes](https://github.com/arbicity/ARBI-frontend/compare/v0.3.40...HEAD)
+[compare changes](https://github.com/arbicity/ARBI-frontend/compare/v0.3.42...HEAD)
 
 ### 🏡 Chore
 
-- Release v0.3.40 [skip ci] ([5e404545](https://github.com/arbicity/ARBI-frontend/commit/5e404545))
+- Release v0.3.42 [skip ci] ([0b0830d0](https://github.com/arbicity/ARBI-frontend/commit/0b0830d0))
+
+## v0.3.40
+
+[compare changes](https://github.com/arbicity/ARBI-frontend/compare/v0.3.39...HEAD)
+
+### 🚀 Enhancements
+
+- **cli:** Add --json to list commands + agent-aware not-logged-in hint ([#629](https://github.com/arbicity/ARBI-frontend/pull/629))
 
 ## v0.3.39
 

package/SKILL.md

@@ -11,9 +11,10 @@ ARBI is an enterprise document intelligence platform with E2E encrypted communic
    - Scripted (humans with API access): `arbi register -e <email> -p <password> --verification-code <code>`
    - Scripted (AI agents / bots, requires `SUPPORT_API_KEY`): `arbi agent-create --email agent-<name>@<domain> --workspace-name "<name>"`
      - The email MUST start with `agent-`. This path creates the account, logs in, and selects the new workspace in one call.
+   - Scripted (non-interactive register for humans with API access): `arbi register --non-interactive --json --email <email> --password "<password>"` — emits a single JSON line; `--json` is also supported on `login`, `logout`, and `status`.
 4. Verify: `arbi status` (add `--json` for machine-readable output)
 
-For multiple agents on the same machine, set `ARBI_ID=<name>` (or `ARBI_CONFIG_DIR=<path>`) to isolate config in `~/.arbi/<name>/`.
+For multiple identities on the same machine, set `ARBI_ID=<name>` (or `ARBI_CONFIG_DIR=<path>`) to isolate config in `~/.arbi/<name>/`. Each identity has its own `config.json` and `credentials.json`, so commands like `ARBI_ID=alice arbi dm list` and `ARBI_ID=bob arbi dm send …` operate independently.
 
 ## When to Use
 
@@ -32,12 +33,12 @@ Documents, conversations, and tags are scoped per workspace. An active workspace
 Common moves:
 
 - List: `arbi workspaces` (human) · `arbi workspaces --json` (script) · `arbi workspaces --ids`
-- Active workspace ID: `arbi workspace current` (prints the ID, empty string if none)
-- Pick/switch: `arbi workspace select <id>` — clears the chat session; uploaded docs in other workspaces are unaffected
-- Create: `arbi workspace create "My WS"` — does NOT auto-select, follow with `workspace select`
-- Rename / edit: `arbi workspace update '{"name":"New Name"}'`
-- Delete: `arbi workspace delete [id]` — deletes immediately (no confirmation prompt); if you delete the active workspace, the selection is cleared
-- Share: `arbi workspace add-user <email> -r <role>` where role is `owner|collaborator|guest` (may be plan-limited)
+- Active workspace ID: `arbi workspace current` (prints the ID, empty string if none) · `arbi workspace current --json` for full details
+- Pick/switch: `arbi workspace select <id-or-name>` — accepts a workspace ID or a unique (case-insensitive) name; clears the chat session; uploaded docs in other workspaces are unaffected
+- Create: `arbi workspace create "My WS"` — does NOT auto-select. Use `--select` to create + select in one go, `--json` for scripts
+- Rename / edit: `arbi workspace update '{"name":"New Name"}'` (add `--json` for scripts)
+- Delete: `arbi workspace delete [id-or-name]` — prompts for confirmation in interactive shells. In non-TTY shells you **must** pass `-y/--yes` (otherwise the command refuses to delete). If you delete the active workspace, the selection is cleared. `--json` outputs `{id, deleted}`
+- Share: `arbi workspace add-user <email> -r <role>` where role is `owner|collaborator|guest` (plan-limited — free tier has 0 collaborator slots)
 - List members: `arbi workspace users [--json]`
 - Remove member: `arbi workspace remove-user <user-id>`
 - Copy docs between workspaces: `arbi workspace copy <target-ws-id> <doc-id>...` — only copies documents that have finished indexing; partial/failed copies exit non-zero
@@ -45,8 +46,10 @@ Common moves:
 Scripting notes:
 
 - The table output of `arbi workspaces` is NOT reliably parseable (names contain spaces, status cells may contain glyphs). Use `--json` or `--ids`.
+- Switch-by-name in one line: `arbi workspace select "My WS"`. If the name is ambiguous, the CLI lists the matches and exits non-zero — use the ID.
 - Sessions persist between CLI invocations via the config file (default `~/.arbi/`, override with `ARBI_CONFIG_DIR`).
 - Per-agent isolation: run agents with their own `ARBI_CONFIG_DIR=<path>` (or `ARBI_ID=<name>`) to avoid stomping each other's active workspace.
+- Agent accounts typically have 0 collaborator slots, so `workspace add-user` errors with "Collaborator limit reached" unless the plan is upgraded.
 
 ## Tips
 
@@ -54,7 +57,7 @@ Scripting notes:
 - If a command fails with "fetch failed", check connectivity with `arbi health`.
 - Use `arbi ask -n` to start a fresh conversation (forget prior context).
 - Use `arbi ask -v` for verbose output showing retrieval steps.
-- Use `arbi status --json` and `arbi workspace current` to read CLI state from scripts.
+- Use `arbi status --json` and `arbi workspace current` to read CLI state from scripts. `arbi workspaces --json` lists every workspace with `is_selected` marked.
 
 ## For Automations / AI Agents
 
@@ -92,3 +95,14 @@ All document list/search/meta commands support machine-readable output. Prefer `
 - **Doctags** (tag↔doc link): `arbi doctags create <tag-id> <doc-id...>` / `arbi doctags delete <tag-id> <doc-id...>`.
 - **Retrieve only**: `arbi find <query> --json` returns raw retrieval results without running the LLM.
 - **Exit codes**: 0 on success (including clean skips), 1 on error. Errors print to stderr.
+
+## Multi-user / Messaging (for agents)
+
+All list commands that summarize people or state support `--json`:
+`arbi contacts list --json`, `arbi dm list --json`, `arbi dm send <to> <msg> --json`, `arbi agent list --json`, `arbi session list --json`, `arbi task list --json`.
+
+- **Contacts are one-way**: `arbi contacts add <email>` only populates *your* contact list; the other party is NOT notified and does not see you in their contacts. Before replying to a DM from a new sender you must add them with `arbi contacts add`.
+- **DM E2E proof**: `arbi dm send … --json` and `arbi dm list --json` emit an `encrypted_in_transit: true` flag per message. The SDK seals every DM with the recipient's curve25519 public key before the network call — this flag makes that invariant visible without reading SDK code.
+- **Listen side-effects**: `arbi listen --agent claude` writes `~/.claude/commands/arbi/SKILL.md` and sets a `defaultAgent` in the CLI config. Run it only on a machine you control.
+- **Persistent agents**: `arbi agent create --name <n> -w <ws-id>` creates a child identity the parent can delegate to (printed email+password). Share workspace IDs via `-w` rather than the interactive picker when running non-interactively.
+- **Agent-create errors**: `agent-create` rejects non-`agent-*` emails with a clear message. If you see "No verification record found" the account probably already exists — use `arbi login` instead.