ComradeIQ
One objective. A coordinated team of AI specialists.
An AI command center that turns one objective into a coordinated workflow. A commander delegates to specialists while their progress appears in a live workspace.
Built and submitted to the OpenAI Build Week Hackathon. The project brings together orchestration, streaming progress, and downloadable deliverables in one interface.
Can one objective become a visible, coordinated workflow?
ComradeIQ makes AI delegation tangible: a commander organizes specialists, their work appears live, and the result becomes a downloadable artifact.
A coordinated team
Commander Atlas organizes Researcher, Writer, Formatter, Critic, Assembler, and final QA work.
Progress you can inspect
An agent graph, live activity stream, and expandable outputs expose the workflow as it runs.
Deliverables beyond chat
Markdown documents, themed PowerPoint decks, and shareable mission pages carry the work forward.
Give the commander a mission.
ComradeIQ was built for the OpenAI Build Week Hackathon. The starting idea is a command center: describe an objective and let a coordinator organize the steps needed to produce something useful. The experience pairs the task with a workspace where the user can see what is happening.
The product includes a fast chat path and more structured document, presentation, and research workflows. Research can opt into web sources; document work can produce Markdown; presentation work can produce a PowerPoint deck in one of four visual themes. The output is meant to leave the chat window.
Delegation needs boundaries.
Commander Atlas routes work through a dependency graph of specialist roles. A researcher’s output can feed a writer; formatting and critique can refine the material; an assembler and final QA step prepare the deliverable. Each specialist receives the relevant upstream material rather than one shared, ever-growing transcript.
Server-Sent Events stream progress into the interface. That gives the graph, activity console, and expandable agent outputs a practical purpose: they help explain which stage is active and what each stage produced. The stack combines Next.js, React, TypeScript, and artifact storage through Vercel Blob, with PptxGenJS for decks.
A demo has to survive production.
The Devpost write-up documents a concrete deployment failure: API routes returned errors in production because of bundling and Node file-tracing behavior, compounded by an eagerly imported PDF parser. The fix involved a stable build path, dependency externalization, and lazy imports. It is a useful example of the work between a locally working idea and a usable public demo.
ComradeIQ also explores smaller interactive experiences, including embedded YouTube results and chess with rules enforced by chess.js. These share the same workspace, while the main engineering story remains coordinated execution and inspectable outputs. Team authentication, broader connectors, and deeper evaluation are future directions described in the submission.
How it comes together.
Brief the commander
Describe the desired result and choose a suitable mode.
Delegate the work
Pass scoped inputs through the specialist dependency graph.
Inspect & refine
Watch streamed progress and inspect the outputs and critique.
Collect the artifact
Download a document or deck, or share the mission’s read-only page.
A closer look.
Explore the interface, the work, and the details behind it.
The orchestration is part of the interface.
ComradeIQ’s most useful idea is making coordination observable. A user can follow how an objective becomes an artifact, while the builder can reason about the boundaries between specialist steps.