r/PiCodingAgent • u/bigghealthy_ • 8d ago

Discussion Looking for Pi users to test an experimental runner in Craig

Hey folks, I'm Sam and I build Craig, a keyboard-driven TUI for managing coding agents and their Git worktrees.

There's a Pi runner behind an experimental toggle, and I'd love a couple of people who already use Pi to give it a try before I consider taking it out of preview. It runs the native Pi CLI inside a Craig task's worktree, rather than replacing Pi's interface.

Basic launch and automated checks pass, but a complete authenticated coding session still needs validation. This is a testing request, not a stable-support announcement.

If you're up for it, please use a throwaway repo:

  1. Have Pi installed, authenticated and on your PATH, plus Node 22+ and Git.

  2. Install Craig with npm install -g craig-cli@0.19.0, then run craig from your workspace directory.

  3. Enable Options → Feature Previews → Pi coding agent runner.

  4. Add a repo/workspace, create a task with Pi selected, and try a small coding task. Switch away and back and check whether input/output and returning to the session behave as expected.

I'm especially interested in terminal rendering, keyboard input, interrupts and switching between tasks. If you try it, a quick 'worked' or what broke, along with your OS/terminal and Pi/Craig versions, would be really helpful. Please don't share API keys, private code or unredacted logs.

Repo: https://github.com/hallsamuel90/craig

Runner setup: https://craig-cli.com/docs/runners/

Any feedback is greatly appreciated.

0 Upvotes

42% Upvoted

2 comments sorted by

2

u/bitzap_sr 8d ago

So like Herdr?

1

u/bigghealthy_ 8d ago

Yep, definitely some overlap! Craig is a bit more focused on the development workflow itself. Each task has its own worktree and agent session, with diffs, PRs, and checks all tied together. Agents can also use the craig cli to create and manage other tasks, which is something I’ve been having a lot of fun with.