Your board, in the loop
with your agents.

X Bench is a free, open-source Mac app for Claude Code, Codex and Grok Build. Start a chat from a ticket, review the diff, and let the agent move the ticket along and suggest what comes next.

macOS on Apple Silicon · Free and open source, MIT



Implement this ticket.
Show the next dusk on the status page
Ticket 14, currently in open.
  • Thought for 4s
  • Run Move ticket 14 to Active
  • Edited 3 files +19−3
  • Claude wants to run a command
    npm test
  • Allowed oncenpm test
  • Run npm test42 passed
  • Run Open pull request #31

#14

  • Run npm test42 passed
  • Run Open pull request #31

The status page shows the next dusk, and #14 is in Review with pull request #31. While I was in there I noticed three things worth doing next.

    • Edited 3 files +19−3
    • Run npm test
    • Run Open pull request #31

    The next dusk sits under the beacon schedule. The diff is on the right.

    ChangesUncommittedBranch
    claude/next-dusk4e1c9a2+19 −3
    • ui/status/NextDusk.tsx+12
    • ui/status/StatusPage.tsx+5−1
    • server/dusk.ts+2−2
    ui/status/StatusPage.tsx+5 −1
    @@ -18,8 +18,12 @@ export function StatusPage
    18 <section className="status">
    19 <h1>{lighthouse.name}</h1>
    20− <BeaconSchedule beacons={beacons} />
    20+ <BeaconSchedule
    21+ beacons={beacons}
    22+ timeZone={keeper.timeZone}
    23+ />
    24+ <NextDusk place={keeper.place} />
    25 </section>
    server/dusk.ts+2 −2
    @@ -4,6 +4,6 @@
    4−export function nextDusk(at) {
    4+export function nextDusk(at, place) {
    5− return sunset(at, HOME);
    5+ return sunset(at, place);
    • Open localhost:5173
    • Click on the page
    • Read the console
    • Build Lighthouse
    • Launch dev.lighthouse.app
    • Tap e4
    • Read the screen's controls

    Browser
    localhost:5173/status
    Lighthouse
    LighthouseStatusLogs

    Tonight at Ness Point

    Next dusk19:42in 28 min
    BeaconOn
    Battery86%
    Last check19:12
    Keeper notified
    Device
    iPhone 17 Pro · iOS 26
    9:41

    Tonight

    19:42

    Dusk at Ness Point

    Start a chat from a ticket

    New chat writes the prompt from the ticket. Tick worktree, start, and the agent moves the ticket to Active. Each folder picks its board: Local, Trello or Jira.

    Linked both ways

    The chat shows its ticket, and the ticket lists its chats. The agent asks before it runs a command, and a ready pull request moves the ticket to Review.

    It suggests what comes next

    Follow-up work the agent spots waits above the composer. Start it in a new worktree, file it as a ticket, or swipe it away.

    Review beside the chat

    The uncommitted changes or the whole branch, file by file.

    A browser and devices you share

    The agent drives a browser and your iOS Simulator or Android emulator while you watch, and you can click and tap along.

    Boards

    Your board, wherever it lives.

    Connect a board to a project folder, and the agent works with it.

    LocalTrelloJira

    Works with

    The agents you already use.

    X Bench drives the Claude Code, Codex and Grok Build CLIs you already have signed in. Sign-in, models and transcripts stay with each agent. One model menu lists them all, and a chat can move to another agent's model and keep going.

    Claude CodeChatGPTGrok Build

    Also in X Bench

    And more.

    Routines

    A prompt on a schedule. Each run is a fresh chat in a new worktree.

    • Nightly testsDaily at 02:00 · GPT-6.1Next run tonight at 02:00
    • Ticket triageWeekdays at 08:30 · Sonnet 5.5Paused

    On-device dictation

    Hold Alt and speak. An on-device model writes it into the composer, and nothing leaves your Mac until you send.

    On-device

    From your phone

    Pair a phone with a QR code. Agents, files and chats stay on your Mac.

    No phone paired
    X Bench app icon

    X Bench

    Free and open source.

    macOS on Apple Silicon · Free and open source, MIT