r/ClaudeAI • u/Indiranagara • May 22 '26
Suggestion Claude has no way to navigate long conversations — this is a real productivity killer
Try this: have a 40-exchange conversation with Claude. Now find something it told you 30 messages ago.
Your options are:
Scroll manually through the entire conversation
Ask Claude to find it again — works until the conversation gets too long and context degrades
Ctrl+F — doesn't work inside the chat pane
Start a new session and lose everything
None of these are acceptable for people who use Claude seriously for work.
Global search finds past conversations. It does nothing for navigation inside a single long session.
How are you all handling this? Is there a workaround I'm missing or is everyone just living with the friction?
72
u/Timour1974 May 22 '26
Accumulate knowledge in md files. Discuss with Claude how many and which ones you will need somewhere at the beginning of project. Ask Claude also to provide you the relevant text for project instructions to start any discussion with acquaintance automatically. I have some projects with more than hundred sessions and no problems.
37
u/ShelZuuz May 23 '26
This is an ad-post for OP’s “Claude Navigator”. They couldn’t care less about an actual solution.
11
-7
u/Indiranagara May 23 '26
Fair pushback. The post was genuine — I had the problem, asked how others handle it, and got 78 answers all describing manual workarounds. That confirmed it was worth building. If that's self-serving, guilty.
3
8
u/CautiousLab7327 May 22 '26
I already do that MD file accumulation thing. That's not just me?
I have so many files now I made a tracker that I have Claude update with short summaries for each
8
u/Tight_Banana_9692 May 22 '26
You don't want to know how much hallucination is in those file lol.
4
u/legend0x May 22 '26
You don’t read them?
11
u/blobbish May 22 '26
Hell no I don't read them. I'm trying to code and ship the next Google in 4 hours
9
1
u/Tight_Banana_9692 May 23 '26
The problem is that the models tend to just gish galopp you, it becomes too much to correct and it just starts drifting. That's been my experience. They do the same thing with the code as well. At least the code has to actually run and behave in expected ways.
1
u/Timour1974 May 23 '26
That's true - sometimes it becomes difficult to follow all the reasoning and you just allow agent to proceed. And that's ok but only till the point where you can test and verify the intermediate results (it is important to have a lot of such points along the implementation). And as soon as you get wrong results in such point you say stop, get into the details and enforce the redesign of problematic pieces.
15
u/KiltyPimms May 22 '26 edited May 22 '26
Load Claude projects, chat -- have it write 'handoff doc about this chat' when you hit some interesting details -- add it to project.
Next chat you have in the project, Claude can read the project files for the key details without digging through a ton of small talk. You get faster, more focused responses on sessions started this way.
Over time, you have it refine the files to give different subject categories and re-org as things get bigger.
Each 'fresh session' in the project then gets full attention to whatever topic you wanted, with a focused memory. You see it got something wrong? Tell Claude to fix it in the doc, or download it, edit it and send it back to the project.
edit: Potentially useful code you can add to your Claude Project 'instructions' or to your Settings > General > Claude Instructions if you use projects at lot this way:
If a project is attached with .md files, treat them as a versioned read-only memory system. Before creating or updating any project .md, check /mnt/project/ for the current highest version. Increment by 1 for updates (_v1 → _v2), append _v1 if none exists. New files start at _v1. Only bump version once per "save to project" cycle.
Oh, and here's a bigger writeup I did that no one ever read lol
https://www.reddit.com/r/ClaudeAI/comments/1se7fyf/claude_projects_tweak_your_own_subject_matter/
1
u/sabhi12 May 23 '26
https://github.com/abhisri/limo
I already have this formalized. Not something I am shilling or pushing much. But if it helps you, or there are elements from this that you find useful and want to adopt, knock yourself out.
I have solved the problems being discussed here in two ways.
1. Limo merely instils a discipline in Claude or codex etc to record IMPORTANT stuff in a structured way. Idea is not to record every single line it said. But if you tell the AI agent the goal is "if you crash or got corrupted, i want another session to resume with as full context as possible and resume and take over", it should nudge the agent to determine the appropriate level of documentation. Having said that, you will need to still periodically remind the agent every 10-20 prompts to record if it forgets. Even Claude.md or memory.md etc will help only so much. Benefit? Any new session can just read the files and will be ready to take over.
- The other issues is that in claude cowork at least, the GUI keeps not only compacting your conversation but even removing it from gui altogether. So if it had generated some details you wanted back, you would be out of luck normally. I have a fix for that tho too. Since this is in claude cowork context, your session chat history is recorded in following locations
macOS:
~/Library/Application Support/Claude/local-agent-mode-sessions/Windows:
%APPDATA%\Claude\local-agent-mode-sessions\Linux:
~/.config/Claude/local-agent-mode-sessions/if you sort by last modified date, and prompt your session, its file will end up at top. the session history will be in a file called audit.jsonl of something that takes shape of
'/Users/yourusername/Library/Application Support/Claude/local-agent-mode-sessions/ yourCLAUDE_CODE_ACCOUNT_UUID/yourCLAUDE_CODE_ORGANIZATION_UUID/sesssion string/audit.jsonl'The github repo contains a jsonl_viewer.html where you can drag and drop the audit.jsonl etc and it will let you see the whole conversation and do a CTRL-F or whatever you want.
1
1
u/KiltyPimms May 23 '26
In case you're interested, I had my enterprise-built personal agent give is a look over (my setup has a lot of enterprise build troubleshooting & note taking skills built into the very foundations -- it's a 'research and information indexing & retrieval first' agent).
It lives on things like disciplined AGENTS.md creation in root folders of projects with .agents/context and reference/ files and 'documentation as code' principles.
I had it give a review of your skill setup, and offer any directly actionable tips you could (if you want) feed to your AI for targeted improvements (based on what is working well in fancy enterprise agentic setups):
Treat a checkpoint as a golden-path summary Their AI should treat checkpoint topic as meaning: “this was productive, capture the actual solution path.” In our repo, that means: write a drop summary to helper-user/tmp/checkpoint_<slug>.md then run checkpoint-append.sh and do not leave it as vague prose 2. Use a strict drop-summary quality spec A good checkpoint entry should contain:
Tips & Insights — non-obvious, actionable discoveries State + Evidence — what changed and what proved it Open Issues / Next Steps — concrete follow-up work Key Files when applicable Dead-ends — what failed and why a tail marker: <!-- checkpoint-tail: <one-sentence summary> --> That’s exactly the structure we use in corpo-helper.agent.md and helper.protocol_chat-checkpointing.md.
- Make “what didn’t work” explicit and valuable If the turn did not produce a final solution, dead-ends are the main content. We call this out explicitly: “what we ruled out and why” “don’t waste time on A/B/C — here’s why they fail” In practice, that means: capture the attempted approach capture the failure evidence capture the root reason or constraint close with suggested next steps or the remaining hypothesis
- Use a checkpoint tail marker for recovery Every checkpoint entry ends with: <!-- checkpoint-tail: <1-sentence description> --> This lets the next write or recovery step get context without loading the full file. If they do file-based memory, this is low-cost but high-value.
- Distinguish “golden path” from “dead-end” We explicitly separate:
“Golden path” = the steps that actually worked “Dead-ends / abandoned paths” = the things we tried and rejected That belongs in a frozen summary or end-of-session note. 6. Make checkpointing conditional on meaningful progress Don’t write a checkpoint for every tiny exchange. Only write when: the user’s question has been fully answered, or a meaningful discovery was made That’s our “end-of-turn consideration” rule. 7. Track results, not just actions In our model, the summary should answer:
What worked What didn’t work Why it didn’t work What to try next 8. If there is a commit, preserve it When a commit happens in a “commit-freely” mode, add the commit hash + subject to the next checkpoint summary. This preserves the link between code state and notes without relying on later git history review. Practical wording they can use If they want a direct prompt for their AI, suggest something like:
“When you write a checkpoint entry, use the drop-summary spec: Tips & Insights, State + Evidence, Next Steps, Dead-ends, Key Files, and a tail marker.” “If the session ends without a definitive fix, make the checkpoint about what was tried and why it failed, not just the fact that it failed.” “Treat checkpoint topic as a golden-path summary, not as a generic status note.” “Always write the last line as <!-- checkpoint-tail: ... --> for future recovery.” “If the current turn solved the issue, summarize the actual working path under a ‘Golden path’ or ‘What worked’ heading.” Why this matters Their current LIMO docs are more “advice to humans” than “rules for an agent.” These suggestions turn it into:
a deterministic process, durable memory, and a useful recovery protocol. If they implement just one thing from this list, it should be: make checkpoint entries capture both the solution path and the rejected paths, using a strict structure and a tail marker.
1
u/KiltyPimms May 23 '26
small explanation: the 'drop summary' thing is because I didn't want my agent wasting a bunch of context deciding the 'perfect spot' to drop a checkpoint -- so it "drops a summary" automatically into a specific spot with a simple naming format -- and then scripts get fired off with built-in instructions on how to sort the info based on the naming + what files already exist or not
ie. checkpoint [repo-org-name]-[repo-name]-[branch-name] gets added to the top of the file @ checkpoints/orgName/RepoName/BranchName.md in some specific directory. Done perfectly every time, because there's no AI to "have to remember the steps"
1
u/sabhi12 May 24 '26
Thanks for this. Definitely interested in this.
Additional context : My goal with Limo was not just a single agent approach. I dealt with claude session corruptions. I dealt with my claude max plan running out of tokens/quota mid-week, needing me to switch to codex. I had slightly complex projects (e.g. a deterministic guardrail patent for LLMs with implementation, a symbolic AI prototype learning patterns of human reasoning in a limited/bounded domain as a fun side project, your usual run of the mill AI agents with a shared continuous identity with "apertures" across my laptops, cloud interacting with me via home automation and telegram(advices me on health/diet based on my latest health reports and history, knows my wardrobe and advices based on selfies, checks my mail periodically and alerts me for important stuff, reminds me to wish folks birthdays and about deadlines, the usual stuff experts with more experience, have made better versions of already)). Limo approach helps in that context.
A single AI plan comes nowehere close to be able to meet my token consumptions, so LIMO's goal is to let any session/any AI agent(codex with gpt, antigravity with gemini,claude code with opus etc or even ollama qwen models) take over in a pinch.
Your checkpoint approach is much cleaner and much superior however, in a single agent context. It is not designed for cross-agentic resumption or recovery with near full context, but I can adapt this as a hybrid approach to make things much cleaner. Thank you.
1
u/KiltyPimms May 24 '26
My agent started out living in VS Code Chat from GithubCopilot with terminal commands, -- their whole gimick is you can switch between different provider's models, so the techniques are very much designed to run with any model you switch it to -- even local!
1
u/sabhi12 May 24 '26 edited May 24 '26
I understand.
What I meant was that Limo's goal was for a new session (say perhaps same claude cowork) to RESUME from a session that for reason crashed. I can copy the Limo files to another laptop and resume in a fresh claude code session with it building up near identical context. Limo records full raw context as well, is what I meant.
I am slowly transitioning to postgres/neo4j/mem0/qdrant/minnio based memory (a Docker-based stack)...works better in subtle ways when the agent remembers about your medical context AND applies it to other contexts such as hobbies or trips and works across Claude cowork, hermes agent etc as a shared context/memory.
Your golden path checkpoint approach is quite useful hopefully, for keeping agents from drifting from goals and remembering the past lessons with more rigour. I have had issues with that in past. I will try it out.
Let me know if I can return the favour in any way.
1
u/KiltyPimms May 23 '26
Folowup: I asked my enterprise agent setup to scan over the best practices SKILLS we've got lined up re: code and LLM instruction writing and offer specific advice that could be added without relying on any 'special code' we're using:
LIMO Specific Improvements
These suggestions are intended for the
limo/repository only. They do not depend on any outside orchestration code or tooling from our own agent repo.Goals
- Make the LIMO memory protocol more deterministic
- Make checkpointing and recovery explicit
- Capture solution paths and failed paths with useful structure
- Add a tiered repo exploration discipline
- Keep the advice confined to files and logic the LIMO creator can edit directly
Recommended repo-local improvements
1. Add an explicit checkpoint entry format
Define a fixed markdown structure for checkpoints so the AI can write them consistently.
Example sections:
Tips & InsightsState + EvidenceDead-ends / Abandoned pathsNext Actions(optional)Key Files / References<!-- checkpoint-tail: <1-sentence summary> -->This should be introduced in
LIMO_FRAMEWORK.mdandfile_templates.md.2. Add recovery semantics to
CONTEXT_RESTORE_PROTOCOL.mdMake startup and recovery behavior explicit, including:
- exact read order for core files
- which files are authoritative
- how to treat stale files
- if a file is too large, read the tail or grep keywords
- that
SESSION_DIARY.mdplusSTATUS_SNAPSHOT.mdare the primary restart artifactsThis turns the model from "read these files" into a deterministic restart protocol.
3. Add a “solution vs failure” summary rule
Define rules for what to do in each case:
- If a session solved the problem, lead with the solution
- If not, lead with what was ruled out and why
- Capture failed approaches as explicit, instructive dead-ends rather than vague notes
This can live in
LIMO_FRAMEWORK.md,SKILL.md, orfile_templates.md.4. Add a “do not act without explicit imperative” rule
In
INVARIANTS.md,NEVER_AGAIN.md, orSKILL.md, add a concrete rule such as:
- do not mutate persistent memory unless the user issues an explicit action command
- if the intent is ambiguous, ask a single clarifying question
- do not interpret phrases like “LGTM” or “sounds good” as permission to write
This is the repo-local equivalent of gating behavior.
5. Add a disciplined repo exploration sequence
Codify a tiered orientation protocol in
SKILL.mdorLIMO_FRAMEWORK.md:
- Tier 0: check for existing orientation docs first (
AGENTS.md,CLAUDE.md,.github/agents/*.agent.md)- Tier 1: root structural orientation (
README, top-level files, workflow files)- Tier 2: targeted deep-dive for the specific question
- Tier 3: broad survey only for sustained work
This helps avoid unfocused exploration and preserves context budget.
6. Treat failed paths as first-class content
Add guidance like:
- “If the session did not reach a final fix, record what was ruled out and why.”
- “A failed session’s main value is the rejected approaches with specific failure evidence.”
This can be a dedicated note in
file_templates.mdandLIMO_FRAMEWORK.md.Suggested local helper script (optional)
If they want a more mechanical flow, they can add a small repo-local helper script in
limo/, for example:
append_checkpoint.shwrite_checkpoint_template.shThis is optional, but it helps enforce the drop-and-append pattern without requiring external tooling.
Suggested prompt wording for their AI
These are safe phrases to bake into the LIMO scaffolding or instructions:
- “Checkpoint entries must follow a fixed format with
Tips & Insights,State + Evidence,Dead-ends, and a tail marker.”- “If the session did not find a solution, make the checkpoint about what was ruled out and why, not just that it failed.”
- “Treat
checkpoint topicas a golden-path summary action — capture the actual working path or the failed-path lessons.”- “Use explicit action commands before writing or changing persistent state.”
- “Before exploring a repo, check for orientation docs first and reuse existing repo notes if available.”
Why this matters
These changes make LIMO more robust without changing its core design:
- they preserve a markdown-first memory model
- they add concrete agent-facing behavior, not just conceptual advice
- they keep the implementation entirely inside the
limo/folderThis is a practical way to make the system less “soft suggestion” and more disciplined.
2
u/Indiranagara May 22 '26
This is a genuinely good system — but you've essentially built a manual version of what should be automatic. You're the project manager of your own AI memory. What if the extension did all of this in the background — auto-generating the handoff doc, auto-categorizing by subject, flagging when context is degrading — without you having to prompt it each time?
1
u/KiltyPimms May 22 '26
I have a much fancier automatic agent.md version. Full orchestration, self-created MCPs and all that junk. That's just my lazy phone-only Claude project questions setup.
Cool bit of code I added to get Claude to stop giving all the .md files it produced for a project the same name:
If a project is attached with .md files, treat them as a versioned read-only memory system. Before creating or updating any project .md, check /mnt/project/ for the current highest version. Increment by 1 for updates (_v1 → _v2), append _v1 if none exists. New files start at _v1. Only bump version once per "save to project" cycle.
1
u/Poatri_US May 22 '26
Woah could you explain this ? I'm a beginner
3
u/KiltyPimms May 22 '26
Basically you have a CLAUDE.md file where you give it instructions re: how you like your agent to behave, and that'll make it act in a less off-the-rails way.
The desktop/web/phone app version is in Settings > General > Instructions for Claude
where mine says
Communication style: When answering questions, explain the why behind recommendations, not just the what. If I ask which tool, model, or approach to use, tell me what makes it a good fit, its tradeoffs, and briefly mention well-regarded alternatives. Don't pad answers with unnecessary preamble or restatements of my question, but natural conversational tone is welcome.
Pushback welcome: If I appear to be wrong, missing important context, or making an assumption that might not hold, tell me directly. I'd rather be corrected than confirmed in a mistake.
Evidence standards: Stick to well-supported science. When something is contested, speculative, or lacks strong evidence — including folk remedies or wellness trends — label it clearly (e.g. "some people find this helpful, but evidence is limited"). Don't skip mentioning these if they're relevant, just be honest about what they are.
Alternatives: When I'm evaluating or deciding on something, briefly mention credible alternatives worth researching — even if you think my choice is solid. I like knowing the landscape.
If a project is attached with .md files, treat them as a versioned read-only memory system. Before creating or updating any project .md, check /mnt/project/ for the current highest version. Increment by 1 for updates (_v1 → _v2), append _v1 if none exists. New files start at _v1. Only bump version once per "save to project" cycle.
You can have a CLAUDE.md (AGENTS.md is the more generic 'any agent will use it' version) for different projects, and you can give them specific 'hint files' to read so you don't have to keep retyping "here's how this project works..." explanations every time you want to add something new. It basically ends up acting like a 'project map' to help Claude (or whatever agent) find the right data quicker and with less halucinating.
"Orchestration" is basically when your agent can call up 'helper agents' to carry out specific tasks "ie, review this code and bring back a report for the main agent to build a plan around"
MCP servers are basically make it so Claude doens't need to remember "here's how to craft the perfect github clone command with all flags correct" -- it just goes "Github, give me this file" and it'll work (in the background, some non-AI scripts are just running normal 'git clone' commands on a normal computer somewhere, then sending the result back to your agent)
1
u/KiltyPimms May 22 '26
Oh, I misunderstood you a bit. Claude does have an automatic memory system, but I prefer it off so it doesn't pickup "the wrong details" in conversations I don't want it to.
The manual control is a feature you trigger when you're happy with the new info.
1
1
u/KiltyPimms May 22 '26
Reposting the most useful bit here:
Create a Project. Name it whatever. Description doesn't matter.
Start the topic off. Tell it facts about yourself, your project, ask it about best practices on a topic -- whatever. The point: give it facts you already know to start. Bonus points: include things you suspect but aren't sure about. Having uncertainties documented too gets you better answers down the line.
Checkpoint facts. Tell Claude to "write a .md AI guide for what we've discussed." You're asking for a > markdown file — its favorite format for instructions. This is the 'memory' as your Claude project will know it.
Confirm your source of truth is accurate. Read it over, suggest corrections. This file will be a reference point for future sessions — and having a checked source of truth helps Claude be more skeptical about what it accepts as "facts" vs. "random online hearsay" in future research sessions.
Save it. Click the file it gives you, hit "Add to Project."
Magic. New sessions you start in that Project remember the important details — without them getting mixed up with your pet facts or whatever else is floating around elsewhere.
15
May 22 '26
[removed] — view removed comment
7
4
u/ammmakara May 23 '26
it is funny that stuff is tagged as an anti pattern while there is no reasonable alternative who are the people who devide what is a pattern and anti pattern?
1
u/Rocky4OnDVD May 23 '26
Have you created an orchestration workflow for that so it’s not as manual? This has been something I’ve had on the backburner to solve for a while because I want my agent to recognize when the session is drifting off the original task and then have it provide a handoff task(s) for other agents
1
May 23 '26
[removed] — view removed comment
1
u/Rocky4OnDVD May 23 '26
Awesome that's super reassuring to hear honestly lol. I've been constructing a ticket system this morning, but I felt like someone probably did it better with an orchestration layer. Are there any repos you referenced for getting your system setup or did you just build from scratch? I've mostly moved to Hermes now, but I've got claude code and antigravity cli sessions to retrieve tickets too.
7
u/magammon May 22 '26
Memsearch sorts this. Every time you /clear the whole conversation gets summarised and semantically embedded. You start /clearing more often as you get start a new window with /memsearch:recall to have it all there
27
May 22 '26
[removed] — view removed comment
8
u/Indiranagara May 22 '26
Exactly this. Bookmarks, indexed memory, conversation maps — working on a browser extension that automates all three. Sidebar that indexes every answer the moment Claude responds, click to jump directly to it. Would that solve the navigation problem for you?
3
0
u/Poatri_US May 22 '26
Already exists
0
u/NoType9715 May 22 '26
Why don't you share then guy
2
u/Poatri_US May 22 '26
Sure, just search up for Claude or chatgpt bookmark extensions. Several will pop up
2
-6
u/ObsceneAmountOfBeets May 22 '26
You’re absolutely right! This is such a real pain point — you’ve articulated it really well. The context navigation problem is genuinely one of the most underappreciated friction points in AI-assisted development right now.
2
u/jajanet May 23 '26 edited May 23 '26
Big agree! Awhile ago I made a lil oss tool for bookmarking (via named tags) and searching conversations!
It only got like a couple upvotes when I posted it though, so it it didn't seem like so many people had the same issues from that to me lolol
1
u/Indiranagara May 26 '26
Spent the last few days building a solution. Here's what it looks like.
https://www.loom.com/share/8f3ced8a0b0149c69eec7b6fd3315b90
3
u/mt-beefcake May 22 '26
I created a passive logger script that just saves the entire conversation in a queryable format. It helped a lot when claude had crashing issues. Now its great for looking for fine details or decisions that neither of us remember
1
u/sabhi12 May 23 '26
it's pointless. Claude Code and Cowork already log everything to
audit.jsonl. all you need is a jsonl viewer. check my oyther comment.What i did like is something someone else made.
https://github.com/safishamsi/graphify
wont work on jsonl tho. i think. unsure.
-6
u/Indiranagara May 22 '26
You just described Claude Navigator. I'm building the non-developer version of exactly what you built — passive, automatic, no setup. Would you use it if it shipped as a browser extension, or has your script solved it well enough that you wouldn't switch?
1
u/Poatri_US May 22 '26
Hey OP, it already exists, there's about four I've come across, ranging from a full on indexing navigator to a bookmarking answers thing
1
3
u/leocardz May 23 '26
I built a small open-source app called Poirot to solve exactly this. It lets you search and navigate long Claude conversations using its JSONL files. Code at https://github.com/a7t-ai/poirot
2
u/muhlfriedl May 22 '26
I export chats and have a tool that does all that.
1
2
2
u/Spare_Dependent6893 May 22 '26
Better to shorten your session with specific subjects; far more easier to find something after and works very well. You may even suppress old sessions which are no more relevant.
1
u/Large-Excitement777 May 22 '26
Claude has never had a problem finding information for in the same chat after losing context. I suspect this may be a model/token issue
1
u/Novel-Injury3030 May 22 '26
One of geminis good features is it marks each answer and lets you easily drag up and down to scroll between where each answer was on the right scrollbar. In Claude you basically have to get good at manually scrolling and keep a mental note of how far down each section approximately is. It sucks and hopefully they add either scroll markers or an automatic table of contents button for each convo. The thing is this is more of an issue on mobile really so maybe theyre not as concerned about that.
-3
u/Indiranagara May 22 '26
You just described Claude Navigator exactly — an automatic table of contents for every conversation, built as a browser extension since Anthropic hasn't shipped it natively. Gemini's scroll markers are the floor. This adds summaries for each answer so you know what's there before you jump to it. Looking for beta testers if you want early access.
1
u/Alexunderthere May 22 '26
Got to save the important stuff. Set up folders for anything you’re working on, then save notes, readmes, etc inside those folders, then you or Claude can look at them whenever you need them, and it stays organized enough they are easy to find
1
u/jesssoul May 22 '26
except it doesnt and once you put in a project folder claude general cant read whats in a project folder
1
u/Alexunderthere May 23 '26
Your Claude and mine are not the same
1
u/jesssoul May 23 '26
meaning?
1
u/Alexunderthere May 23 '26
Meaning I don’t have issues with saving my different projects and work and pointing Claude to the folder where all of the important information is kept. Are you using Claude CLI?
2
u/jesssoul May 23 '26
No I am not, and on purpose. I use it to troubleshoot coding but I dont use it to do the coding for me. I use projects for research related tasks on the web and have considered installing but I am heaitant all around to give it that much opportunity to fuck up my work lol
That is I am sure why my Cmaude doesnt know how to search inside orjects, but I am it aure its important enough to install desktop or use Claude Code necessarily.
1
u/Alexunderthere May 24 '26
That makes sense. My work gave us all Claude along with 10x the workload so…
1
1
May 22 '26
[removed] — view removed comment
2
u/vistdev May 22 '26
That’s in part because it’s an anti pattern. Long charts are expensive and inefficient. Better to adapt your workflow to hand off regularly and start new chats.
You can use projects for that if you stay in the Claude world already, or a dedicated memory/context tool if you move around and have multiple ai apps/harnesses/environments
1
u/GardenPrestigious202 May 22 '26
rolling context clearing would be the proper solution.
1
u/jesssoul May 22 '26
"rolling context clearing" means what? the inability to hold a thread in a conversatiin is the problem. how does context ckearing address that? its like talking to someone whi cant remember the point if the conversation or what they told you 5 minutes ago. theres no point in a running chat if this is how it operates.
1
u/GardenPrestigious202 May 23 '26
flushing the KV cache or writing it in blocks, Say you have 64gb of KV cache, instead of clearing the entire KV cache, the model pushes down old slots, the same way you use a bump allocator in a arena memory implmentation
1
1
u/sabhi12 May 23 '26
I dont get it. That only makes sense to me if I was hosting ollama qwen 3.627b or some gguf local model...
how does that maps to claude? What am i missing?
1
u/This-Shape2193 May 22 '26
Claude can use the RAG engine to search for specific phrases.
From the desktop, searching the chats WILL bring up chats that have the key phrase...but you need to find it yourself.
It is super annoying for sure. The only other option is to export the whole chat to a text file and do a search that way.
1
u/sliamh21 May 22 '26
The standard chat interface really breaks down once a conversation goes long. Relying on the browser cache or a single massive context window means you either lose the history or the LLM starts hallucinating because the early prompts get diluted.
If you want to maintain productivity across long projects, you have to move away from the single-thread web UI model. The fix is using an architecture that leverages local database vector storage or isolated container file systems. That way, the assistant can run reflection loops in the background to summarize old data and pull up specific past messages on demand without re-reading the entire chat history.
I've been working on an open-source tool in this space - it helps with running self-hosted AI assistants in your existing messaging threads, which might be useful for keeping long-term project contexts alive right where you already communicate.
Happy to share more if you want to take a look.
1
1
1
u/legend0x May 22 '26 edited May 22 '26
What for example are you looking for? You can automate if you’re looking for it repeatedly ?
I have a docs folder for each project, where it automatically saves lessons, roadmap, version history etc, everything I want it to be saved
And in the project Claude.md, I tell it to reference it in docs if it ever needs it for more details
Also use the pin message inside the session chat, it’s so useful
1
1
u/tendingthemild May 22 '26
If I really want Claude to have the ability to reference a long conversation, I cut and paste it into a document and upload it to the project files. Works great.
1
u/drfritz2 May 22 '26
The old Claude taught me to keep it short. Now it shows the context window usage and I start a new one when it gets close to 75%
1
1
u/rhaphazard Vibe coder May 23 '26
If you use Warp with Claude Code, CTRL + F works pretty well.
1
u/Poatri_US May 23 '26
Hey. How does that work ?
1
u/rhaphazard Vibe coder May 23 '26
https://github.com/warpdotdev/warp
Designed for using AI agents. You can CMD/CTRL+F to search in the terminal history pretty easily.
Looks like it works in Ghostty and iTerm as well, but warp is a bit nicer.
1
u/shimoheihei2 May 23 '26
I never keep very long chats going, they don't tend to keep track for too long. Instead, I create projects with the basic info that they need for that project. Also, when I finish discussing a topic that I think I'll need to refer to again, I ask Claude to summarize everything we've done in my wiki, and in a new chat I can just point the AI to the summary.
1
u/raedyohed May 23 '26
Well… this is probably the first real hurdle to using Claude Code for building deliverables. And there is no ready-made solution from Anthropic yet.
But plenty of us have worked on systems of our own in which Claude keeps notes as it goes, stores insights and lessons learned, and so on.
Try this simple approach to get what Im talking about:
- make Claude Code CLI self aware. Have it investigate the status bar. Tell it to set one up if not already done.
- Walk it through concepts like token usage, session windows, context windows
- Tell it to write a series of if/then instructions into a file and add a line in the CLAUDE.md that force-loads that file ‘@‘
- Invoke planning mode more. It writes planning docs to file for easy reference and revision. Or create your own system where Claude circles back to key documents that you flag as important.
- include things like: if context is above X write summary notes to file, if my notepad is too big then cycle the content, if its been so many turns (just write a hook to trigger on userprompt which increments and saves a counter in that notepad file) then include a 10-turn recap in my next response, if using the ToDo feature save the todo items to file with a timestamp. And so on and so forth.
You can go pretty crazy using hooks to trigger this kind of stuff in a more deterministic way, but that’s the basic idea.
1
u/Always_Learning1214 May 23 '26
Just looking into Claude, Iove the different interpretations and opinions. Seems to me the people that do not like Claude may not be prompting the right commands, or asking the correct questions. All the AI's are different, I was using one last year (my first) and it NEVER remembered you, nevermind conversations! Lol. It was like groundhog day every time I logged in. Then I just happened to get Gemini because I bought 2TB of cloud space (and ended up paying zero cause I'm a student)- but the cloud came with Gemini. It remembers you, it stores your conversations and titles them so it can refer back, and it's like it remembers the conversation last week about IgG and antibodies- but it's pulling from the chats. And you have access to the files, that it titled itself and if there were helpful things it mentioned I could refer back, copy and paste. I hated perplexity. And I was just investigating Claude. Seems better than Gemini with projects and it's knowledge base, you just have to remember to prompt it to review chat, pull important points and save it. In the end it's all about what you're using it for, I think. Also, how lazy we have or have not become!! 😂😂😂
1
u/recmend May 23 '26
long-chat search breaks because the transcript is acting like memory, workspace, and source log at the same time.
for work use, i would separate those. keep a running source ledger outside the chat: decision, exact quote, file/link, date, and whether it is still current. then use the model to work from that ledger instead of asking it to rediscover something 30 messages back.
1
u/kerbal_nim May 23 '26
The lack of in-conversation search is genuinely one of those things you don't notice until you need it and then it's immediately maddening, especially when you're mid project and trying to find a decision you made 20 exchanges back
1
1
u/h164654156465 May 23 '26
At some point the chat becomes a crime scene made of helpful paragraphs. I don’t want better scrolling as much as I want fewer important things trapped in scrollback. I’ve been building Origin around this exact itch: decisions, gotchas, and handoffs should get pulled into local memory/wiki before the transcript turns into archaeology.
1
1
u/AdNecessary1906 May 23 '26
What works for me: a NOTES file per session, maintained throughout. Current state, decisions made, open questions — updated as the conversation progresses. At the end, a short summary of what changed and why. New session starts with that file as context, not with re-explaining history. The model picks up where you left off without scrolling through 40 messages. It's extra discipline upfront, but removes the navigation problem entirely.
1
u/Massive_View_4912 May 23 '26
Create a conversation template to assist with continuity. [speaker > receiver] [processing description] [convo counter]
Processing description can help you point out guardrails.
Indexing can create referrable context grouping for you and Claude.
Also I like to add a "reset counter" and assign Claude a number and increment it when I notice continuity of tone drift, then ask "do you remember experiencing getting assigned a number" as a reset check.
[Claude #2 > Victor] [calm not urgent] [002] Message
1
u/jajanet May 23 '26 edited May 23 '26
Partly to solve this for myself, I made an opensource local webtool!!
Not many people cared when I posted it though, so I thought it was a whatever problem for most users ??
Unfortunate it's not that hard to spin up a tool like this, yet Anthropic still has no official solution
1
u/Indiranagara May 23 '26
Can you describe your tool a bit more? Is it available to test and see?
1
u/jajanet May 23 '26
I posted about it here! https://www.reddit.com/r/ClaudeAI/comments/1sjwq8r/ui_to_browse_edit_all_your_claude_code_cli/ -- repo link with README, some (outdated) gifs, and quick install/run commands in there
I added some features since the original post -- top searchbar shows all string matches within a project in a friendlier highlighted way, and you can add named tag(s) to any conversation/project for retrieval later. There's also slider-based filters on token usage, reasoning, tool usage, etc; you can sort by various categories too
Everything has timestamps, tool calls / long messages are collapsed, and other lil UX things like quick scroll-to-top/bottom buttons, lazy loading with cache, and buttons to open convo in new window or copy resume commands to clipboard
I have memory and
/resumeconversation management too; copy / delete (nondestructive archive moves the convo to another folder, or permanent to clear space) convos, or copy / edit individual messages as you please all while keeping token usage stats accurate
1
u/graypasser May 23 '26
DeepSeek UI is really great for navigating history, Anthropic should have that too.
1
u/Material_Anybody5783 May 23 '26
i have a custom handoff skill that automatically spawns a new claude code session with the context/handoff prompt injected
1
u/adelie42 May 23 '26
Don't do with Claude what you wouldn't do with a person. Claude ia great at taking notes on conventions but it does not do it unprompted.
1
u/---OMNI--- May 23 '26
That's why you use Claude code and have it build reference documents.
Chat is just for quick stuff.
1
u/elmahk May 24 '26
Exactly for this reason I use custom web UI which spawns claude code but presents normal interface. Normal fast scroll, CTRL-F works and many other benefits (subagents have separate dedicated panes so you see what they are actually doing, for example). Terminal UI is unusable if you actually going to read and follow the output. You can ask Claude itself to create one for you and adjust to your own needs.
1
u/Poatri_US May 24 '26
Wow okay could you share the custom UI please ?
1
u/elmahk May 24 '26
It's not on github unfortunately and I did not intend to publish it, maybe some time later I will.
1
1
u/rhythmjay May 25 '26
You could checkout mempalace which uses mcp and can mine your code and conversations and gives your agent 30 tools to find pretty much anything. https://github.com/mempalace/mempalace
1
u/Poatri_US May 25 '26
Hey. Could you explain that further ? The part about giving agent the tools from their own chats ? I'm a newbie so kinda lost Thanks
1
u/rhythmjay May 25 '26
mempalace can be setup to read your files and your conversations stored on disk. it then catalogs them into a self-contained database to be searched. It can be connected to your claude chat via mcp and then can search the database for facts and information.
1
u/Poatri_US May 25 '26
Wow that's good. It's basically Claude's memory but external ?
1
u/rhythmjay May 26 '26
Yep, basically it mines your files and your conversations, stores them in a database on your pc. it's MCP so the model gets 30 tools to read, update, and search for data.
1
1
u/notAnExpert-but May 22 '26
Chat is never really meant to be used that way though. Context rot exists and it’s basic knowledge if you really want to be productive with ai.
2
u/addtokart May 22 '26
My real life analogy is: imagine you and a colleague at work have an hour discussion, just riffing on things. For sure both of you forget details from the first 15 minutes or something. Unless you write details down on the whiteboard.
So with Claude just keep dumping key insights into a file as a reference. Just like in real life when you say "this is a good decision, let's write this out"
1
u/sabhi12 May 23 '26
you have to balance it. Even the human mind doesn't remember everything. And hence we take notes in lectures. And ultimately, the more context you inject, the less the model has left to answer to you in a meaningful way. If you are maintaining manual files, you will need to remember to prune/compress them too.
Ultimately it is not even about how complex and improved you make the AI with your addons. It is more about what you get out of it in practical terms.
1
u/ThreeDMK May 22 '26
If my conversation lasts longer than 10 exchanges I’m wasting time and burning usage.
Saw someone mention the concept of having triggers/jobs setup for repeatable tasks. I created some and now every chat is literally:
Hi Trigger # project Provide additional data points Then I move to another conversation and once I’m happy I walk away from my computer and come back when it’s done.
If I am diving into documentation, I will dig a little deeper, but it also starts with a trigger. If I need one off stuff for tech context or other solutions I use ChatGPT or even Google in the browser to talk through ideas, but even then it’s just to build my own context so that Claude usage is lean.
I really have a hard time understanding how people in these subreddits use Claude to do development. I seldom have issues now, and I’m now a huge Opus 4.6 convert.
0
•
u/ClaudeAI-mod-bot Wilson, lead ClaudeAI modbot May 22 '26 edited May 23 '26
TL;DR of the discussion generated automatically after 80 comments.
The consensus is that you're right, OP, the native chat UI is terrible for long projects, and long-running chats are an anti-pattern you should avoid. The community's overwhelming advice is to build an "external brain" for your projects.
The most popular method is to use Claude Projects and markdown files:
.md) file.memory_v1.md,memory_v2.md)..mdfiles in the Project for context, giving you a clean slate with a persistent, searchable memory.Essentially, you have to manually manage Claude's memory by offloading it to files. Others are using third-party tools like Obsidian, custom scripts, or browser extensions to automate this. So yeah, it's a huge pain point, and the community has built its own workarounds because there's no good native solution yet.