<< All versions

Skill v1.0.0

currentAutomated scan100/100
loupe-ac/loupe/loupe-workers
──Details
PublishedNovember 17, 2026 at 11:19 AM
Content Hashsha256:325690c9e628be47...
Git SHA8f577c719f68
──Files
Files (1 file, 5.6 KB)
SKILL.md5.6 KBactive
SKILL.md · 85 lines · 5.6 KB

name: loupe-workers description: "Use when reading worker runs or bridges through the loupe MCP, stopping, resuming or holding workers, cancelling a bridge command, or recovering workers after a usage limit or network outage." metadata: version: "1.0.0"


Controlling Loupe workers

A bridge runs the workers of a project, and each worker is a run on one card. A resume continues the session of a run as a new run of the same series. The tools act as the project owner, on the bound project only, with the same checks as the worker runs page. No tool pauses a bridge.

The tools

ToolUse it to
worker_run_listfind runs by states, cardNumber, workKind, bridgeId, search, endedAfter and endedBefore
worker_run_getread one run with its series, output, state changes and commands
bridge_listcheck that each bridge is live and takes commands
worker_run_resumeresume up to 50 ended runs by runIds
worker_run_stopstop one queued, resumed, preparing or running run, or close an interactive session
card_holdhold one card, by cardId or number, so no agent starts on it
card_releaseend the hold of one card
card_pause_releaseend the workflow pause of one card, so the paused rule runs again
bridge_command_cancelwithdraw the command that waits on one run

Pass runId values from worker_run_list, never a card number. Only card_hold, card_release and card_pause_release name a card.

Recover workers after a usage limit or an outage

  1. Call worker_run_list with states such as gave-up, failed, timed-out and lost, and a window around the outage. A timed-out or lost run counts at its first report, so start endedAfter before the outage began.
  2. Read every page while hasMore is true.
  3. Read the reason of each row, and group the runs by cause yourself. Leave out a run that failed for its own reason.
  4. Call bridge_list. Each bridge of the runs must show liveness live and takesCommands true.
  5. Confirm that the cause is gone, for example that the usage limit reset. When you cannot confirm it, do not resume.
  6. Call worker_run_resume with the run ids, at most 50 in one call.
  7. Read each row of results. A resumed row carries commandId, and a refused row carries code and message.
  8. Call card_list with paused true, and read every page.
  9. Call card_get on each card, and read its pause: kind, reason, ruleId and since.
  10. Call card_pause_release with the cardId and the pauseId of each pause that the outage caused. Leave a pause that has its own cause.

Refusal codes

CodeMeaning
not-foundno run of this project has this id
no-bridge, unknown-bridgethe run has no connected bridge, so tell a person
bridge-outdatedthe bridge cannot take commands, so ask a person to update it
pendinga command already waits on the run, so wait or cancel it
not-controllablethe run is an interactive session, and the tool cannot resume it
no-sessionthe run has no session to resume
not-resumablethe run did not end, or it succeeded
card-leftthe card left the column of the run, so leave the run
card-heldthe card is held, so ask a person to manage it again
not-stoppablethe run is not queued, resumed, preparing or running
reason-too-longthe stop reason is over 1000 characters
nothing-pendingno command waits, or the bridge already read it
already-pausedcard_hold found the card held already
card-gonecard_hold found the card deleted
not-pausedcard_release found no hold, or card_pause_release found no workflow pause
card-unmanagedcard_pause_release found the card held, or the workflow off for the project
pause-changedthe active pause is not the pauseId you passed, so read the card again
kind-not-releasablea pause of kind rule ends only on its own release condition

Stop a run

Call worker_run_stop with the runId and a reason that a person reads. A stop ends this run only. On an interactive session, worker_run_stop closes the run in Loupe with the outcome closed. The terminal of the session stays open. A rule can still start new work on the card, because a stop does not hold the card.

Hold a card

Call card_hold with one of cardId or number. No bridge then starts a worker on the card. A hold stops no live run, so call worker_run_stop as well when a run must end now. A queued run waits, and starts when the hold ends.

Call card_release to end the hold. A person ends it too when they select Manage again, delete the column of the card, or delete the card.

At the end of a hold, each workflow rule whose condition is true fires, also when it was true before the hold. Each rule gets a fresh work budget, and an open work request gets a new timeout. A live request is not opened twice, and a workflow pause stays.

Release a workflow pause

The workflow pauses a card when a rule runs out of retries, reaches its work limit, or no bridge takes its work in time. A hold and a workflow pause are different states, and card_release does not end a pause.

Call card_pause_release with one of cardId or number, and the pauseId from card_get. The paused rule then runs again with a fresh budget. Release a pause only when its cause is gone. A person releases a pause with Retry now in the Workflow panel of the card.

Cancel a command

Call bridge_command_cancel with the runId to withdraw the waiting resume or stop. An online bridge reads a command in about a second, so a cancel helps mainly while a bridge is offline.

All versions