Relationships
↑ child of #622#711 serve-auth: --server support for remaining remote-capable commands (phase 2)
Opened by stack72 · 6/19/2026· Shipped 6/30/2026
Parent
Follow-up to #710 (phase 1 --server support) under #662 (serve authentication & authorization).
Summary
After #710 ships, the core data/model/workflow/vault/audit/summary/report commands work remotely. This issue tracks the remaining commands that should also support `--server` — everything an admin or user would need to check, query, or manage on a running server without SSH.
Commands to add `--server` support
Data operations
- `swamp data search` — search data across models
- `swamp data versions` — list versions of a data item
- `swamp data delete` — delete data remotely
- `swamp data rename` — rename data remotely
Model operations
- `swamp model get` — get a model definition
- `swamp model output get/data/logs/search` — model output retrieval
- `swamp model method history get/logs/search` — method execution history
- `swamp model validate` / `swamp model evaluate` — validate/evaluate definitions
- `swamp model create/delete` — remote definition management
Workflow operations
- `swamp workflow get` — get a workflow definition
- `swamp workflow history get/logs/search` — workflow run history
- `swamp workflow run search` — search workflow runs
- `swamp workflow schema` — workflow input schema
- `swamp workflow approve/reject/resume` — approval flow
Vault operations
- `swamp vault describe` — vault configuration
- `swamp vault inspect` — vault health
- `swamp vault list-keys` — list secret keys
- `swamp vault search` — search vaults
- `swamp vault annotate` — vault metadata
Server administration
- `swamp worker list` — list connected workers
- `swamp auth whoami --server` — "who am I on this server?" based on token
- `swamp extension install/list/rm/search/info/outdated` — manage extensions on a remote server
- `swamp doctor audit/extensions/vaults/secrets/workflows` — diagnose remote server health
- `swamp datastore status` — check remote datastore health
Implementation
Same pattern as #710 — per-command `--server` and `--token` options, protocol frame types, server-side handlers with `authorizeOrReject`, same renderers for local and remote. One commit per command.
Priority
Phase 2. The commands in #710 cover the critical daily-use path. These are the long tail for full remote operations coverage.
References
- #710 — phase 1 `--server` support (data/model/workflow/vault/audit/summary/report)
- #662 — serve authentication & authorization epic
- Memory: server command inventory has the full categorization
Shipped
Click a lifecycle step above to view its details.