dsh-openkapsel

Usage

1. kapsel_config(workspace_url, control_token) stores credentials in this DSH session's private plugin state, then selects or creates an active root Plan for mutation attribution. Re-run it to switch workspaces or rotate credentials.
2. skill("openkapsel-rest") loads the authoritative REST reference before nontrivial operations.
3. Operate through the remote tools:

Tool	Purpose
kapsel_config / kapsel_status	Configure or inspect the active workspace
kapsel_plan_update	Update, reparent, cancel, or complete a Plan with a structured debrief
kapsel_fs_list / kapsel_fs_read / kapsel_fs_stat	Read-side filesystem
kapsel_fs_write / kapsel_fs_replace	Remote text write/edit
kapsel_shell_exec / kapsel_task_output	Run and poll a remote Shell task
kapsel_http	Context, Memory, sharing, preview, schedules, and other REST surfaces

kapsel_http.json is always a JSON object. Endpoint fields belong inside it, not beside it. Context-management endpoints are handled specially because their plan_id fields describe the Context graph rather than ordinary operation attribution; prefer kapsel_plan_update for Plan changes.

Each DSH agent is keyed separately by agent.id. Credentials live under $DSH_HOME/state/dsh-openkapsel//.openkapsel.env; active Plan and taskname values are held in an agent-keyed WeakMap. The local project cwd is not used for credentials or remote-workspace selection. An absolute stateDir plugin option can replace the default private state root.

For a recorded mutation, taskname is resolved from the current tool call, then the selected active Plan/session value, then the value set by kapsel_config, then the plugin's preset configuration, and finally dsh. Empty and whitespace-only values do not suppress this fallback. The active Plan is selected automatically when plan_id is omitted; selecting a persisted Plan after a Host restart also restores that Plan's taskname. A missing or blank message receives a short default operation message.