What it does
Coding agents work for one developer; TeamHQ is where the whole engineering org converges to decide what code change ships next. Built for the Nozomio Hackathon (Track 4: The Company Brain). Every change — an upstream release break, a product feature, a convention dispute — starts as a card that is visible to everyone, actionable by the right roles, synthesised from each team's brain, verified in a sandbox, and shipped by the agent of your choice.
- Live demo: web-nine-lemon-57.vercel.app
- Target repo where the agent opens PRs: kitrakrev/teamhq-hero (example: PR #4)
How it works
Trigger → Acceptance criteria → Per-role questions → Per-team plans → Sandbox → Quorum gate → Real PR
- Each step emits a card to InsForge; the web UI polls and streams them every 2 s.
- Per-team plans fuse each team's own brain (Hyperspell: Slack, Notion, GitHub, Linear) with world context from Nia and repo state.
- The quorum gate is on by default: the PR cannot ship until every team lead approves their plan card.
- A bundled MCP server exposes 7 tools so Claude Code, Codex, Cursor or Devin can act as the executor; decision history is durable in InsForge.
Tech stack
Python agent loopHyperspellNiaTensorlakeInsForgeNext.js 16Tailwind 4VercelMCP