Dosu

Dosu

@dosu.dev

Dosu turns your codebase into a living knowledge base that every team member—from engineering to operations—can understand, so builders can build. http://go.dosu.dev/discord

34 followers12 following67 posts

Pinned

It's Dosu Drop Day! 🎃 🔌 Live context from connected MCP servers (beta) 🔔 Approve knowledge updates in Slack 🔎 Deeper research, with the slowest answers about 30 seconds sooner 🏠 A limited self-hosted trial when security review blocks hosted Dosu go.dosu.dev/drop-oct26-b...

Should Humans Review An AI Agent's Work? Our CEO's, Devin Stein, take: people are already overwhelmed with review. Reviewing small pieces of conflicting information is work nobody has time for. Let the agent's do it.

In our Vercel AI SDK replays, agents learned the same build rule across 59 sessions and 40 tickets. One Codex run traced a missing import to a dependency's missing compiled output. What knowledge should you save for the next agent? dosu.dev/blog/coding-...

Does your coding agent choose a skill from the task...or only when you name the skill? Try a fresh session without the conversation where you wrote the instructions. Our procedural memory guide explains what to check. dosu.dev/blog/procedu...

After internal tests, we saw three embedding models rank undated Celery and DBOS facts in the same order for June and December questions. Your coding agent needs the history behind a fact to judge when to apply it. dosu.dev/blog/semanti...

How much better would a coding agent actually perform if it had the right memories from the start? VibeMemBench tries to answer that before testing existing memory systems. Devin explains why that made the benchmark the best memory one so far.

Most AI memory benchmarks do not test for what real coding agents actually need to be good at: learning across long histories of work. But our team thinks VibeMemBench does and it is why it sits alone in S-Tier for Michael👇️

Your agent runs pytest again. In the last session, it learned that make test-int starts the database the tests need. That lesson may still be saved, but never retrieved. Before correcting your agent again, check what made it into context. go.dosu.dev/episodic-mem...

Knowing something and knowing how to do something are very different kinds of memory. EvoMemBench tries to measure both. Devin breaks down why that makes it interesting for real-world agents and where it still falls short for coding.

What if AI memory systems look bad because we’re measuring the wrong thing? Task completion alone doesn’t tell us much anymore. Did the agent learn from past work? Repeat old mistakes? Need the same human correction again? Michael thinks our benchmarks need to change.

It's Dosu Drop Day! 🎒 For our back-to-school edition, Dosu does the studying. When a coding session ends, Dosu writes down what your team would otherwise rediscover. 📝 Session-end study 🧾 Knowledge read cards 💳 Credits that go further go.dosu.dev/drop-sep26-bsky

Who reviews agent memory when people can’t keep up? Michael Mangus, Head of Product at Dosu, on trusting AI to maintain memory—and making mistakes easy to correct. Recording + transcript: dosu.dev/webinars/age...

A summary of a summary keeps getting further from the source. Michael Mangus, Head of Product at Dosu, explains how repeated summaries lose details in agent memory. Recording + transcript: dosu.dev/webinars/age...

Dosu reposted

Ever wonder what happens when you sign in to Netflix on your TV? You get shown a code, approve it on your phone, and never have to type in a password. Coding agents don't get that luxury, though. Learn about how we solved that problem in Dosu's CLI, and where we found our inspiration!

go.dosu.devHow to design a CLI login flow for coding agentsDesign a CLI login for coding agents with a ticket flow that pauses, resumes in a new process, and returns the next command in JSON. Learn how Dosu built it.

It's Dosu Drop Day! 🗄️ Your Claude Code, Codex, and Cursor logs hold answers you keep spending tokens on. Now, Dosu stores them. 1. Backfill your Library from agent logs 2. Configure Dosu by asking Dosu 3. Analytics on login 4. See what knowledge your agent used go.dosu.dev/drop-aug26-b...

We launched a new OSS project today called Decant! Decant reads the logs Claude Code and Codex write and splits each run into categories of Context, Planning, Code, and Communicating. We'd love to hear what you think and what you learn from your sessions. go.dosu.dev/decant-aug26-bsky

go.dosu.devIntroducing Decant: Insights for your Claude Code and Codex sessionsClaude Code and Codex log every session you run. Decant turns those logs into real numbers for what your agents did and how much it cost, without leaving your machine.

Dosu reposted

If you run an open-source project and aren't using @dosu.dev, you're missing out! Dosu's responses to new issues are really on point, and it's great to have them reference other issues and PRs, and brainstorm within an issue to make better decisions.

We built a Claude Code skill that generates project docs from source code. Then, we tested it on a FastAPI project. It caught stale AGENTS.md refs on the first pass and generated five files without inventing things it couldn't verify. Learn how to build your own: go.dosu.dev/doc-it-bsky

go.dosu.devA Claude Code Skill for Auto-Generating Project DocsGenerate your project's entire documentation layer from source code with a single Claude Code skill. Build /doc-it and run it against a real FastAPI project.

Also in this drop -> Doc Reviews get quite the upgrade. Edit proposed changes in place, see change summaries at a glance, and better quality updates across the board. Plus a new blog post on catching documentation drift with Claude Code and GitHub Actions.

One unspoken agreement among every engineering team is that someone will update the docs... later. So, we built a GitHub Actions workflow that catches doc drift on merge, and wrote down every sharp edge we hit. dosu.dev/blog/how-to-...

Also in this drop. MCP Server is available to everyone, one click for Cursor, one command for Claude. Plus a new case study where Bluefin went from 42-hour support response to 12 minutes across 139 repos!

Dosu reposted

We just launched ask.cncf.io at KubeCon! 300+ sessions, hallway conversations everywhere, questions faster than answers. Sound familiar? You can ask about CNCF projects, governance, or this week's schedule. Then, you can get answers WITH sources. We’d love to hear what you think of the experience!

ask.cncf.ioCNCF | DosuDosu is an AI teammate that lives in your GitHub repo, helping you respond to issues, triage bugs, and build better documentation.

Dosu reposted

How might you manage a massive global community that grows to 40k stars in one year with a small maintainer team? Docling figured out a way! Spoiler: they MAY have used @dosu-ai.bsky.social to help 😉 You can read about the whole story here! dosu.dev/blog/docling...

dosu.devHow IBM Research's Docling Manages Open Source Growth with DosuIBM's Docling scaled from 0 to 40K GitHub stars (as of October 2025) in one year with just 4 maintainers. Check out how Dosu reduced response time by 99% and automated 70% of issues.