Context Flow Weekly Update

Hey everyone, welcome to the first of what we’re hoping will become a weekly cadence of contextflow updates.

For anyone new here: contextflow is a tool for keeping project context current across the places where work already happens, like Discord, documents, chats, code, and meeting notes. The goal is to help teams answer “what’s going on?” without digging through five different tools or relying on one person to remember everything.

We’re building this because project context is usually scattered, stale, or trapped in conversations that are hard to search later. AI can help with that, but only if it has the right context and the context stays up to date. That’s the core idea behind contextflow: collect the important signals from your project, turn them into useful project documents, and keep those documents alive as the work changes.

The biggest focus this week was onboarding.

The dashboard is useful once you understand the shape of contextflow, but we heard from a couple users that, on first visit, they weren’t always sure where to start. There’s a lot of information available at once, and that can make the first step feel less obvious than it should.

So we spent time making the first-run experience much more guided. The goal is simple: creating a project, connecting a source, and getting to a useful first project document should feel dead simple. You should not be able to get it wrong.

We also put a lot of work into making contextflow genuinely useful inside Discord itself. Since contextflow is now an official app in the Discord App Directory, we wanted the bot to feel like a real product surface, not just a shortcut back to the web app.

You can now start from Discord with /context setup, connect or create a workspace, choose the source channel contextflow should read from, choose where updates should go, and kick off the first project document sync. Once setup is done, /context ask lets people ask questions against the project context directly from Discord.

On the web side, onboarding now does a better job guiding you through source setup, preserving where you were after Discord OAuth, showing source provider logos, and keeping the Sources tab cleaner and easier to scan. The first document generation flow also keeps checking until the initial project documents are ready, so the handoff feels smoother.

We added voice input for text sources too. You can record source material with your microphone, see recording feedback, and have it transcribed into contextflow instead of typing or pasting everything manually.

We also finished a lot of the backend plumbing for GitLab sources. GitLab is not available in production yet, but the core ingestion path is now in place: connecting a repo, reading commit metadata and commit messages, and using that history as source material for project documents.

There were also reliability improvements under the hood around Discord setup, source syncing, document updates, and messy real-world ingestion.

What’s next

We’re going to keep pushing on additional sources. GitHub, Google Docs, Jira, Slack, and custom integrations are all likely candidates for what we work on next.

We’re also going to keep testing reliability hard. A big part of the product is trust: if contextflow is going to help teams understand what changed and what matters, it needs to work consistently and at a high level of quality.

We may also start streaming some of these development sessions on Twitch under the same username. A lot of the work right now is product design, integration plumbing, and testing against real project messiness, and it could be fun to build more of that in public.

Thanks for following along. This week moved contextflow closer to the goal: meet teams where their work is already happening, keep the important context current, and make it easier to ask “what’s going on?” without digging through a pile of tools.