Devigner
Dev instincts. Designer eyes. No sacred rules.
Dev instincts.Designer eyes.No sacred rules.
How I keep Codex side chats and old tasks findable without losing work
Terminal Codex sessions scatter context across chats and tasks, making it hard to resume past work or hold several investigations at once.
Read articleThe latest 16 of 81 articles, oldest to newest.
Articles
All articles- WorkflowCodex CLI
How I keep Codex side chats and old tasks findable without losing work
Terminal Codex sessions scatter context across chats and tasks, making it hard to resume past work or hold several investigations at once.
- WorkflowCodex CLI
How I kept provider and pane control in Codex without losing flow
Replayed Codex conversations dropped reasoning summaries and steering messages could vanish mid-turn, making long sessions hard to trust.
- ContextClaude Code
Why does your resumed Claude Code session still lose recent turns?
Sessions that stop without a clean exit used to drop your latest turns on resume; the newest build now preserves them.
- WorkflowCodex CLI
When to use incremental tool updates instead of legacy streaming?
Codex tool updates on Google Cloud Vertex AI previously arrived in batches rather than as they happen; incremental sending is now the default, with a flag to opt out.
Thoughts
All thoughtsI once wired a search tool directly to one provider and paid for it later: switching models meant rewriting the whole integration. Standardized gateway tools let me swap models without touching my agent's tooling code. Abstractions you don't own are worth renting when they sit at the integration boundary.
Every AI coding session leaves behind a new Vercel project, and I was deleting them by hand months later when the free tier filled up. Setting expiry on new projects via the CLI fixed it, but the real lesson is that throwaway output needs a lifecycle from the start. If I generate something disposable, I should decide when it dies the moment I create it.
I let scripted opencode runs pile into my session list until finding the good conversations felt like inbox triage. One flag, --archived at launch, and machine runs stay out of sight by default. Tools that mix automation and human traffic need a separation knob from day one, not after the noise wins.
Workflow field notes, straight to your inbox
Join readers getting workflow field notes and reusable assets in every issue. No spam, unsubscribe anytime.