Cursor, Codex CLI, Gemini CLI are powerful — but why do they still forget the task?
I use Cursor. I’ve tried Codex CLI. I’ve played with Gemini CLI.
They’re impressive at generating code.
They’re bad at remembering work.
Every new session starts with:
re-pasting requirements
re-explaining decisions
re-linking docs
re-defining scope
That’s not a model problem.
That’s a workflow problem.
In real dev teams, context lives in:
tasks
comments
docs
decisions
Not in someone’s clipboard.
So I’ve been experimenting with a task-first CLI flow:
blocpad task 12The AI pulls the task’s full context automatically and just continues the work.
No prompt gymnastics.
No “here’s the background again.”
Which leads to the debate:
Are tools like Cursor and Codex optimizing the chat interface…
when they should be optimizing context ownership?
Curious how other devs feel about this.
51 views
Replies
Totally agree this isn't about model memory, it’s about workflow design. Tools like Cursor or Codex are great at generating code, but if the context isn’t owned or linked to real tasks, every session feels like starting from scratch.
A task-first approach like yours makes a lot of sense context should live in tasks, docs, and decisions, not a clipboard. Curious to see how this approach scales with bigger teams!
BlocPad - Project & Team Workspace
@djbutterrock__ For larger teams, the focus is on scoped context (per project, per task) rather than global memory, so relevance stays high as usage scales. The challenge isn’t storing more context
it’s keeping it useful.