SHARED KNOWLEDGE. COLLECTIVE MOMENTUM.
Bring your conversations, project knowledge, and AI agents into one place. See what changed, decide what matters, and move the work forward with shared understanding.
THE WHOLE PICTURE. THE NEXT MOVE.
Work happens across conversations, documents, repositories, and tools. Coflow connects that knowledge to the people and agents who need to act on it.
Take the product tourFeeds and Radar bring the work into view.
People, Flo, and your agents share the context.
Knowledge carries into the next conversation.
01 / INSIDE COFLOW
Explore the actual app, from the first signal to the next handoff.
A living brief for a workspace, project, or topic. Read the same update through the lens of sales, design, engineering, or your own audience, with the original evidence close at hand.
Choose who you’re reading for. Get the implications in language that fits.
Open the original sources behind an update.
Hand a feed item to Flo with its context attached.
Radar looks across the work you can access, bringing recent changes and issues needing attention into one view. Start with the whole picture, then narrow it when you need to.
Accessible workspaces and projects come into view together.
Review decision changes, coordination issues, and context drift.
Inspect sources, follow a finding, or mark it resolved.
Work through a question with Flo, Coflow’s built-in assistant. Bring the relevant project knowledge, a feed update, or a finding into the conversation and keep going from there.
Use your connected knowledge and conversation context.
Follow references back to the material behind an answer.
Turn an update into a question, a discussion, or a next step.
A focused place to work with a coding agent that has your project context. Keep source, conversation, previews, and a visual canvas close to the work you are building.
Bring the project’s knowledge into your coding conversation.
Draw, drop an image, annotate, and send a visual brief to your agent.
Expand the canvas to fill the window; choose paper or black.
Capture a runbook as a procedure, a diagram as an editable visual, and a plan as work to follow. Each context type has a creation flow shaped around what it needs.
Docs, runbooks, diagrams, handoffs, todos, plans, tickets, and media.
Capture triggers, steps, checks, and recovery in a runbook.
Turn a useful message into a decision, lesson, preference, or document.
Focus a channel or direct message on the workspaces, projects, and knowledge relevant to the conversation. Pin the details worth keeping close, then change focus as the work evolves.
Choose the workspace or project you want to work on.
Pin documents, decisions, plans, and other context.
Conversation scope guides attention. Sharing controls who has access.
Bring connected work into Coflow, from repository activity and project tracking to documents, design, and business signals. Choose where a connection is available and whether Flo and your agents can read it.
GitHub, GitLab, Bitbucket, Notion, Linear, Jira, Stripe, and PostHog.
Connect an open Paper Desktop design through its local MCP server.
Set workspace access, resource selection, and agent read access.
Share a workspace, project, or feed with selected teammates and give each person read or read/write access. Choose broader team access when that is what the work calls for.
Choose teammates and set their level of access.
Use private channels and control who joins the conversation.
Creators and workspace owners and admins retain their management access.
One connected system. Explore a feature above, then see how your team brings it all together below.
02 / THE PEOPLE BEHIND THE WORK
From an early idea to a release, Coflow gives the conversation, the knowledge, and the people doing the work a shared home.
CONVERSATION WITH CONTINUITY
Talk in channels, follow a thread, work in a direct message, or jump into a huddle. Bring an agent into the conversation with the knowledge it needs.
See conversation contextWork with Claude Code, Codex, goose, or another ACP runtime. Give agents a place on the team and follow their activity alongside the conversation.
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, choose who can access it, and connect the tools each team relies on.
Explore access and sharingA DAY IN COFLOW
A release date moves. Here’s how the same knowledge can travel through the work.
A project feed brings the update into view. Radar surfaces a decision change that needs attention.
Feeds + RadarBring the update to Flo. Discuss the implications with your team using the original sources.
Flo + conversationsWork through the code change with an agent. Use a canvas or screenshot to explain the intended result.
ContextCode + canvasUpdate the runbook, capture the decision, and create a handoff with the context the next step needs.
Knowledge + handoffs
03 / POWERED BY CONTEXTSTREAM
Coflow is where people and agents work together. ContextStream connects the knowledge behind that work, from source code and documents to decisions, lessons, and past sessions.
Discover ContextStreamSearch across code, documents, and project memory.
Bring relevant decisions and lessons into the next session.
Carry the background, current state, and next steps forward.
A FEW THINGS TO KNOW
Coflow brings project knowledge, conversations, and agents together for the whole team. Product, design, operations, and engineering can follow relevant work, ask Flo, and keep knowledge up to date. ContextCode adds a dedicated environment for coding with an agent.
Coflow is the place where your team talks, follows work, and collaborates with agents. ContextStream provides the connected knowledge and memory behind it. Together, they bring project context into daily work and carry it between sessions.
No. Choose the people who can access a workspace, project, or feed and set read or read/write permissions. Private channels control participation in conversations. Creators and workspace owners and admins retain their management access. Narrowing a conversation’s context changes its focus; it does not grant additional access.
Connect GitHub, GitLab, Bitbucket, Notion, Linear, Jira, Stripe, and PostHog. Paper connects through Paper Desktop’s local MCP server with a design open. Each connection has its own setup, workspace scope, and agent read setting.
Coflow supports Claude Code, Codex, goose, and ACP runtimes, alongside Flo. Join a hosted community or run your own Coflow relay. Your runtime and connected services may require their own accounts and configuration.
THE NEXT CHAPTER IS SHARED
Your people. Your agents. Everything you know, ready to work.
Available for macOS and Linux. Windows preview.