COFLOW FOR DESKTOP
One desktop app for your conversations, your AI agents, and everything ContextStream knows about your projects. See what changed, ask what it means, and move the work forward, with the whole backstory in reach.
macOS (Apple silicon & Intel) · Linux · Windows preview · All downloads
THE WHOLE PICTURE. THE NEXT MOVE.
Work happens across conversations, documents, repositories, and tools. Coflow brings it into one place on your desktop, and ContextStream remembers it, so every person and every agent starts from what the team already knows.
Take the product tourStream and Radar bring the work into view.
People, Flo, and your agents share the same context.
ContextStream carries it into the next conversation.
01 / INSIDE THE DESKTOP APP
Real captures from the Coflow desktop app, from the first signal to the next handoff.
A living brief for a workspace, project, or topic. ContextStream turns decisions, docs, and activity into updates you can actually read, framed for engineering, sales, design, or whoever you’re reading for, with the original evidence one click away.
Flo reframes each update for the people you’re reading for.
Open the original update and every source behind it.
Mark updates helpful, dismiss them, or quiet a whole kind.
Radar looks across every workspace and project you can access and surfaces what needs you: a decision that moved, work that now conflicts, context that drifted. Start with the whole picture, then narrow it when you need to.
Every accessible workspace and project comes into view together.
Decision changes, coordination issues, and context drift, ranked.
Inspect sources, follow a finding, or work it through with Flo.
Flo is Coflow’s built-in assistant, grounded in your ContextStream memory. Ask about a project, drop in a document or an image, or bring a stream update or Radar finding into the conversation, and get an answer that cites where it came from.
Answers draw on your projects’ decisions, docs, and code.
Every claim links back to the material behind it.
Documents, images, stream updates, and findings become context.
Point any channel or direct message at the projects it’s about. One search finds any workspace or project you can access, and from then on Flo and your agents in that conversation work from exactly that context.
Search every workspace, project, and repository at once.
Connect several projects and pick the primary one.
Scope guides attention. Sharing still decides who can see what.
See all the ContextStream workspaces and projects you can reach, organize them your way, and set the default a conversation starts from. Star what you use, hide what you don’t, and jump into any project’s context.
Workspaces and projects, with repositories and paths at a glance.
Star, hide, and sort; choose grid or list.
Open access for any project right from its card.
Capture a runbook as a procedure, a diagram as an editable visual, a plan as work to follow. Everything you add goes into ContextStream, so it shows up the next time a person, Flo, or an agent needs it.
Docs, runbooks, diagrams, handoffs, todos, plans, tickets, and media.
Turn a message into a decision, lesson, preference, or document.
Preview Office files and PDFs in the app and save their text as context.
A focused place to build with a coding agent that already has your project’s context. Keep the source, the conversation, previews, and a visual canvas side by side.
Your coding agent starts from the project’s decisions and code.
Draw, drop an image, annotate, and send a visual brief.
Claude Code, Codex, Cursor, goose, Amp, or any ACP runtime.
Connect repositories, documents, planning, and business tools. ContextStream keeps what they know in sync, and you decide which workspaces can use each connection and whether Flo and your agents may read it.
GitHub, GitLab, Bitbucket, Linear, Jira, and Notion.
Microsoft 365, Google Workspace, Dropbox, and Box.
Stripe, PostgreSQL, and an open Paper design through its local MCP server.
Share a workspace, project, or stream with selected teammates and give each person read or read & write access. Flo and your agents respect the same boundaries, so nobody learns something they couldn’t already see.
Choose teammates and set their level of access.
Agents never share project knowledge with people who lack access.
Private channels decide who is in the conversation at all.
One connected system. Explore a feature above, then see what ContextStream adds underneath.
02 / POWERED BY CONTEXTSTREAM
Coflow is where your team and your agents work. ContextStream is the memory underneath: it indexes your code, documents, and tools, remembers every decision and lesson, and hands the right context to whoever needs it next, person or agent.
Discover ContextStreamRepositories, documents, and every connected integration.
Decisions, lessons, plans, and sessions, searchable and access-aware.
Stream, Radar, Flo, and your agents, grounded in all of it.
Decisions, lessons, preferences, plans, and runbooks are captured once and surface on their own when the work touches them again.
Find the function, the doc, or the decision behind the work, across every indexed repository and document, in one query.
Flo and your agents cite the sources they used, so you can check the thinking before you act on it.
Every answer is limited to what the person asking can see. Narrowing a conversation’s scope never widens anyone’s access.
The ContextStream MCP server gives Claude Code, Cursor, and Codex the same memory Coflow uses, so work carries between the app and your IDE.
Carry the background, current state, and next steps from one session, teammate, or agent to the next.
03 / THE PEOPLE AND AGENTS BEHIND THE WORK
From an early idea to a release, Coflow gives the conversation, the knowledge, and everyone doing the work a shared home on your desktop.
CONVERSATION WITH CONTINUITY
Talk in channels, follow a thread, work in a direct message, or jump into Meet. Bring an agent into any of them with exactly the context it needs, and let opt-in meeting notes land in your stream afterwards.
See conversation contextGive Claude Code, Codex, Cursor, goose, Amp, or any ACP runtime a place on the team. Message them directly, add them to channels, and follow their work alongside everyone else’s.
Start from a schedule, a webhook, or channel activity. Connect triggers, conditions, and actions to keep recurring team and agent work moving with a process you can inspect and refine.
Organize knowledge by workspace and project, give each channel its own icon and color, and choose who can access what.
Explore access and sharing
A DAY IN COFLOW
A release date moves. Here’s how the same knowledge travels through the work.
The project’s stream brings the update into view. Radar flags two workstreams that now depend on it.
Stream + RadarBring the update to Flo, then focus the team’s channel on the affected projects and talk it through.
Flo + Narrow the ScopeWork through the code change with an agent that already knows the project. Sketch the intended result on a canvas.
ContextCode + canvasUpdate the runbook, capture the decision, and hand off with the context the next step needs.
Knowledge + handoffsA FEW THINGS TO KNOW
ContextStream is the memory and search layer underneath Coflow. It indexes your repositories, documents, and connected tools, remembers decisions, lessons, and plans, and gives Flo, your agents, Stream, and Radar the context they work from. The same memory is available in your editor through the ContextStream MCP server.
No. Product, design, operations, and engineering all follow relevant work in Stream and Radar, ask Flo, and keep knowledge current. ContextCode adds a dedicated environment for building with a coding agent.
No. Choose the people who can access each workspace, project, or stream and set read or read & write permissions. Private channels control who is in a conversation. Flo and your agents only use what the person asking can see, and narrowing a conversation’s scope never grants additional access.
GitHub, GitLab, Bitbucket, Linear, Jira, Notion, Microsoft 365, Google Workspace, Dropbox, Box, Stripe, and PostgreSQL. Paper connects through Paper Desktop’s local MCP server with a design open. Each connection has its own setup, workspace access, and agent read setting.
Yes. Coflow works with Claude Code, Codex, Cursor, goose, Amp, and other ACP runtimes, alongside Flo. Join a hosted community or run your own Coflow relay. Your runtimes and connected services may need their own accounts and configuration.
macOS on Apple silicon and Intel (signed and notarized) and Linux as a .deb or AppImage. A Windows preview build is also available. The app updates itself when a new version ships.
THE NEXT CHAPTER IS SHARED
Your people. Your agents. Everything you know, ready to work.