Login

u/Affectionate_Sink820

▲ 1 r/sideprojects

gi-log v0.2.0 — follow-up on my Claude Code memory tool (now with session summaries)

gi-log Update

A few weeks ago I posted about gi-log, a tool that saves Claude Code conversations locally and recalls them in future sessions. Thanks for the feedback — it helped shape this update.

What was wrong with v0.1.0

The keyword search was unreliable. gi-log extracted entities from individual exchanges, which meant short or technical conversations produced poor keywords and recall would miss relevant sessions entirely.

What's new in v0.2.0

When a session ends, gi-log now generates an LLM summary of the full conversation. Entity extraction runs on the summary instead of individual exchanges — this gives it much more context to work with and keyword matching is noticeably more accurate.

  • Session summary stored in SQLite on every hook-stop
  • Entities extracted from the summary → better keyword search
  • Summary embedded and stored (groundwork for session-level semantic search)

Everything still runs locally. Same OpenAI dependency for embeddings and summarization.

Upgrading from v0.1.0

The sessions table schema changed — drop it and it'll recreate on next run:

>

Install

>

>

GitHub: https://github.com/Bdo1112/gi-log

Free Trial API Keys Offer

Want to try it without setting up an API key?

I'm offering free trial API keys to a few people who want to test it. Just comment below or DM me — I'll send you a key so you can try it with zero setup friction. Only asking that you share what you think of the recall quality after a few sessions.

Still early — would love to know if recall quality feels better after a few sessions.

reddit.com
u/Affectionate_Sink820 — 1 day ago
▲ 2 r/SideProject

gi-log v0.2.0 — follow-up on my Claude Code memory tool (now with session summaries)

gi-log Update

A few weeks ago I posted about gi-log, a tool that saves Claude Code conversations locally and recalls them in future sessions. Thanks for the feedback — it helped shape this update.

What was wrong with v0.1.0

The keyword search was unreliable. gi-log extracted entities from individual exchanges, which meant short or technical conversations produced poor keywords and recall would miss relevant sessions entirely.

What's new in v0.2.0

When a session ends, gi-log now generates an LLM summary of the full conversation. Entity extraction runs on the summary instead of individual exchanges — this gives it much more context to work with and keyword matching is noticeably more accurate.

  • Session summary stored in SQLite on every hook-stop
  • Entities extracted from the summary → better keyword search
  • Summary embedded and stored (groundwork for session-level semantic search)

Everything still runs locally. Same OpenAI dependency for embeddings and summarization.

Upgrading from v0.1.0

The sessions table schema changed — drop it and it'll recreate on next run:

>sqlite3 ~/.gi-log/gi_log.db "DROP TABLE sessions;"

Install

>go install github.com/Bdo1112/gi-log@latest

>gi-log install

GitHub: https://github.com/Bdo1112/gi-log

Free Trial API Keys Offer

Want to try it without setting up an API key?

I'm offering free trial API keys to a few people who want to test it. Just comment below or DM me — I'll send you a key so you can try it with zero setup friction. Only asking that you share what you think of the recall quality after a few sessions.

Still early — would love to know if recall quality feels better after a few sessions.

reddit.com
u/Affectionate_Sink820 — 1 day ago
▲ 1 r/SideProject

I built a memory system for Claude Code so it stops forgetting everything between sessions

Introducing gi-log

Every time I start a new Claude Code session, I have to re-explain my stack, re-describe past decisions, and sometimes re-solve problems I already solved last week. It's frustrating.

So I built gi-log — a tool that automatically saves every Claude conversation to a local SQLite database and lets you recall past context with a slash command.

How it works:

  • A stop hook captures every user message + Claude response after each exchange
  • It embeds the conversation via OpenAI (text-embedding-3-small) and stores it locally
  • An MCP server exposes a recall tool so Claude can search past conversations
  • Type /gi-log in any session to pull in relevant past context

Everything runs locally. The only external call is to OpenAI for embeddings — at text-embedding-3-small prices, saving thousands of conversations costs less than $1.

Setup is one command:

git clone https://github.com/Bdo1112/gi-log
cd gi-log
make install

Then add your OpenAI key to ~/.gi-log/config.json and restart Claude Code.

Would love feedback — especially on the recall quality and whether the /gi-log slash command feels natural to use.

GitHub: https://github.com/Bdo1112/gi-log

u/Affectionate_Sink820 — 4 days ago