Sharing a 'RAM' stack between human and agent to keep long revision work on track
alfcnz · x · 2026-11-18
alfcnz describes sharing a stack between himself and his agent: the set goal sits at the bottom, revision tasks are pushed on top, so detours still converge back to the goal. The screenshot shows a concrete working stack (section revisions, pending decisions, parked items). He notes the more he uses this, the more he builds friction-free custom tooling.
Related event: Dev Shares Stack-Based Shared RAM Workflow for Human-Agent Collaboration(2 posts)→
More from coding & agent
- aivoicebus 0.16.0 adds Grok Bot to its AI agent fleet via webhook — baditaflorin · 2026-11-18
- deadweight: a Rust CLI that measures wasted tokens in your Claude Code setup — JeremyCMorgan · 2026-11-18
- Shadow MCP services need governance: 'no policy means you're asking for failures' — colinmcnamara · 2026-11-18
- LangChain's GTM Agent: deals with agent-built sales docs advance 47% vs 16% — LangChain · 2026-11-18
- Trader wires Muse agents to execute CME futures trades, plans broker API for instant orders — CyborgTraderOFTAGI · 2026-11-18
- Qwen 3.8 27B vs Flash-Next vs DeepSeek V4.1 Flash: one-shot landing page build-off — jesdga95 · 2026-11-18