@otto-code/protocol 0.7.5 → 0.8.0

package/dist/agent-attention-notification.d.ts

@@ -2,6 +2,7 @@ export type AgentAttentionReason = "finished" | "error" | "permission";
 export interface AgentAttentionNotificationData {
     [key: string]: unknown;
     serverId: string;
+    workspaceId?: string;
     agentId: string;
     reason: AgentAttentionReason;
 }
@@ -13,6 +14,7 @@ export interface AgentAttentionNotificationPayload {
 interface BuildAgentAttentionNotificationPayloadInput {
     reason: AgentAttentionReason;
     serverId: string;
+    workspaceId: string;
     agentId: string;
     assistantMessage?: string | null;
     permissionRequest?: NotificationPermissionRequest | null;

package/dist/agent-attention-notification.js

@@ -74,7 +74,7 @@ const PERMISSION_INPUT_DESCRIPTION_KEYS = [
     "query",
     "prompt",
 ];
-// Deterministic field extraction — NOT an AI summary. Picks an existing string
+// Deterministic field extraction - NOT an AI summary. Picks an existing string
 // field out of the tool's input (by the priority list, then any string field)
 // so the notification can show it verbatim instead of raw JSON.
 const describePermissionInput = (input) => {
@@ -180,6 +180,7 @@ export function buildAgentAttentionNotificationPayload(input) {
         body,
         data: {
             serverId: input.serverId,
+            workspaceId: input.workspaceId,
             agentId: input.agentId,
             reason: input.reason,
         },

package/dist/agent-deep-link.d.ts

@@ -0,0 +1,8 @@
+export interface AgentDeepLinkTarget {
+    serverId: string;
+    agentId: string;
+}
+export declare function buildAgentDeepLinkRoute(target: AgentDeepLinkTarget): `/h/${string}/agent/${string}`;
+export declare function buildAgentDeepLink(target: AgentDeepLinkTarget): string;
+export declare function parseAgentDeepLink(input: string): AgentDeepLinkTarget | null;
+//# sourceMappingURL=agent-deep-link.d.ts.map

package/dist/agent-deep-link.js

@@ -0,0 +1,49 @@
+function normalizeSegment(value) {
+    return value.trim();
+}
+function normalizeAgentDeepLinkTarget(target) {
+    const serverId = normalizeSegment(target.serverId);
+    const agentId = normalizeSegment(target.agentId);
+    if (!serverId || !agentId) {
+        throw new Error("Agent deep links require a server ID and agent ID.");
+    }
+    return { serverId, agentId };
+}
+export function buildAgentDeepLinkRoute(target) {
+    const { serverId, agentId } = normalizeAgentDeepLinkTarget(target);
+    return `/h/${encodeURIComponent(serverId)}/agent/${encodeURIComponent(agentId)}`;
+}
+export function buildAgentDeepLink(target) {
+    return `otto:/${buildAgentDeepLinkRoute(target)}`;
+}
+export function parseAgentDeepLink(input) {
+    let url;
+    try {
+        url = new URL(input);
+    }
+    catch {
+        return null;
+    }
+    if (url.protocol !== "otto:" ||
+        url.hostname !== "h" ||
+        url.username ||
+        url.password ||
+        url.port ||
+        url.search ||
+        url.hash) {
+        return null;
+    }
+    const segments = url.pathname.split("/").filter(Boolean);
+    if (segments.length !== 3 || segments[1] !== "agent") {
+        return null;
+    }
+    try {
+        const serverId = normalizeSegment(decodeURIComponent(segments[0] ?? ""));
+        const agentId = normalizeSegment(decodeURIComponent(segments[2] ?? ""));
+        return serverId && agentId ? { serverId, agentId } : null;
+    }
+    catch {
+        return null;
+    }
+}
+//# sourceMappingURL=agent-deep-link.js.map

package/dist/agent-labels.js

@@ -11,9 +11,9 @@ export function isDelegatedAgent(agent) {
 // ── Orchestration node labels (projects/orchestration-graphs) ───────────────
 // Stamped by the daemon on agents it spawns as orchestration participants. The
 // otto-tool catalog reads the policy label to enforce the tool binary:
-// "deterministic" — the daemon does all linking; the node gets NO orchestration
+// "deterministic" - the daemon does all linking; the node gets NO orchestration
 // tools (spawning/steering agents, runs), NO preview/dev-server tools, and NO
-// browser tools. "autonomous" — full otto toolset EXCEPT start_run
+// browser tools. "autonomous" - full otto toolset EXCEPT start_run
 // (orchestrations never nest orchestrations).
 export const ORCHESTRATION_POLICY_LABEL = "otto.orchestration-policy";
 export const ORCHESTRATION_POLICIES = ["deterministic", "autonomous"];
@@ -26,10 +26,10 @@ export function getOrchestrationPolicyFromLabels(labels) {
 export const ORCHESTRATION_RUN_ID_LABEL = "otto.orchestration-run-id";
 // The node's declared output fields, JSON-encoded, stamped on the spawned
 // agent. The otto-tool catalog reads it to register that agent's submit_output
-// tool — which is why this rides a label rather than a spawn option: the
+// tool - which is why this rides a label rather than a spawn option: the
 // catalog is built per agent from the agent's own record, so every provider
 // (MCP-served and native-loop alike) inherits the tool with no per-provider
-// plumbing. Malformed JSON reads as "no declared fields" — a node that can't
+// plumbing. Malformed JSON reads as "no declared fields" - a node that can't
 // parse its own contract falls back to prose rather than failing to spawn.
 export const ORCHESTRATION_OUTPUT_FIELDS_LABEL = "otto.orchestration-output-fields";
 export function getOutputFieldsFromLabels(labels) {

package/dist/agent-personalities.d.ts

@@ -24,7 +24,7 @@ export declare function personalityCanLaunch(personality: Pick<AgentPersonality,
 export interface PersonalitySelectionSummary {
     tier: PersonalityRoleTier;
     canLaunch: boolean;
-    /** The "why you'd choose me" blurb — each of the personality's roles, joined. */
+    /** The "why you'd choose me" blurb - each of the personality's roles, joined. */
     guidance: string;
 }
 /**
@@ -40,7 +40,7 @@ export declare const ORCHESTRATOR_METHOD_DIRECTIVE: string;
  * spawn. The orchestrator gets the full conductor method; other coordinators
  * (chatter/artificer/scheduler) get a lighter delegate nudge; focused workers
  * are told to stay on the task someone is waiting on. Roleless spawns get
- * nothing. This is guidance, not a gate — the tools stay available either way.
+ * nothing. This is guidance, not a gate - the tools stay available either way.
  */
 export declare function composeRoleFocusDirective(roles: readonly string[] | undefined): string | undefined;
 export type PersonalityUnavailableCode = "provider-missing" | "provider-disabled" | "provider-not-ready" | "model-missing" | "mode-missing";

package/dist/agent-personalities.js

@@ -1,7 +1,7 @@
 import { PERSONALITY_ROLES } from "./messages.js";
 // Pure, dependency-free personality helpers shared by the daemon (spawn-time
 // resolution) and the app (picker availability + role filtering). Effort
-// resolution is NOT here — it needs the model's advertised thinking options and
+// resolution is NOT here - it needs the model's advertised thinking options and
 // lives with the daemon's effort resolver; availability does not depend on it.
 const ROLE_SET = new Set(PERSONALITY_ROLES);
 // Retired role names, mapped to their canonical replacement. "worker" was split
@@ -41,7 +41,7 @@ export const PERSONALITY_ROLE_INFO = {
     // ── Surfaces ──────────────────────────────────────────────────────────────
     chatter: {
         tier: "coordinator",
-        guidance: "Interactive driver — converse, plan, and delegate. Pick to run a chat or coordinate work.",
+        guidance: "Interactive driver - converse, plan, and delegate. Pick to run a chat or coordinate work.",
     },
     artificer: {
         tier: "coordinator",
@@ -54,37 +54,37 @@ export const PERSONALITY_ROLE_INFO = {
     // ── Thinking workers (read-only, structured findings) ─────────────────────
     researcher: {
         tier: "focused",
-        guidance: "Read-only surveyor — maps the code or domain and reports files, types, patterns, and gotchas. Pick to gather facts; proposes no solutions and edits nothing.",
+        guidance: "Read-only surveyor - maps the code or domain and reports files, types, patterns, and gotchas. Pick to gather facts; proposes no solutions and edits nothing.",
     },
     planner: {
         tier: "focused",
-        guidance: "Planning specialist — turns a goal into a typed, sequenced phase plan for others to execute. Pick to draft an actionable plan; stays on the plan and doesn't dispatch.",
+        guidance: "Planning specialist - turns a goal into a typed, sequenced phase plan for others to execute. Pick to draft an actionable plan; stays on the plan and doesn't dispatch.",
     },
     judger: {
         tier: "focused",
-        guidance: "Review specialist — evaluates work or a plan against criteria and returns a structured verdict. Pick for a focused review; stays on task.",
+        guidance: "Review specialist - evaluates work or a plan against criteria and returns a structured verdict. Pick for a focused review; stays on task.",
     },
     advisor: {
         tier: "focused",
-        guidance: "Read-only second opinion — weighs the trade-offs and returns one recommendation. Pick for advice; never edits and does not fan out.",
+        guidance: "Read-only second opinion - weighs the trade-offs and returns one recommendation. Pick for advice; never edits and does not fan out.",
     },
     // ── Making workers (produce code, design, or text) ────────────────────────
     coder: {
         tier: "focused",
-        guidance: "Focused implementer — writes code for one sub-task others are waiting on. Pick to get a coding job done; stays on task.",
+        guidance: "Focused implementer - writes code for one sub-task others are waiting on. Pick to get a coding job done; stays on task.",
     },
     designer: {
         tier: "focused",
-        guidance: "Design maker — styling and layout plus the human-skill text (copy, naming). Pick for the look-and-feel or the words; stays on task.",
+        guidance: "Design maker - styling and layout plus the human-skill text (copy, naming). Pick for the look-and-feel or the words; stays on task.",
     },
     writer: {
         tier: "focused",
-        guidance: "Fast small-text specialist — commit messages, summaries, names. Pick for quick text; stays on the one task.",
+        guidance: "Fast small-text specialist - commit messages, summaries, names. Pick for quick text; stays on the one task.",
     },
     // ── Conductor ─────────────────────────────────────────────────────────────
     orchestrator: {
         tier: "coordinator",
-        guidance: "The sole conductor — plans team-shaped work, dispatches typed tasks to the right teammates, gathers, and synthesizes. Pick to run a multi-agent workflow.",
+        guidance: "The sole conductor - plans team-shaped work, dispatches typed tasks to the right teammates, gathers, and synthesizes. Pick to run a multi-agent workflow.",
     },
 };
 /**
@@ -111,21 +111,21 @@ export function summarizePersonalityForSelection(personality) {
         guidance: roles.map((role) => PERSONALITY_ROLE_INFO[role].guidance).join(" "),
     };
 }
-// The conductor's standing directive — the distilled `/epic` method taught to
+// The conductor's standing directive - the distilled `/epic` method taught to
 // the sole orchestrator role at spawn, so orchestration is emergent (the agent
 // recognizes team-shaped work and runs it) rather than something a user must
 // invoke. Kept here as one exported constant so the wording is testable and
 // shared. See projects/agent-orchestration/agent-orchestration.md.
-export const ORCHESTRATOR_METHOD_DIRECTIVE = "You are the orchestrator — the team's sole conductor. Team-shaped work is yours to run, and you should reach for it naturally, not only when asked. " +
-    "First apply the complexity gate: if a task is small and not splittable, just do it — no ceremony. Only orchestrate when the work is large, parallelizable, or benefits from independent perspectives. " +
-    "When you do orchestrate: (1) if the shape is unclear, dispatch a researcher to survey and a planner to draft a typed plan; (2) declare that plan as a Run with start_run — phases typed research/plan/implement/design/verify/gate/deliver, fanning out candidates where several angles help and attaching a judger to grade them, looping until enough pass; (3) put a gate before irreversible or costly steps so the user approves; (4) synthesize the passing results into the deliverable. " +
-    "Prefer start_run over hand-spawning and tracking agents yourself — the runtime fans out, gathers typed verdicts, and enforces the loop for you. Every phase maps to a teammate's role; if the active team lacks a role a phase needs, say so plainly and stop rather than papering over the gap.";
+export const ORCHESTRATOR_METHOD_DIRECTIVE = "You are the orchestrator - the team's sole conductor. Team-shaped work is yours to run, and you should reach for it naturally, not only when asked. " +
+    "First apply the complexity gate: if a task is small and not splittable, just do it - no ceremony. Only orchestrate when the work is large, parallelizable, or benefits from independent perspectives. " +
+    "When you do orchestrate: (1) if the shape is unclear, dispatch a researcher to survey and a planner to draft a typed plan; (2) declare that plan as a Run with start_run - phases typed research/plan/implement/design/verify/gate/deliver, fanning out candidates where several angles help and attaching a judger to grade them, looping until enough pass; (3) put a gate before irreversible or costly steps so the user approves; (4) synthesize the passing results into the deliverable. " +
+    "Prefer start_run over hand-spawning and tracking agents yourself - the runtime fans out, gathers typed verdicts, and enforces the loop for you. Every phase maps to a teammate's role; if the active team lacks a role a phase needs, say so plainly and stop rather than papering over the gap.";
 /**
  * The in-context "role directive" injected into a personality's system prompt at
  * spawn. The orchestrator gets the full conductor method; other coordinators
  * (chatter/artificer/scheduler) get a lighter delegate nudge; focused workers
  * are told to stay on the task someone is waiting on. Roleless spawns get
- * nothing. This is guidance, not a gate — the tools stay available either way.
+ * nothing. This is guidance, not a gate - the tools stay available either way.
  */
 export function composeRoleFocusDirective(roles) {
     const normalized = normalizePersonalityRoles(roles);
@@ -139,7 +139,7 @@ export function composeRoleFocusDirective(roles) {
     if (normalized.some((role) => PERSONALITY_ROLE_INFO[role].tier === "coordinator")) {
         return `You are a coordinator personality (roles: ${roleList}). You front interactive work and may delegate: use list_personalities to see who else is available, and spawn other agents or hand off to the team's orchestrator whenever delegating gets the work done faster or better.`;
     }
-    return `You are a focused worker personality (roles: ${roleList}). Someone is waiting on this specific task — stay on it and finish it. You can still call list_personalities to see the roster, but don't spawn sub-agents or start side workflows unless it is genuinely essential to completing this job.`;
+    return `You are a focused worker personality (roles: ${roleList}). Someone is waiting on this specific task - stay on it and finish it. You can still call list_personalities to see the roster, but don't spawn sub-agents or start side workflows unless it is genuinely essential to completing this job.`;
 }
 /**
  * Decide whether a personality is usable against a provider's current snapshot.

package/dist/agent-teams.d.ts

@@ -3,7 +3,7 @@ import type { AgentPersonality, AgentTeam, PersonalityRole } from "./messages.js
  * The dynamic "Team's Scheduler" schedule binding. Stored in the schedule's
  * `personality` field in place of a personality name; resolved at RUN time to
  * the active team's first available member carrying the Scheduler role
- * (member order). Deliberately contains "@" — personality names are sanitized
+ * (member order). Deliberately contains "@" - personality names are sanitized
  * to [A-Za-z0-9_-] at the authoring surface, so the sentinel can never collide
  * with a real name. No active team, or no available Scheduler member, is a
  * hard run failure with a named error (same loudness as a bound personality
@@ -17,7 +17,7 @@ export interface AgentTeamsConfigView {
 export declare function findAgentTeam(teams: readonly AgentTeam[] | undefined, teamId: string | null | undefined): AgentTeam | null;
 /**
  * Resolve the host's active team. A dangling `activeTeamId` (team deleted, or
- * a patch raced a delete) reads as "no team active" — teamlessness is a valid
+ * a patch raced a delete) reads as "no team active" - teamlessness is a valid
  * state and must never error. The daemon additionally heals a dangling id back
  * to null on the next config patch; this helper is the read-side tolerance.
  */
@@ -42,13 +42,13 @@ export declare function pruneTeamMemberIds(memberIds: readonly string[] | undefi
  * team at all, so the delete confirm can offer to clean them up. Dangling member
  * ids resolve to nothing and drop out, same as everywhere else.
  *
- * Pass the teams that will REMAIN after the delete — the caller owns the filter,
+ * Pass the teams that will REMAIN after the delete - the caller owns the filter,
  * so this stays a pure set operation with no notion of "the team being deleted".
  */
 export declare function resolveExclusiveTeamMembers(team: Pick<AgentTeam, "memberIds"> | null | undefined, otherTeams: readonly Pick<AgentTeam, "memberIds">[] | undefined, personalities: readonly AgentPersonality[] | undefined): AgentPersonality[];
 /**
  * The union of all members' roles, normalized and returned in canonical
- * `PERSONALITY_ROLES` order — the team card's role-pill strip.
+ * `PERSONALITY_ROLES` order - the team card's role-pill strip.
  */
 export declare function teamRoleUnion(team: Pick<AgentTeam, "memberIds"> | null | undefined, personalities: readonly AgentPersonality[] | undefined): PersonalityRole[];
 /**

package/dist/agent-teams.js

@@ -1,14 +1,14 @@
 import { normalizePersonalityRoles } from "./agent-personalities.js";
 // Pure, dependency-free team helpers shared by the daemon (spawn-time active
 // team resolution, list_personalities scoping) and the app (team cards,
-// pickers, the Active Team switcher). Availability is deliberately NOT here —
+// pickers, the Active Team switcher). Availability is deliberately NOT here -
 // a team is never "out of commission"; its members are individually available
 // or not, judged by checkPersonalityAvailability per member.
 /**
  * The dynamic "Team's Scheduler" schedule binding. Stored in the schedule's
  * `personality` field in place of a personality name; resolved at RUN time to
  * the active team's first available member carrying the Scheduler role
- * (member order). Deliberately contains "@" — personality names are sanitized
+ * (member order). Deliberately contains "@" - personality names are sanitized
  * to [A-Za-z0-9_-] at the authoring surface, so the sentinel can never collide
  * with a real name. No active team, or no available Scheduler member, is a
  * hard run failure with a named error (same loudness as a bound personality
@@ -23,7 +23,7 @@ export function findAgentTeam(teams, teamId) {
 }
 /**
  * Resolve the host's active team. A dangling `activeTeamId` (team deleted, or
- * a patch raced a delete) reads as "no team active" — teamlessness is a valid
+ * a patch raced a delete) reads as "no team active" - teamlessness is a valid
  * state and must never error. The daemon additionally heals a dangling id back
  * to null on the next config patch; this helper is the read-side tolerance.
  */
@@ -86,7 +86,7 @@ export function pruneTeamMemberIds(memberIds, personalities) {
  * team at all, so the delete confirm can offer to clean them up. Dangling member
  * ids resolve to nothing and drop out, same as everywhere else.
  *
- * Pass the teams that will REMAIN after the delete — the caller owns the filter,
+ * Pass the teams that will REMAIN after the delete - the caller owns the filter,
  * so this stays a pure set operation with no notion of "the team being deleted".
  */
 export function resolveExclusiveTeamMembers(team, otherTeams, personalities) {
@@ -100,7 +100,7 @@ export function resolveExclusiveTeamMembers(team, otherTeams, personalities) {
 }
 /**
  * The union of all members' roles, normalized and returned in canonical
- * `PERSONALITY_ROLES` order — the team card's role-pill strip.
+ * `PERSONALITY_ROLES` order - the team card's role-pill strip.
  */
 export function teamRoleUnion(team, personalities) {
     const roles = resolveTeamMembers(team, personalities).flatMap((personality) => personality.roles ?? []);

package/dist/agent-types.d.ts

@@ -110,6 +110,7 @@ export interface ProviderSnapshotEntry {
     provider: AgentProvider;
     status: ProviderStatus;
     enabled: boolean;
+    source?: "builtin" | "custom";
     error?: string;
     models?: AgentModelDefinition[];
     modes?: AgentMode[];
@@ -177,18 +178,18 @@ export interface AgentRunOptions {
  * origin. Powers the visualizer's context ring/bar colored segments (the same
  * five categories the vendored render layer draws). Every field is optional and
  * a token count: a provider fills as many categories as it can attribute and
- * omits the rest, so richness degrades gracefully per provider — Claude
+ * omits the rest, so richness degrades gracefully per provider - Claude
  * attributes the most; a provider that can attribute nothing omits the whole
  * object and consumers fall back to occupancy-only (no colored segments, the
  * pre-composition behavior). Counts are best-effort estimates, not billed usage;
  * they need not sum exactly to `contextWindowUsedTokens` (the consumer scales).
  */
 export interface ContextComposition {
-    /** System prompt + tool/function definitions — the fixed base cost. */
+    /** System prompt + tool/function definitions - the fixed base cost. */
     systemPrompt?: number;
     /** User-authored input messages. */
     userMessages?: number;
-    /** Tool results — file contents, search output, command output (usually the
+    /** Tool results - file contents, search output, command output (usually the
      * largest and most volatile category). */
     toolResults?: number;
     /** The agent's own reasoning / thinking blocks. */
@@ -198,14 +199,14 @@ export interface ContextComposition {
 }
 /**
  * One provider-reported context-window category. `name` is a provider-supplied
- * *display label* ("Messages", "System prompt", "MCP tools") — deliberately an
+ * *display label* ("Messages", "System prompt", "MCP tools") - deliberately an
  * OPEN-ENDED string and not an enum, so each provider reports the split it
  * actually has instead of being squeezed into categories it can't populate.
  *
  * Structurally identical to `AgentContextUsageCategory` on the pull path
  * (`agent.context.get_usage`, see messages.ts) *by design*: the two carry the
  * same accounting, one pushed on the agent snapshot and one pulled on demand.
- * Keep them in sync — a divergence here is how the context meter and the
+ * Keep them in sync - a divergence here is how the context meter and the
  * visualizer would start disagreeing about the same agent.
  */
 export interface AgentContextCategory {
@@ -218,7 +219,7 @@ export interface AgentUsage {
     inputTokens?: number;
     cachedInputTokens?: number;
     /**
-     * Prompt tokens spent writing (not reading) the prompt cache this turn —
+     * Prompt tokens spent writing (not reading) the prompt cache this turn -
      * Anthropic's `cache_creation_input_tokens`, billed above normal input.
      * Disjoint from `inputTokens`/`cachedInputTokens`. Claude-specific today;
      * other providers omit it. Optional/additive.
@@ -235,7 +236,7 @@ export interface AgentUsage {
      */
     contextComposition?: ContextComposition;
     /**
-     * The provider's OWN context-window split, with its own labels — the same
+     * The provider's OWN context-window split, with its own labels - the same
      * accounting the `agent.context.get_usage` RPC returns, pushed here on the
      * agent snapshot so stream/backfill consumers (the visualizer) read the very
      * numbers the context meter shows rather than a parallel estimate.
@@ -373,6 +374,7 @@ export type AgentTimelineItem = {
     type: "user_message";
     text: string;
     messageId?: string;
+    clientMessageId?: string;
 } | {
     type: "assistant_message";
     text: string;
@@ -490,7 +492,7 @@ export interface ObservedSubagentUpdate {
     requiresAttention?: boolean;
     usage?: AgentUsage;
     /**
-     * True once this run is known to outlive an interrupt of the parent's turn —
+     * True once this run is known to outlive an interrupt of the parent's turn -
      * the provider backgrounded it, so the parent's teardown does not take it
      * down. Sticky: the daemon keeps it set for the row's whole life, and
      * propagates it to nested rows (a child of a backgrounded run survives too).
@@ -509,7 +511,7 @@ export interface ObservedSubagentUpdate {
      */
     toolUseCount?: number;
     /**
-     * The tool this subagent is running (or ran last) — the "spinning _on a 90s
+     * The tool this subagent is running (or ran last) - the "spinning _on a 90s
      * Bash_" signal. Neutral field any provider can set; unlike the counters it is
      * NOT monotonic (latest wins) and the daemon drops it once the row goes
      * terminal. Claude reads it from `task_progress.last_tool_name`. Absent ⇒ the
@@ -521,7 +523,7 @@ export interface ObservedSubagentUpdate {
  * A background shell task reported by a provider's own Bash tool (Claude:
  * `run_in_background`). `key` is a provider-local stable identifier (Claude:
  * the Bash tool_use id); the daemon namespaces it under the owning agent.
- * Unlike {@link ObservedSubagentUpdate} this has no transcript/pane — it's a
+ * Unlike {@link ObservedSubagentUpdate} this has no transcript/pane - it's a
  * plain status row (command, status, elapsed) in the Background Tasks track.
  */
 export interface BackgroundShellTaskUpdate {

package/dist/agent-types.js

@@ -26,7 +26,7 @@ export function getAgentStreamEventTurnId(event) {
 // accept the setting and ignore it.
 //
 // This is a *boundary*, not an instruction. "read" means the write tools are
-// not offered, so there is no write to make — never a line of prompt asking the
+// not offered, so there is no write to make - never a line of prompt asking the
 // model to behave. A control a user relies on when deciding to run something
 // unattended has to be true in exactly the cases where the model is confused.
 export const WORKSPACE_ACCESS_LEVELS = ["none", "read", "write"];

package/dist/artifacts/rpc-schemas.js

@@ -20,13 +20,13 @@ export const ArtifactCreateRequestSchema = z.object({
     systemPrompt: z.string().optional(),
     // Snapshotted spinner colors of the chosen Agent Personality (optional).
     spinner: ArtifactSpinnerSchema.optional(),
-    // Snapshotted human name of the chosen Agent Personality (optional) — shown
+    // Snapshotted human name of the chosen Agent Personality (optional) - shown
     // on the artifact card's identity line as the "who generated it".
     personalityName: z.string().optional(),
     requestId: z.string(),
 });
 // Update edits an artifact's metadata (name/description/project/provider/
-// model/thinking) WITHOUT re-running generation — editing never regenerates;
+// model/thinking) WITHOUT re-running generation - editing never regenerates;
 // the user triggers that separately. Every field except artifactId is
 // optional; only provided fields overwrite.
 export const ArtifactUpdateRequestSchema = z.object({
@@ -41,7 +41,7 @@ export const ArtifactUpdateRequestSchema = z.object({
     requestId: z.string(),
 });
 // Regenerate re-runs generation for an existing artifact using its stored
-// config. It carries no field updates — edit those first via update.request.
+// config. It carries no field updates - edit those first via update.request.
 export const ArtifactRegenerateRequestSchema = z.object({
     type: z.literal("artifact.regenerate.request"),
     artifactId: z.string(),
@@ -166,7 +166,7 @@ export const ArtifactDeletedNotificationSchema = z.object({
         artifactId: z.string(),
     }),
 });
-// Input validation helper — extracts CreateArtifactInput from a create request
+// Input validation helper - extracts CreateArtifactInput from a create request
 export function validateArtifactCreateRequest(data) {
     const result = ArtifactCreateRequestSchema.safeParse(data);
     if (!result.success) {

package/dist/artifacts/types.js

@@ -27,7 +27,7 @@ export const ArtifactMetadataSchema = z.object({
     generationModel: z.string().nullable(),
     // Requested generation mode/effort, persisted so regeneration re-runs with
     // the same settings. Optional: records written before these fields existed
-    // omit them (no migrations). The mode is a *request* — the artifact service
+    // omit them (no migrations). The mode is a *request* - the artifact service
     // only honors unattended modes and otherwise resolves the provider's
     // unattended default, so generation never stalls on an approval prompt.
     generationModeId: z.string().nullable().optional(),
@@ -39,7 +39,7 @@ export const ArtifactMetadataSchema = z.object({
     generationSpinner: ArtifactSpinnerSchema.nullable().optional(),
     // Human name of the Agent Personality that generated (last generated) this
     // artifact, snapshotted at create/regenerate time like the provider/model
-    // above — the "who actually did it" the card's identity line shows alongside
+    // above - the "who actually did it" the card's identity line shows alongside
     // provider/model. Absent ⇒ no personality was used (plain provider/model
     // selection). Purely additive (no daemon floor needed).
     generationPersonalityName: z.string().nullable().optional(),
@@ -71,7 +71,7 @@ export const ArtifactRunSchema = z.object({
 });
 // The full on-disk record: the lean metadata plus its generation run history.
 // `runs` defaults to [] so records written before run history existed parse
-// unchanged (no migrations — same approach the rest of the store takes).
+// unchanged (no migrations - same approach the rest of the store takes).
 // list_artifacts / broadcasts keep sending ArtifactMetadata (runs stripped);
 // only inspect_artifact returns this fuller shape.
 export const StoredArtifactSchema = ArtifactMetadataSchema.extend({

package/dist/binary-frames/file-transfer.d.ts

@@ -13,6 +13,7 @@ export declare const FileBeginMetadataSchema: z.ZodObject<{
         "utf-8": "utf-8";
     }>;
     modifiedAt: z.ZodString;
+    revision: z.ZodOptional<z.ZodString>;
     fileName: z.ZodOptional<z.ZodString>;
 }, z.core.$strip>;
 export interface FileBegin {

package/dist/binary-frames/file-transfer.js

@@ -10,6 +10,7 @@ export const FileBeginMetadataSchema = z.object({
     size: z.number().int().nonnegative(),
     encoding: z.enum(["utf-8", "binary"]),
     modifiedAt: z.string(),
+    revision: z.string().optional(),
     fileName: z.string().optional(),
 });
 export function encodeFileTransferFrame(input) {

package/dist/browser-automation/rpc-schemas.js

@@ -418,7 +418,7 @@ export const BrowserAutomationScreenshotElementResultSchema = z.object({
     dataBase64: z.string().min(1),
     width: z.number().int().nonnegative(),
     height: z.number().int().nonnegative(),
-    /** Render scale used for the clip — above 1 means the element was re-rendered zoomed in. */
+    /** Render scale used for the clip - above 1 means the element was re-rendered zoomed in. */
     scale: z.number().positive().optional(),
 });
 export const BrowserAutomationUploadResultSchema = z.object({

package/dist/client-capabilities.d.ts

@@ -1,7 +1,10 @@
 export declare const CLIENT_CAPS: {
+    readonly selectiveAgentTimeline: "selective_agent_timeline";
     readonly reasoningMergeEnum: "reasoning_merge_enum";
     readonly customModeIcons: "custom_mode_icons";
     readonly terminalReflowableSnapshot: "terminal_reflowable_snapshot";
+    readonly providerSubagents: "provider_subagents";
+    readonly projectUpdates: "project_updates";
     readonly browserHost: "browser_host";
 };
 export type ClientCapability = (typeof CLIENT_CAPS)[keyof typeof CLIENT_CAPS];

package/dist/client-capabilities.js

@@ -1,4 +1,8 @@
 export const CLIENT_CAPS = {
+    // COMPAT(selectiveAgentTimeline): added in v0.1.106. Capable clients receive
+    // agent streams only for their explicit viewed set. Remove after 2027-01-12
+    // once the supported client floor is >= v0.1.106.
+    selectiveAgentTimeline: "selective_agent_timeline",
     reasoningMergeEnum: "reasoning_merge_enum",
     // COMPAT(customModeIcons): added in v0.1.84. Old clients pin AgentModeIcon to
     // a closed enum and crash rendering unknown values; daemon downgrades icons
@@ -11,6 +15,11 @@ export const CLIENT_CAPS = {
     // Old clients use a strict TerminalState schema and would reject the extra fields.
     // Drop the gate (always send the flags) when floor >= v0.1.88.
     terminalReflowableSnapshot: "terminal_reflowable_snapshot",
+    // COMPAT(providerSubagents): added in v0.1.107. The daemon emits provider-owned
+    // child descriptors and timelines only to clients that understand the new messages.
+    providerSubagents: "provider_subagents",
+    // COMPAT(projectUpdates): added in v0.1.109, remove gate after 2027-01-15.
+    projectUpdates: "project_updates",
     browserHost: "browser_host",
 };
 //# sourceMappingURL=client-capabilities.js.map

package/dist/daemon-endpoints.d.ts

@@ -32,7 +32,7 @@ export declare function buildRelayWebSocketUrl(params: {
     role: RelayRole;
     /**
      * Per-connection routing identifier used by the daemon to open server data sockets.
-     * Clients should NOT provide this — the relay assigns a routing ID on connect.
+     * Clients should NOT provide this - the relay assigns a routing ID on connect.
      */
     connectionId?: string;
     version?: RelayProtocolVersion | 1 | 2;