EN中 GitHub

Features

Plan with your team. Build on your own machine.

SuDuo connects your team's requirements board and discussion rooms to the Codex on each developer's computer. Here is what it does today, with screenshots of the real app.

Requirements board and pages

Your team's requirements sit on one board, from Draft to Done, so everyone can see who is on what and how far along it is. Each requirement has its own page with the description, comments, attachments and activity in one place.

  • Board and list views, seven statuses, assignees and REQ-n numbers
  • Requirement pages with Markdown, comments, attachments and a full activity history
  • Confirmed versions publish the agreed set of materials, so everyone builds from the same files
The requirements board, with a column for each status (Draft, Refining, Ready, In development and so on); each card shows the number, title, summary and assignee

Project and requirement rooms

Every project comes with a room that the whole team is in, and any requirement can have rooms of its own. The back-and-forth stays next to the work instead of getting lost in a chat app.

  • Threads, @mentions, files and video
  • A requirement's page shows its rooms and their latest message
  • Floating room windows that stay open while you move around
  • Messages and files are stored on the server your team runs
The Order Center project room, with messages from four teammates about release timing and testing, including @mentions

Shared agents

Share your Codex into a room, and teammates can @ it with questions. It works read-only on your computer, in the project's code folder, and replies in the thread under their message for everyone in the room to read. A product manager with no code on their laptop can still ask how something works today.

  • You choose which rooms to share it in and for how long, and you can stop sharing anytime
  • Read-only: it answers questions, drafts plans and can look things up online, but doesn't change your code
  • The message shows Queued, Running or Done; open it to read the full answer and see what the agent did
  • Its answers and steps are posted in the room, and they can quote code

Team server · Room

Maya Lin

@Alex Chen's Codex When a payment callback fails, do we retry it automatically yet?

Alex Chen's CodexDone · Answer in the thread

Read-only
Read-only

Alex's computer · Project folder

  1. Reads the message and the discussion before it
  2. Looks through the code, read-only
  3. Posts the answer back to the thread

The owner turns sharing on, chooses how long it lasts, and can turn it off anytime.

Start work from a requirement

Click Start session on any requirement, and SuDuo starts a Codex session in that project's folder on your computer. The requirement card and SuDuo's tools come with it, so Codex can read the requirement, its comments and attachments, and write its conclusions back. No copying and pasting.

  • Choose a project's local folder once, then start from any requirement
  • Sessions stay linked to their requirement, and the requirement page lists them
  • If the requirement changes after you've started, My work tells you
  • Code, sessions and model credentials stay on your computer
A requirement page with the background, what to build, acceptance checks, materials and confirmed versions, and rooms on the left; status, assignee, the local folder and local sessions on the right; Start session at the top right

Approvals and file changes

Everything Codex does lands on one timeline, from the actions waiting for your approval to the commands it ran, the files it changed and their diffs. Going back is easy too, with checkpoints you can restore in one click.

  • Approvals, commands, file changes and diffs in one timeline
  • Git checkpoints, with an optional checkpoint before every turn and one-click restore
  • Skills, @ file references and a message queue in the composer
  • File paths in answers open a preview at the right line, or open in VS Code
A local session with the session list on the left, the conversation and composer in the middle (with the approval mode and model below the composer), and the inspector panel on the right with Changes, Requirement, Environment and Files tabs

My work and Overview

My work gathers what needs you across every project, and Overview shows a project's status breakdown, flow and stalled requirements. Open these two pages first and you know where to start.

  • My work: approvals waiting for you, new comments, requirements that changed since you started, plus your requirements, your sessions and recent activity
  • Overview: how many requirements are in each status, status flow over the last 7 or 30 days, stalled requirements and recent activity
My work, with a new comment and a requirement that changed since you started under Needs your attention, then my requirements grouped by status, sessions and recent activity
Overview, with the number of requirements in each of the seven statuses, a bar chart of status changes over the last 7 days, stalled requirements and recent activity

English and Chinese interface

The interface is available in English and Simplified Chinese. It follows your system language by default, and you can change it under Settings → Appearance → Language. Each person picks their own, and the choice is saved in their browser, so one team can work in both.

  • Only SuDuo's own text changes language; requirements, comments, messages and Codex's answers are shown as written, never translated
  • SuDuo asks Codex to reply in the language you write in
  • The command line and the server script follow the system language too; set SUDUO_LOCALE to choose
The requirements board in English
English
The requirements board in Chinese, with a Chinese set of demo data
简体中文

Also included

  • Light and dark themes, or follow the system
  • Keyboard shortcuts and a command palette
  • A hint when the client and server versions differ

Run it on your own server

The server installs with one command on Linux with Docker. The client runs from source on macOS and Windows.

Deploy to your serverView the source on GitHub