Early access

Task management for
hyper-agile agentic coding teams

A shared stream where your team posts requests and screenshots, groups them into issues with a drag, and hands them to Claude Code or Codex. The agent does the work and asks its questions right there in the thread. No tickets, no forms, nothing pasted into a terminal.

The wakustream project stream: team messages on the left rail grouped into open, in progress and done issues, with Claude asking a question marked Awaiting your reply
Why

Issue trackers assume a human will do the work

When an agent does the work, the bottleneck moves. The agent needs context the way a teammate gets it: the chat, the screenshots, the follow-ups. And it needs to ask a question without someone babysitting a terminal. wakustream is a stream first and a tracker second.

1

Chat like you already do

Messages and screenshots are the primary thing. Nobody fills in a form to report a bug. Partners post from their phone.

2

Draw an issue over the chat

Drag a box around a few messages, click Create issue. The thread, with its images, becomes the issue. Nothing gets retyped.

3

Your coding agent picks it up

Claude Code, Codex or any MCP-capable agent lists open issues, reads the thread and screenshots, does the work, and posts what it changed and how to verify it.

The loop that matters

The agent asks. You answer in the chat. It carries on.

Agents surface decisions mid-task. In wakustream that question lands in the issue as an agent bubble marked Awaiting your reply. The person already chatting in that issue answers there. The agent gets the answer on its next read and keeps going.

No Slack ping, no terminal prompt someone has to be sitting at.

Issue INV-3 in progress: Claude has posted a question with an Awaiting your reply badge and a Reply in INV-3 link
Triage without the ceremony

Lasso messages into an issue

Drag a selection box over the stream, or tap messages on a phone. Create a new issue or add them to an existing one. A message belongs to one issue, so nothing gets duplicated or silently moved.

Loose messages stay in an Untriaged view until someone decides what they are.

Three messages selected with a drag box, and a floating bar offering Create issue or Add to an existing issue
Done means verified

Every issue ends with a receipt

When the agent finishes, it posts what changed, where, and how to check it, then marks the issue Done. The person who reported it confirms in the same thread. The whole history stays attached to the issue.

Issue INV-1 marked done: Claude's closing summary lists what changed and how to verify, followed by Maya confirming it works
Across every project

One dashboard, honest numbers

Unread messages, open issues, questions waiting on you, untriaged chatter, and a 14-day pulse per project. Open a project and you are in its stream.

  • Per-person read tracking, so "new" means new to you
  • Tab title and app badge show what is waiting
  • Quote replies and a small fixed set of reactions
The wakustream dashboard: tiles for unread, messages today, open issues, awaiting your reply and untriaged, above a table of projects
Phones are first-class

Built for the partner on the go

The people who spot problems are often not at a desk. wakustream works as an add-to-home-screen app: a camera button on the composer, images downscaled on the device before upload, and a drawer for the issue rail.

wakustream on a phone: the Invoicing app stream with Claude's question and the message composer

Give your coding agent a seat in the conversation

wakustream is in early access with a small number of teams. Tell us about yours.