smithery.ai

loom-team-manager-pane-dead-on-spawn

Diagnose and fix Loom team manager pane dying immediately (tmux pane status 1).

First seen Mar 31, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1
LicenseMIT
Compatibilityopencode,claude
Declared agents claude-code opencode
More metadata
created_at
2026-01-29T09:27:53.279Z
updated_at
2026-01-29T09:27:53.279Z
version
1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,714 B
  • docs SUMMARY.md 123 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

<!-- BEGIN:compound:skill-managed -->

When To Use

  • loom team start <TEAM> succeeds, but manager pane shows dead (status 1) and capture output is empty.

Diagnose

  • Confirm run exists:

- loom team status <TEAM> --show-dead

  • Capture manager:

- loom team capture <TEAM> manager --lines 200 --header

  • Open the capture metadata file under .team/runs/<TEAM>/captures/*.json and check:

- pane.startcommand - pane.currentcommand - pane.dead

Common Root Cause: Missing team Binary

  • If pane.start_command begins with team tui ...:

- Verify: command -v team (likely missing) - Verify Loom exists: command -v loom - This means the pane died because tmux tried to run team directly.

Fix Options

  • Option A (fast local): add a team shim on PATH that forwards to Loom.

- team should behave like: loom team "$@"

  • Option B (proper): adjust Loom/runner config so tmux spawns loom team tui ... (not team tui ...).
  • Option C: pass an explicit harness --bin that points to the correct executable if supported.

Validate

  • Restart run (or use --force):

- loom team start <TEAM> --force ...

  • Confirm manager pane is alive:

- loom team status <TEAM> - loom team capture <TEAM> manager --lines 40 <!-- END:compound:skill-managed -->

Manual notes

This section is preserved when the skill is updated. Put human notes, caveats, and exceptions here.