[ [object Object] ]

/// SECTION 01 — OVERVIEW
A macOS Electron control room for DHDTech.io contractors. The engineer signs in once, then the app runs and babysits Claude Code and Codex sessions against their own work: reviewing other people's pull requests, shepherding their own pull requests all the way through to deploy, picking up backend tickets from Jira, and assembling yesterday's standup. Cost, duration and verdict are recorded for every run, with PTO and invoicing alongside.
An engineer's day is spread across GitHub, Jira, Confluence, Slack, two AI CLIs and an invoicing portal. Review work stays invisible until it is late, and nobody can say what a pull request actually cost in tokens or in wall-clock time.
An Electron 44 app whose poller finds pull requests through the gh CLI and spawns one PTY per pull request running Claude Code, with a supervisor that respawns a dead session, freeze and resume, and a live cost ticker. A serial navigator drives one pull request at a time and reports its health, queue depth and remaining budget. Which modules an engineer sees is granted by the backend rather than chosen locally. The Report tab keeps every run's verdict, duration and cost over two SQLite databases — run history, and a disposable capped log store. Auto Develop scans active Jira sprints for backend tickets. What I Did Yesterday gathers a standup from GitHub, Jira, Confluence and Slack. Billing uploads invoices and downloads receipts, and PTO plans and tracks time off. The app lives in the menu bar and updates itself.
[ Call to action ]
Tell us the roles you need to fill and we'll get back within 24 hours.