status

Check the current state of the Fabrik project. Run these probes (in parallel where possible), then summarise.

1. Read the project config

Use the Read tool on .fabrik/config.yaml to extract:

• owner (GitHub org or user)
• project (project number, integer)
• owner_type if present (organization or user — defaults to organization when omitted)

You'll inline these values into the GraphQL query in step 3. Don't try to set shell variables from config.yaml in a heredoc — just substitute the values directly into the gh api graphql invocation.

2. Find running workers

Fabrik spawns every worker with --plugin-dir <abs-path-to-.fabrik/plugin> (runClaude appends this flag on every invocation). This is the only reliable detector.

--output-format stream-json must never be used as a detector, alone or in combination. It's the generic Claude Code headless flag — any headless claude process on the machine matches it, including other plugins' background daemons (e.g. claude-mem), other agent harnesses, or a user's own scripts. None of those processes carry --plugin-dir .fabrik/plugin. Matching on it (even as one arm of an "either/or") reintroduces false positives; don't reintroduce it here even for "redundancy."

Scope the match to this project's absolute plugin-dir path, not just the relative .fabrik/plugin suffix — Fabrik commonly runs as a fleet of concurrent per-repo instances on one host, and a relative match would also count a different repo's Fabrik workers as this project's:

FABRIK_PLUGIN_DIR="$(pwd)/.fabrik/plugin"
ps aux | grep -F -- "--plugin-dir $FABRIK_PLUGIN_DIR " | grep -v grep

Use $(pwd), not realpath/pwd -P — Fabrik itself derives this path from os.Getwd() without resolving symlinks, so a symlink-resolving form could produce a path that no longer textually matches what a running worker actually passed on its command line. Use grep -F (fixed string), not an interpolated regex, so the path's literal characters can't be misread as regex metacharacters. The trailing space in the pattern is required, not cosmetic: without it, a fixed-string match is a prefix match, and one project's plugin-dir path can be a literal prefix of another's (e.g. a dev --plugin-dir override of .fabrik/plugin vs .fabrik/plugin-workflows, both documented in docs/USER_GUIDE.md) — the trailing space anchors on the argument boundary that always follows --plugin-dir <value> in Fabrik's actual argv (--resume, --model, or --max-turns always come next; see buildClaudeArgs in engine/claude.go), so a same-prefix-different-suffix path can no longer false-match.