v0.7.0
LLM inference in C/C++. Contribute to ggml-org/llama.cpp development by creating an account on GitHub.
llama.cpp11 min read
chat-recall Blog
Stay updated with the latest developments in Artificial Intelligence
Agents on live hardware: reason where you must, engineer everywhere else
CoreWeave Blog10 min read
b11669
llama.cpp1 min read
Cursor chat history: where it lives and how to read it
Cursor keeps chat history in two different SQLite databases depending on whether you used the IDE or the CLI, and it has moved the IDE format three times.
chat-recall Blog5 min readClaude Code session history disappeared: four reasons
Four things make Claude Code sessions vanish from the picker, and only one deletes anything. Check the other three before you conclude the work is gone.
chat-recall Blog4 min readGiving Claude Code memory with an MCP server
Which file Claude Code reads, what the entry looks like, and the one key that makes a correctly configured server register and then expose no tools at all.
chat-recall Blog5 min readHow to view your Claude Code session history
Claude Code keeps every session as a JSONL file on disk. Two built-in commands show you part of it, the files show you the rest, and neither one searches.
chat-recall Blog4 min readCompact instructions: tell /compact what to keep
Compaction decides what survives unless you decide for it. Passing instructions to /compact, and the PreCompact hook that supplies them every time.
chat-recall Blog5 min readContext left until auto-compact: what the number counts
The percentage in the status line, what makes it fall, how to move the threshold, and what actually happens to your conversation when it reaches zero.
chat-recall Blog5 min read/clear vs /compact in Claude Code
One summarizes the conversation and keeps going. The other starts a fresh one. What each does to the transcript on disk, and which to reach for.
chat-recall Blog5 min readClaude Code has auto memory. Where it stops.
Auto memory writes notes about your preferences per repository, on one machine. What it is good at, the four boundaries it does not cross, and what to pair it with.
chat-recall Blog5 min readWhere every AI coding tool stores your sessions on disk
Exact paths and formats for every AI coding tool chat-recall reads: and the retention period that quietly deletes them.
chat-recall Blog5 min readDoes Claude Code remember previous sessions?
Partly, and the part it forgets is the expensive one. What CLAUDE.md, auto memory and --continue each carry across, and what none of them carry.
chat-recall Blog5 min readYou pasted an API key into a coding session. Now what?
Deleting the chat does not remove it. Where the key actually lives, how to find every session that contains one, and what to do in what order.
chat-recall Blog4 min readThe three kinds of MCP memory server
Knowledge-graph stores, note-takers and session indexes are three different products wearing one label. Which one you need depends on a single question.
chat-recall Blog5 min readCompacting conversation: what Claude Code keeps and drops
What auto-compact does to a long session, why the assistant starts contradicting itself afterwards, and how to get the lost detail back instead of retyping it.
chat-recall Blog6 min readUsing several AI coding tools without losing the thread
A practical setup for working across several AI coding tools at once: what breaks when you switch tools, and how to keep one memory across all of them.
chat-recall Blog5 min readWhat claude --continue does not do
claude --continue resumes one session, in one tool, in one directory. What to use when the thing you need is older than that, or was not in Claude Code at all.
chat-recall Blog3 min read
Showing 15 of 15 stories
You're all caught up.
AiByts Weekly Brief
Get the top AI news and tools straight to your inbox every week.
Weekly · AI news from chat-recall Blog
Join 15,000+ AI enthusiasts