@socialseal/cli 0.1.1 → 0.1.3

package/CHANGELOG.md

@@ -2,6 +2,14 @@
 
 ## Unreleased
 
+## 0.1.3 - 2026-03-19
+- Republish the current CLI release line after the successful `0.1.2` npm publish, keeping the internal and OSS package versions aligned.
+
+## 0.1.2 - 2026-03-18
+- Add `search-journey-run` async CLI ergonomics: `--async` starts the backend async mode, polling is on by default, and `--no-poll` returns the initial `runId` immediately.
+- Add `--poll-interval <ms>` for async `search-journey-run` status polling.
+- Treat terminal async `search-journey-run` failures as non-zero CLI exits instead of silent `200` JSON output.
+
 ## 0.1.1 - 2026-03-13
 - Document public base URL and CLI error output.
 - Add request timeouts, verbose error output, and OSS-safe tool discovery behavior.

package/README.md

@@ -9,6 +9,7 @@
 Environment variables:
 - `SOCIALSEAL_API_KEY`
 - `SOCIALSEAL_API_BASE` (default `https://api.socialseal.co`)
+- `SOCIALSEAL_WORKSPACE_ID` (optional workspace override; takes precedence over config)
 - `SOCIALSEAL_TIMEOUT_MS` (optional request timeout override)
 - `SOCIALSEAL_AGENT_IDLE_TIMEOUT_MS` (optional agent WebSocket inactivity timeout override; default 300000)
 
@@ -19,14 +20,22 @@ Optional config file:
 {
   "apiKey": "ss_cli_...",
   "apiBase": "https://api.socialseal.co",
+  "workspaceId": "00000000-0000-0000-0000-000000000000",
   "timeoutMs": 30000,
   "agentIdleTimeoutMs": 300000
 }
 ```
 
 ## Commands
+- Workspace discovery/defaults:
+  - `socialseal workspace list`
+  - `socialseal workspace current`
+  - `socialseal workspace use <workspace-id|slug|exact-name>`
+  - `socialseal workspace clear`
+
 - Agent (non-interactive, streaming):
   - `socialseal agent run --message "..." --api-base https://api.socialseal.co --api-key <key> [--workspace-id <uuid>]`
+  - `socialseal agent run --message "..." --continue <token>`
   - `socialseal agent run --message "..." --timeout 60000`
   - `socialseal agent run --message "..." --idle-timeout 300000 --verbose`
 
@@ -37,6 +46,8 @@ Optional config file:
 - Tools (direct edge function call):
   - `socialseal tools call --function <tool> --body @payload.json --api-base https://api.socialseal.co --api-key <key>`
   - `socialseal tools call --function <tool> --body @payload.json --json`
+  - `socialseal tools call --function search-journey-run --body @payload.json --async --workspace-id <uuid>`
+  - `socialseal tools call --function search-journey-run --body @payload.json --async --no-poll --workspace-id <uuid>`
 
 - Data exports (provisional):
   - `socialseal data export-tracking --group-id 123 --time-period 30d --out out.csv`
@@ -46,12 +57,28 @@ Optional config file:
 - `export-report` and `export_tracking_data` are provisional until CLI export specs are finalized.
 - `tools list` ships a stable built-in registry of supported direct-call function targets. It is not live backend enumeration.
 - `--timeout <ms>` controls HTTP request timeouts. Agent runs default to a 5-minute WebSocket inactivity timeout unless you set `--idle-timeout <ms>` (or the matching env/config value).
+- `search-journey-run` supports CLI-managed async polling: `--async` starts backend async mode, polling is on by default, `--no-poll` returns the initial `runId`, and `--poll-interval <ms>` controls the status polling cadence.
+- `socialseal agent run` now defaults to a fresh conversation. The CLI prints a continuation token to `stderr`; pass it back with `--continue <token>` to resume the same agent conversation explicitly.
+- Effective workspace precedence is: `--workspace-id` → `SOCIALSEAL_WORKSPACE_ID` → config `workspaceId` → backend personal-workspace fallback.
+- `socialseal workspace use ...` writes a local default workspace into `~/.config/socialseal/config.json`, which the CLI reuses for `agent`, `tools`, and `data` commands.
+- `socialseal workspace list` discovers the workspaces accessible to the current CLI key and marks the active/suggested default.
+- If a scoped CLI key cannot safely infer a workspace, `agent run` now fails closed and tells you to set `--workspace-id` or configure a local default first.
 
 ## Errors and exit codes
 - Exit codes: `2` (usage), `3` (auth), `4` (not found), `5` (server), `1` (unknown)
 - Add `--json` to `tools call` or `data` commands to emit machine-readable errors.
 - Add `--verbose` to print error details plus agent session/tool progress diagnostics.
 
+## Troubleshooting
+- `SUPABASE_ANON_KEY not configured`
+  - This comes from the CLI gateway, not the local CLI install.
+  - The deployed gateway is missing its `SUPABASE_ANON_KEY` secret, so `/cli/tools/*` cannot proxy to Supabase Edge Functions.
+  - Fix on the server side with `wrangler secret put SUPABASE_ANON_KEY --env <staging|production>` for the gateway Worker, then re-run a `socialseal tools call ...` smoke test.
+- `AI_UNSUPPORTED_LOCATION` or `The live agent is unavailable in this region right now.`
+  - This is raised when the upstream Gemini API rejects the worker egress location.
+  - The agent worker currently uses Google Gemini directly from Cloudflare Workers; there is no SocialSeal-side region allowlist in the CLI.
+  - If this reproduces from a supported Google AI region, treat it as an infrastructure/runtime issue. Practical workarounds are to run the agent from a worker placement/egress region that Google accepts, or switch the agent runtime to Vertex AI for server-side calls.
+
 ## Smoke Test (manual)
 1. `SOCIALSEAL_API_KEY=... socialseal agent run --message "ping"`
 2. `SOCIALSEAL_API_KEY=... socialseal tools call --function <tool> --body @payload.json`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@socialseal/cli",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "private": false,
   "type": "module",
   "description": "SocialSeal CLI (non-interactive)",