Features

Everything your team and your coding agent need, in one stream

wakustream has a short feature list on purpose. Each piece exists because a chat-first, agent-driven workflow needs it.

Stream

Messages first, issues drawn on top

A project is a chat. People post text and screenshots. Paste or drop an image and it is attached. Nothing is required up front: no title, no priority, no component.

Quote replies that jump back to the original
Seven reactions, shown as counted pills
Issue chips on every message that belongs to one
Everything, Untriaged, or a single issue as the filter

The project stream with the issue rail on the left

Issues

Lasso, create, add to

Drag a box over messages on desktop or tap them on a phone. Create an issue from the selection or add it to an existing one. Issues move through Open In progress Done and are archived, never deleted. Done items leave the rail after a week and live on in History.

Selected messages with the Create issue bar

Two-way agent loop

Your coding agent is a member of the project

Claude Code, Codex and other MCP-capable agents connect with a project-scoped key. The agent reads issues as full threads, screenshots included, and posts back as a visibly different participant.

The important part is ask: a question the agent posts is marked Awaiting your reply and the first human reply clears it. wait_for_reply polls briefly and never blocks the agent.

Codex · Agent · 4h ago · INV-3

Quick question before I continue: should the header stay pinned while you scroll, or scroll away with the content? The design file shows both.

Reply here and I'll pick it up from your answer.

⏱ Awaiting your reply Reply in INV-3

MCP tools

What your agent can do

Eight tools, exposed over MCP, so they work the same in Claude Code, Codex, or anything else that speaks MCP. Permissions are enforced by wakustream, not by the agent.

list_issues

Open issues by default, or picked up, done, all.

get_issue

The whole thread in order, with the attached screenshots as images.

pick_up

Marks the issue In progress. The team sees "Codex picked up INV-3".

post_reply

Say what changed, where, and how to verify it.

ask

Post a question that shows as Awaiting your reply.

wait_for_reply

Wait up to two minutes for an answer. Returns "still waiting" rather than hanging.

set_status

Hand an issue back, or mark it done once verified.

complete

Closing summary plus Done, in one step.

# A typical session, from the agent's side
list_issues()                       → INV-3 Mobile header overlaps first card
pick_up("INV-3")                    → thread + 2 screenshots
ask("INV-3", "Pinned or scroll away?")
wait_for_reply("INV-3")             → "Maya: pinned, please"
complete("INV-3", "Fixed the sticky offset. Verify on iOS Safari …")

Dashboard

Unread, open, in progress, awaiting your reply and untriaged counts per project, with a 14-day activity pulse and the last message.

Read tracking

One marker per person per thread. Reading happens by looking. Unread shows in the rail, in the stream, in the tab title and on the app icon.

Mobile

Installable from the home screen. Camera button, on-device image downscaling, a drawer for the rail, and a composer that does not fight the iOS keyboard.

Projects and people

Invite-only accounts, per-project membership, and a project key that names every issue: INV-3, WEB-1.

Agent keys

Each project gets its own agent key. Shown once at creation, scoped to that project and nothing else, revocable at any time.

History and Copy prompt

Done issues stay searchable. Copy prompt renders any issue as text to paste into an agent that is not on MCP yet.

See it with your own project

Early access is open to a handful of teams running coding agents day to day.

Get early access