@rallycry/conveyor-agent 10.6.1 → 10.7.0

package/dist/index.d.ts

@@ -424,13 +424,6 @@ declare class SessionRunner {
     private queryBridge;
     private inputResolver;
     private pendingMessages;
-    private prNudgeCount;
-    /** Set when the agent posts a substantive message to the task chat (the
-     *  `post_to_chat` tool) during the current turn; reset at the start of every
-     *  query. Read by the stuck-detection: an auto agent that finished without a
-     *  PR but DID explain itself / ask for help in chat is waiting on a human,
-     *  not silently stuck, so it is left attached rather than nudged. */
-    private agentSpokeThisTurn;
     /** Guards overlapping runs of the periodic git flush. */
     private periodicFlushInFlight;
     /** Consecutive flush ticks skipped because a heavy gate was running. */
@@ -537,43 +530,6 @@ declare class SessionRunner {
     flushGitOnShutdown(): Promise<void>;
     stop(): void;
     softStop(): void;
-    private static readonly MAX_STUCK_NUDGES;
-    /** The build-phase nudge (In Progress, no PR). Offers BOTH escape routes so
-     *  the agent never just goes idle. */
-    private static readonly STUCK_PROMPT;
-    /** The pre-build nudge (still Planning/Open, identification/plan unfinished).
-     *  Same two-escape-route shape, aimed at landing the plan + continuing to build. */
-    private static readonly STUCK_PROMPT_PLANNING;
-    /**
-     * Classify how an auto task is "stuck" after its turn ended (call sites run
-     * post-turn, so the TUI is no longer working), or null if it isn't. Shared
-     * guards: only auto, not rate-limited, under the nudge cap, and the agent
-     * stayed silent this turn — if it posted to chat (explained itself / asked for
-     * help) it's waiting on a human, not silently stuck.
-     *
-     * - "pr":       In Progress with no open PR (build finished without shipping).
-     * - "planning": still in a pre-build status (Planning/Open) without
-     *   (identified + saved plan) — e.g. the server-side InProgress bump failed
-     *   and the agent idled before documenting its plan. An agent that idles
-     *   here would otherwise clean-exit → its session Ends → the workspace is
-     *   reaped "agent_gone" before a plan ever landed. Nudging (and, on
-     *   exhaustion, going dormant) keeps the session Active so the pod is never
-     *   prematurely slept.
-     */
-    private autoStuckKind;
-    private isAutoStuck;
-    /**
-     * Stop driving the agent and route the core loop into dormant idle —
-     * connected and attachable, but NOT running (so no tokens are spent while it
-     * waits). A human reply (chat or TUI keystroke after the next wake) resumes
-     * it. This replaces the old hard `stop()`: the auto agent must never kill its
-     * own session, so a person can always take over.
-     */
-    private enterDormantForHumanTakeover;
-    private refreshTaskContext;
-    /** Prompt + chat-message label for a stuck-nudge of the given kind. */
-    private stuckNudgeContent;
-    private maybeHandleStuckAuto;
     private buildFullContext;
     private createQueryBridge;
     private wireConnectionCallbacks;

package/dist/index.js

@@ -20,7 +20,7 @@ import {
   unshallowRepo,
   updateRemoteToken,
   uploadSnapshotToGcs
-} from "./chunk-5ELLQUP4.js";
+} from "./chunk-TIEFSYIY.js";
 import "./chunk-7TQO4ZF4.js";
 
 // src/runner/worktree.ts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rallycry/conveyor-agent",
-  "version": "10.6.1",
+  "version": "10.7.0",
   "description": "Conveyor Agent Runner v10 - PTY harness for the task chat (SDK harness for audit/project-chat). Agent-as-User architecture with BaseService patterns. Works locally too.",
   "keywords": [
     "agent",

package/runtime/entrypoint.sh

@@ -337,15 +337,34 @@ if [ -n "${CONVEYOR_USER_ID}" ] && [ -n "${USER_HOME_PROJECT_ID}" ] && [ -d "${U
   USER_HOME_ROOT="${USER_HOME_MOUNT}/users/${CONVEYOR_USER_ID}/${USER_HOME_PROJECT_ID}"
   echo "[pool] Linking Claude state to ${USER_HOME_ROOT}"
   mkdir -p "${USER_HOME_ROOT}/.claude" "${USER_HOME_ROOT}/.config/claude" 2>/dev/null || true
-  seed_claude_json "${USER_HOME_ROOT}/.claude.json"
 
-  # Replace any image defaults with live symlinks into the mount.
-  rm -rf /home/conveyor/.claude /home/conveyor/.claude.json /home/conveyor/.config/claude 2>/dev/null || true
+  # Replace any image defaults with live symlinks into the mount for the SHARED,
+  # append-mostly Claude state: transcripts/plans/memory under ~/.claude and
+  # ~/.config/claude. These persist across every pod the user runs, and --resume
+  # + session history depend on them (see claude-session-persistence.md).
+  #
+  # ~/.claude.json is deliberately NOT symlinked — it is POD-LOCAL (below). The
+  # Claude CLI rewrites that file wholesale at startup and during runs, so a
+  # burst of concurrent pods for the same user+project (seen live 2026-07-12: 7
+  # pods in 10 minutes) racing one shared file produces last-writer-wins lost
+  # updates — the true root cause behind the read-back mismatch that parked a
+  # TUI at a startup dialog, and the vector that let one poisoned
+  # customApiKeyResponses write brick every future pod. Nothing load-bearing
+  # lives only in ~/.claude.json: credentials are in ~/.claude/.credentials.json
+  # (still shared, re-synthesized per boot) and transcripts in ~/.claude/projects.
+  # The agent's ensureClaudeOnboarding + the seed below rebuild every first-run
+  # gate this file needs, fresh, on each boot.
+  rm -rf /home/conveyor/.claude /home/conveyor/.config/claude 2>/dev/null || true
   mkdir -p /home/conveyor/.config 2>/dev/null || true
   ln -sfn "${USER_HOME_ROOT}/.claude"        /home/conveyor/.claude
-  ln -sfn "${USER_HOME_ROOT}/.claude.json"   /home/conveyor/.claude.json
   ln -sfn "${USER_HOME_ROOT}/.config/claude" /home/conveyor/.config/claude
 
+  # Pod-local ~/.claude.json: clear any symlink/file a prior boot or the image
+  # baked in, then seed a fresh real file on the pod's OWN disk (local
+  # read-after-write is consistent, so no cross-pod race and no read-back skew).
+  rm -rf /home/conveyor/.claude.json 2>/dev/null || true
+  seed_claude_json /home/conveyor/.claude.json
+
   # OpenCode state (sessions + config) persists the same way as ~/.claude.
   mkdir -p "${USER_HOME_ROOT}/.local/share/opencode" "${USER_HOME_ROOT}/.config/opencode" 2>/dev/null || true
   rm -rf /home/conveyor/.local/share/opencode /home/conveyor/.config/opencode 2>/dev/null || true