Not exactly - the feature works, and the local parsing decision is the right architectural call. What I'm skeptical about is the manual curation ceiling. The developers who'd benefit most are running multiple Claude Code sessions a day. They'll upload three sessions in the first week because it's novel. Then stop. The sessions keep accumulating in ~/.claude/projects/.
The missing piece isn't the UI. It's the evaluation layer that runs before you ever see the session — automatic extraction, scoring, surface the high-signal moments for review. DEV.to built the right first 10%. The rest is a pipeline problem, not a design problem.
The effort problem and the curation problem are the same problem. People don't stop uploading because curation is hard. They stop because the return isn't visible. You put in the work, you get a post that maybe three people read. The feedback loop is too weak to sustain the habit.
That's why the pipeline has to run before you see the session not after. If the evaluator surfaces two insights worth keeping from a four-hour session automatically, the effort cost drops to minutes and the return is immediate - something retrievable in your next session, not a post you hope someone finds.
"Whipped up in an afternoon" is probably fair. The local parsing was thoughtful. Everything upstream of it wasn't.
I actually think we're solving for different problems here, and I really appreciated your post's thoughtful deep dive into the larger problem space since there's a lot of opportunities there. Chat-knowledge is also a very clever tool.
Ultimately, the goal of DEV's Agent Sessions was not explicitly to provide a new layer of knowledge to agents.
The goal was to enrich the content on DEV that already showcases people's work with coding agents. The most common way that people were showcasing these interactions was with screenshots, and this was meant to be a solution for that specifically, especially as our volume of content around AI workflows has grown drastically.
I agree with you that the curation is a bit unwieldy, especially with very long sessions or a lot of parallel sessions. I have some ideas around better recommendations of what to include in your curated sessions as part of the upload workflow as well.
I also do think there are opportunities in the future to make sessions or even content on DEV a part of your workflow with coding agents, via some kind of agent-friendly skill or tool (MCP/CLI/etc), which could help with some of the knowledge commons issues you're describing.
That's a fair correction and worth making clearly. I was reading Agent Sessions through the lens of the knowledge commons problem which was my frame, not yours. Screenshots as the dominant format for showcasing agent workflows is a real problem and a more immediate one than what I was writing about.
The MCP/CLI direction is exactly where I'd hope this goes. The gap between "showcasing work" and "work feeding back into future sessions" is smaller than it looks architecturally. The capture layer is mostly already there. What's missing is the curation signal that decides what's worth injecting into future context versus what's noise. That's the problem Foundation's evaluator is trying to solve at the session level.
If DEV ever wants to experiment with an agent-friendly knowledge layer, I'd be genuinely interested in that conversation.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
So you think that dev.to's feature is a "nice idea" but it's not gonna be practically usable?
Not exactly - the feature works, and the local parsing decision is the right architectural call. What I'm skeptical about is the manual curation ceiling. The developers who'd benefit most are running multiple Claude Code sessions a day. They'll upload three sessions in the first week because it's novel. Then stop. The sessions keep accumulating in ~/.claude/projects/.
The missing piece isn't the UI. It's the evaluation layer that runs before you ever see the session — automatic extraction, scoring, surface the high-signal moments for review. DEV.to built the right first 10%. The rest is a pipeline problem, not a design problem.
But not only a curation problem - as you say:
"They'll upload three sessions in the first week because it's novel. Then stop"
It takes effort to do, and without tangible benefits, people won't do it ...
Curation (the other 90%) is then the next hurdle.
I see it a bit as a "cool feature" which they whipped up in an afternoon, but which they didn't really think through enough.
The effort problem and the curation problem are the same problem. People don't stop uploading because curation is hard. They stop because the return isn't visible. You put in the work, you get a post that maybe three people read. The feedback loop is too weak to sustain the habit.
That's why the pipeline has to run before you see the session not after. If the evaluator surfaces two insights worth keeping from a four-hour session automatically, the effort cost drops to minutes and the return is immediate - something retrievable in your next session, not a post you hope someone finds.
"Whipped up in an afternoon" is probably fair. The local parsing was thoughtful. Everything upstream of it wasn't.
I actually think we're solving for different problems here, and I really appreciated your post's thoughtful deep dive into the larger problem space since there's a lot of opportunities there. Chat-knowledge is also a very clever tool.
Ultimately, the goal of DEV's Agent Sessions was not explicitly to provide a new layer of knowledge to agents.
The goal was to enrich the content on DEV that already showcases people's work with coding agents. The most common way that people were showcasing these interactions was with screenshots, and this was meant to be a solution for that specifically, especially as our volume of content around AI workflows has grown drastically.
I agree with you that the curation is a bit unwieldy, especially with very long sessions or a lot of parallel sessions. I have some ideas around better recommendations of what to include in your curated sessions as part of the upload workflow as well.
I also do think there are opportunities in the future to make sessions or even content on DEV a part of your workflow with coding agents, via some kind of agent-friendly skill or tool (MCP/CLI/etc), which could help with some of the knowledge commons issues you're describing.
That's a fair correction and worth making clearly. I was reading Agent Sessions through the lens of the knowledge commons problem which was my frame, not yours. Screenshots as the dominant format for showcasing agent workflows is a real problem and a more immediate one than what I was writing about.
The MCP/CLI direction is exactly where I'd hope this goes. The gap between "showcasing work" and "work feeding back into future sessions" is smaller than it looks architecturally. The capture layer is mostly already there. What's missing is the curation signal that decides what's worth injecting into future context versus what's noise. That's the problem Foundation's evaluator is trying to solve at the session level.
If DEV ever wants to experiment with an agent-friendly knowledge layer, I'd be genuinely interested in that conversation.