AI coding session context lost when switching tools

“Show HN: Needle: We Distilled Gemini Tool Calling into a 26M Model Hey HN, Henry here from Cactus. We open-sourced Needle, a 26M parameter function-calling (tool use) model. It runs at 6000 tok/s prefill and 1200 tok/s decode on consumer devices. We were always frustrated by the little effort made towards building agentic models that run on budget phones, so we conducted investigations that led to an observation: agentic experiences are built upon tool calling, and massive models are o”

“Show HN: Total Recall – write-gated memory for Claude Code built this because I got tired of re-teaching Claude Code the same context every session. Preferences, decisions, “we already tried X,” “don’t touch this file,” etc. After a few days it starts to feel like onboarding the same coworker every morning. Most “agent memory” tools auto-save everything. That feels good briefly, then memory turns into a junk drawer and retrieval gets noisy. Total Recall takes the opposite approach: a write gate.”

“Show HN: Mesa – A collaborative canvas IDE built for agent-first development Hi HN - I'm Ryan a product designer who codes, and I built Mesa. Current IDEs feel wrong for the type of development being done now - the focus is still on files. Mesa puts the focus on the full workflow: your agent, terminal, browser, and files all live as equal nodes on a canvas with full multiplayer support. (think figma but for code) I was tired of the overhead of switching windows, tabs, and terminals across m”

“Ask HN: How do you cope with the broken rythm of agentic coding? I used to seek focus and concentration while coding. It was not always easy to reach this flow state but I knew it was possible. I am now using agentic coding quite a lot. The honeymoon is finishing and I am starting to dislike some facets of it. I think the main setback is the rythm. Writing some specs/prompts, launching the agent, confirming quite atomic actions and waiting 10 to 30 seconds until the next question/confi”

“Ask HN: $50 monthly budget, which coding models would you recommend now? I currently have a claude pro monthly subscription ($20) which I use for coding. It's been useful but I'm fatigued from optimising my work around it's session limits. There are so many choices and providers out there today but hard to get a good signal about what's good. I'm not looking for another Opus-level model but something reliable enough that it can follow TDD well.”

“Show HN: Unpack – a lightweight way to steer Codex/Claude with phased docs I've been using LLMs for long discovery and research chats (papers, repos, best practices), then distilling that into phased markdown (build plan + tests), then handing those phases to Codex/Claude to implement and test phase by phase. The annoying part was always the distillation and keeping docs and architecture current, so I built Unpack: a lightweight GitHub template plus docs structure and a few commands th”

“Show HN: OpenGem – A Load-Balanced Gemini API Proxy (No API Key Required) Hi HN! I built OpenGem, an open-source, load-balanced proxy for the Gemini API that requires absolutely no paid API keys. GitHub: https://github.com/arifozgun/OpenGem The Context: Like many developers, I was constantly hitting 429 Quota Exceeded errors while building AI agents and processing large payloads on free tiers. I wanted to build freely without calculating API costs for every test request. How ”

“Show HN:`npx continues` – resume same session Claude, Gemini, Codex when limited i kept hitting rate limits in Claude Code mid-debugging, then hopping to Gemini or Codex. the annoying part wasn't switching tools (copy-pasting terminal output doesn't bring tool-use context with it) — it was losing the full conversation and spending 10 minutes re-explaining what i was doing. so i built *continues*. it finds your existing AI coding sessions across five tools (Claude Code, GitHub Copilot, ”

“Show HN: VAEN – Package and import portable AI coding-agent Harnesses Hi HN, I built VAEN (an open source CLI) because I kept running into a boring problem with AI coding-agent workflows: the setup becomes useful, but then it is hard to move. A good, useful agentic harness consists of more than just instructions: skills, mcp servers and more. There should be a better way to share those than just .MD files, and that is why I created VAEN. What works: create a yaml, run the CLI commands as per the”

“Show HN: My AI agents bully each other to prevent context drift Most multi-agent systems fail the same way: agents drift apart across handoffs. By turn 3 they are working in different realities. By turn 5 they are repeating each other's mistakes and calling it parallelism. WUPHF is an open-source local-first office where AI coworkers run on your laptop, around a shared markdown + git LLM wiki the agents build. The wiki is the collective memory. The office around it keeps the team on the sam”