--- title: Your coding agent remembers the conversation. It has no... description: A developer describes a common but underappreciated failure mode with AI coding agents: sessions persist conversation history but not filesystem state, so... canonical: https://daily.dev/posts/your-coding-agent-remembers-the-conversation-it-has-no-idea-your-branch-moved--lcbaazklp twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Your coding agent remembers the conversation. It has no idea your branch moved. | daily.dev og:description: A developer describes a common but underappreciated failure mode with AI coding agents: sessions persist conversation history but not filesystem state, so... og:url: https://daily.dev/posts/your-coding-agent-remembers-the-conversation-it-has-no-idea-your-branch-moved--lcbaazklp og:image: https://api.daily.dev/og/posts/LCbaAzKLP.png og:image:alt: Your coding agent remembers the conversation. It has no idea your branch moved. og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Your coding agent remembers the conversation. It has no idea your branch moved. **[JigJoy](https://daily.dev/sources/jigjoy)** · [@telvinteum](https://daily.dev/telvinteum) · 5 min read · 3 upvotes · 5 comments ## Summary A developer describes a common but underappreciated failure mode with AI coding agents: sessions persist conversation history but not filesystem state, so resuming a session after repository changes causes the agent to confidently act on a stale world model. The post introduces Limboo, a local-first desktop workspace built to solve this by treating the environment as infrastructure — reconciling the git worktree on session resume, maintaining a local project knowledge base (SQLite/FTS5, offline), and enforcing a unified permission model across multiple agents. v1.5.1, MIT-licensed, built with Electron + React + TypeScript, with no backend or telemetry. ## Content Here's a failure mode I hit constantly, and I don't think it gets talked about enough. You spend an afternoon with a coding agent working through something real. It's going well. You close the laptop. Two days later you reopen the session and ask it to finish up. It remembers everything. What it decided, what it already tried, the approach you told it to avoid. The transcript is perfectly intact. And it's quietly, confidently wrong — because while you were away, a teammate merged a refactor that moved the module it was editing, a dependency went up a major version, and someone rebased the branch out from under the diff. Sessions persist the conversation, not the filesystem. So the agent resumes with a perfect memory of a world that no longer exists. You spend the first several turns dragging it back to reality. The bad cases are the ones where you don't notice, and it writes code against an API that got deleted on Tuesday. That isn't a reasoning failure. The model is fine. It's a **missing system** — nothing in the stack is responsible for the _world_ the agent acts in. ## Watching an agent isn't the same as grounding it The tools that grew up around these CLIs mostly solved a different problem: visibility. Run several agents at once, give each one its own branch, review the diffs inline, keep the transcripts tidy. That's genuinely useful, and I use those ideas too. But underneath the dashboards, the environment is still ambient. Whatever changed between turns is still the agent's problem to rediscover. And every provider keeps its own memory, its own permission model, its own config — so switching agents means starting over. So I've been building **Limboo**, a local-first desktop workspace, around one bet: the environment deserves to be actual infrastructure, owned by the app, with its own state. ## What that means concretely **Resume reconciles the repository, not just the chat.** Reopen a session and it revalidates the git worktree against the exact state that session last saw, then computes a structured _repository delta_: commits that landed, files changed (with dependency manifests and migrations flagged), symbols added or removed, and which files import what moved. That gets handed to the agent once, before your next prompt — so it reconciles up front instead of discovering the drift three tool calls deep. Bounded, argv-only git. It never blocks you from switching sessions, and if it can't finish in time it degrades to "no delta" rather than making you wait. **The knowledge belongs to the project, not the vendor.** Durable project memory and the code-search index are services the app maintains — local SQLite, FTS5/BM25 ranking, fully offline, no embeddings API. Both supported agents query the same memory and the same index through the same tools. Memory entries link to repository symbols, so guidance whose code got deleted is automatically demoted until that code comes back. **One set of permission rules, whichever agent runs.** Every tool call enters the same decision function — same risk classes, same path guards, same approval dialog — whether it arrives through Claude's SDK callback or Cursor's hooks bridge. Underneath sits an OS-level sandbox with a floor you can't configure away: the secrets store, the database, and settings stay unreadable no matter what the agent is told to do. ## On that last point — the knobs This is the part I didn't expect to care about as much as I do. An agent with filesystem and shell access on your machine should be _governable_, and "governable" means more than an on/off switch. Right now that's **15 settings categories and 172 individually searchable settings**, across 13 config groups: per-session permission modes (plan / ask / approve-edits / accept-edits), a provider-neutral sandbox policy with its own network posture, how memory gets captured (propose, auto with a confidence threshold, or off), retrieval budgets, worktree behavior, which commands count as read-only, MCP servers shared across both agents. You shouldn't have to accept someone else's defaults about what an autonomous process may do in your repo. ## What it deliberately isn't It's not a model, it's not an agent loop, and it's not a clone of one. It doesn't hold your API keys — each agent authenticates itself exactly as it does in your terminal. Drop Limboo tomorrow and your CLI still works the same; there's nothing to lock you in. It owns the parts the agent isn't responsible for and every agent needs: repository state over time, durable knowledge, a permission model with an OS-level floor, isolated execution roots. ## Where it's at v1.5.1, MIT, Electron + React + TypeScript, installers for Windows / macOS / Linux. Local-first in the strict sense: no backend, no telemetry, no cloud sync — the only network traffic is the agent talking to its own provider. [REPO](https://github.com/limboo-ai/limboo) If you've hit the stale-resume problem too, I'd genuinely like to hear how you deal with it — I'm not convinced a repository delta is the only shape this fix can take. ## Community discussion Top comments from developers on daily.dev. **@lezli01** · 1 upvotes > Valid thoughts. **@rizzdev** · 1 upvotes > The amount of nightmares I’ve had not realizing I’m on the wrong branch ## Similar posts on daily.dev - [Your Coding Agents Are Only as Good as Their Feedback Loop](https://daily.dev/posts/your-coding-agents-are-only-as-good-as-their-feedback-loop-lkobdwt1q) · Atomic Spin · 1 upvotes · 0 comments - [AI Agents Need Their Own Desk, and Git Worktrees Give Them One](https://daily.dev/posts/ai-agents-need-their-own-desk-and-git-worktrees-give-them-one-8wfs2jfmk) · Towards Data Science · 1 upvotes · 0 comments - [I Built a Claude Code Skill That Turns Any Existing Web App Into a Local Vibe Coding Environment](https://daily.dev/posts/i-built-a-claude-code-skill-that-turns-any-existing-web-app-into-a-local-vibe-coding-environment-gs4kx8e7g) · Medium · 2 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#git](https://daily.dev/tags/git), [#claude-code](https://daily.dev/tags/claude-code) [View this post on daily.dev](https://daily.dev/posts/your-coding-agent-remembers-the-conversation-it-has-no-idea-your-branch-moved--lcbaazklp) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/your-coding-agent-remembers-the-conversation-it-has-no-idea-your-branch-moved--lcbaazklp","headline":"Your coding agent remembers the conversation. It has no idea your branch moved.","text":"A developer describes a common but underappreciated failure mode with AI coding agents: sessions persist conversation history but not filesystem state, so resuming a session after repository changes causes the agent to confidently act on a stale world model. The post introduces Limboo, a local-first desktop workspace built to solve this by treating the environment as infrastructure — reconciling the git worktree on session resume, maintaining a local project knowledge base (SQLite/FTS5, offline), and enforcing a unified permission model across multiple agents. v1.5.1, MIT-licensed, built with Electron + React + TypeScript, with no backend or telemetry.","url":"https://daily.dev/posts/your-coding-agent-remembers-the-conversation-it-has-no-idea-your-branch-moved--lcbaazklp","datePublished":"2026-07-25T03:10:31.038Z","dateModified":"2026-09-13T21:12:02.797Z","author":{"@type":"Person","name":"TELVIN TEUM","url":"https://daily.dev/telvinteum","image":"https://media.daily.dev/image/upload/s--Xm3EENwc--/f_auto/v1764264817/avatars/avatar_fHXKQsFKEpHqADEmpsXk2?_a=BAMAK+ZW0","description":"We are still floating 🥲😭","interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":680}},"image":"https://media.daily.dev/image/upload/s--_S2QAD_2--/f_auto/v1784937196/posts/DCOjqnPAs?_a=BAMAMicg0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":5}],"comment":[{"@type":"Comment","text":"Valid thoughts.","datePublished":"2026-07-28T07:59:19.886Z","url":"https://daily.dev/posts/LCbaAzKLP#c-JWdYr8B65","author":{"@type":"Person","name":"László Szabó","url":"https://daily.dev/lezli01","image":"https://lh3.googleusercontent.com/a/ACg8ocKj3v7EFYJoXUUuro6ALF9fD3RTRATiBpBOVcOzqro4fy6bWqMm=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}},{"@type":"Comment","text":"The amount of nightmares I’ve had not realizing I’m on the wrong branch","datePublished":"2026-07-30T18:53:27.641Z","url":"https://daily.dev/posts/LCbaAzKLP#c-sf8InmDM3","author":{"@type":"Person","name":"Andrew","url":"https://daily.dev/rizzdev","image":"https://media.daily.dev/image/upload/s--35vRfXAA--/f_auto/v1785413727/avatars/avatar_fQ7ttCKtPuu6tDvcgQXv5?_a=BAMAMicg0"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/squads/jigjoy","name":"JigJoy"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"JigJoy","item":"https://daily.dev/squads/jigjoy"},{"@type":"ListItem","position":3,"name":"Your coding agent remembers the conversation. It has no idea your branch moved."}]} ```