Files

T

Bohdan Triapitsyn e908db637b feat: agent and CLI control plane for sessions, worktrees, and scheduled tasks (#2408 )

Add a shared OpenChamber control service with two thin adapters — a native
`openchamber` tool injected into managed OpenCode, and new CLI commands — so
users can manage parallel sessions, worktrees, and scheduled tasks
conversationally through agents or from the terminal.

Control plane:
- New openchamber-control service owning a fixed action contract:
  projects.list, models.list, session list/create/send/fork/status/messages,
  and schedule list/create/run/delete/toggle. Session and worktree deletion
  and project registration are deliberately not exposed.
- New openchamber-sessions module owning create/worktree/prompt orchestration,
  Goal Mode dispatch, wait semantics (initial idle never counts as completion;
  timeout and cancellation are failures), and explicit partial-failure results.
- Scheduled-task logic extracted into a service shared by routes, CLI, and the
  agent tool.

Agent tool:
- Managed OpenCode gets a materialized plugin registering one typed tool with
  a loopback-only callback, per-child ephemeral bearer (timing-safe, never
  persisted or logged), and abort propagation into the service.
- The ~1.5k-token schema applies progressive disclosure: short descriptions,
  server-side validation returning actionable usage errors, and intent
  guardrails — created sessions/tasks are user-facing work (not age
  self-delegation); worktree/goal/agent/variant/wait are omit-by-default;
  dispatches produce no completion notification, and later result r
  to session.messages, which now returns the authoritative sessionStatus.
- session.create without a user-named model picks from favorites/re
  send/fork omit the selection and the service reuses the target session's
  last user-message model, agent, and variant before falling back t
- An "Agent control tool" setting (default on, Save + Reload to apply)
  disables plugin injection entirely.

CLI:
- New `openchamber session`, `schedule`, `projects`, and `models` commands
  with automatic instance targeting, --wait/--timeout/--last-assist
  worktree flags, and Goal Mode, preserving interactive, non-TTY, --quiet,
  and --json contracts. The control HTTP timeout derives from the w
  instead of the 4-second default.

UI:
- New built-in "Schedule a Task" starter (/schedule-task) running a
  dialogue that defines a task and offers to create it via the tool after
  explicit confirmation; Craft a Goal and Feature Planning gain the
  handoff offer, and guided starters reserve the question tool for concrete
  option choices. Localized in all 10 locales, migrated into custom
  starter lists, hidden on VS Code.
- Sidebar shows CLI/agent-created sessions live via the control eve
- openchamber tool calls render with per-action titles and metadata.

2026-07-24 21:54:28 +03:00

2.4 KiB

Raw Blame History

OpenChamber Control Service

Purpose

This module owns the typed control contract shared by the OpenChamber CLI and the managed OpenCode openchamber tool. Both adapters delegate to createOpenChamberControlService(); neither adapter may call or spawn the other.

Boundaries

service.js validates and executes the fixed project, model, session, and scheduled-task action allowlist. actions.js marks CLI-only actions with agentExposed: false (currently schedule.status); the agent tool consumes the filtered OPENCHAMBER_AGENT_TOOL_* exports. schedule.toggle requires the disabled boolean and replaces separate enable/disable actions; schedule.list also returns scheduler status as scheduler.
routes.js is the authenticated CLI HTTP adapter. It forwards one action, preserves service status and partial-result details, and propagates request cancellation.
../agent-tool/runtime.js is the managed-tool adapter. It wraps service results in the versioned native-tool envelope and uses a separate ephemeral loopback credential.
../openchamber-sessions/routes.js and ../scheduled-tasks/service.js own their domain operations and are composed into this service.

Invariants

Session status and messages come from official directory-scoped OpenCode APIs. Message output includes only ordered text parts.
Wait never treats an initial idle response as completion after dispatch. It requires observed activity or a newly completed assistant message.
Timeout and cancellation are failures, never authoritative idle results.
Validation that protects side effects runs before session creation or dispatch.
Send and fork dispatches without an explicit model/agent/variant reuse the target session's last user-message selection before falling back to the configured defaults; only session creation resolves defaults directly.
Usage errors name the missing or conflicting input so CLI and agent-tool callers can correct an invalid request without an upfront usage manual.
Explicit projectId or directory scope takes precedence over the managed tool's current-session directory fallback; the fallback never creates a conflicting second scope.
One failed directory status lookup produces unknown for only that directory and does not erase other session results.
Destructive session/worktree deletion and project-path registration are not part of the action contract.

2.4 KiB Raw Blame History

OpenChamber Control Service

Purpose

Boundaries

Invariants

2.4 KiB

Raw Blame History