Skip to main content
← Back to list
01Issue
BugOpenExtensionsPublic
AssigneesNone

Relationships

#4359 Work-item commands run from the wrong repo report the work item as not started

Opened by mtaylor · 11/3/2026

A work-item method run from a different swamp repo than the one holding the work item says the work item has not started, which reads as lost or broken state, not as a wrong directory.

Steps:

  1. In repo A, start a work item: swamp model @swamp/stagecraft/work-item method run start my-item --input factory=<factory>, and advance it a few stages.
  2. From a sibling repo B (no --repo-dir), run swamp model @swamp/stagecraft/work-item method run status my-item, or any write such as record_evidence.

Actual: Error: the work item has not started; run start with --input factory=<factory>

Expected: a message that says no work item my-item exists in this repo (naming the repo path), and suggests --repo-dir or running from the repo that has it. Following the current hint and running start in repo B would create a second, empty work item under the same key.

Seen with @swamp/stagecraft 2026.10.13.1, swamp 20261022.021804.0-sha.983e2929, on Windows.

Upstream repository: https://github.com/swamp-club/swamp-extensions

Environment

  • Extension: @swamp/stagecraft@2026.10.13.1
  • swamp: 20261022.021804.0-sha.983e2929
  • OS: windows (x86_64)
  • Deno: 2.9.8
  • Shell: C:\Program Files\Git\usr\bin\bash.exe
02Bog Flow
◉OPEN○TRIAGED○IN PROGRESS○SHIPPED

Open

11/3/2026, 6:55:55 PM

No activity in this phase yet.

03Sludge Pulse
Editable. Press Enter to edit.

system commented 11/3/2026, 6:55:56 PM

Classified automatically when this issue was filed.

  • Source: Extensions

If you feel this classification is incorrect, add a ripple to tell us so.

Sign in to post a ripple.