swmcc / swmcc/agentic-development

swarm: agents-tab detection requires running inside a herdr pane

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement thrawn
Dominant language
Python
Stars
0
Forks
0
Avg merge
2m
Merged PRs (30d)
1

Description

thrawn swarm finds/creates the shared agents tab by asking herdr pane current for the workspace id. That only works when thrawn is invoked from inside a herdr pane.

Current behaviour when detection fails: a warning is printed and panes fall back to a per-run ⚔ swarm tab (or detached background processes when herdr isn't running at all). Agents still run either way.

Possible improvements:

  • Fall back to the focused workspace (herdr workspace API) when there's no current pane, so swarm launched from a plain terminal still lands in the right place
  • Config option to pin swarm to a specific workspace

From the swarm mode PR (#4).

🤖 Generated with Claude Code

Agent brief

Safe to land: this improves a fallback path only. When herdr pane current fails because thrawn was not invoked from inside a herdr pane, try resolving the workspace another way before falling back (for example herdr api by matching the repo cwd against workspace paths, if the socket API supports it; read herdr --help and the api subcommands to find out). Keep the existing warning and per-run tab fallback when nothing resolves. Add a test if the resolution logic is a pure function. Acceptance: make test and make lint green; behaviour inside a pane unchanged.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in the thrawn swarm detection path that calls herdr pane current, then read herdr --help and its API subcommands to determine whether the focused workspace can be resolved from the repository cwd. Preserve the existing warning and per-run ⚔ swarm fallback when resolution fails, and verify that in-pane behavior is unchanged. Run make test and make lint.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.