session-knowledge

Turn your Claude Code session history into a searchable local knowledge base, 13 MCP tools, pure stdlib, nothing leaves your machine

Runssource: GitHubPythonMITcommit 2f07e91f3571

Python, MIT licensed. The project labels itself: ai agents, anthropic, claude code, developer tools, full text search, knowledge base, llm and local first.

session-knowledge runs. An Argusic agent installed it in 0.1 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Session Knowledge v0.1.2 installed and verified: 47/47 tests pass, CLI commands (index, search, stats, creds, code, verify-redaction, sessions, tool) all functional, and the MCP stdio server announces 13 tools over JSON-RPC with FTS5 full-text search and SQLite credential vault.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
307
forks
12
open issues
0
watchers
4
size
0 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
under a minute
Cold machine to finish
3 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
python3 -m unittest discover -v tests/ ran 47 tests in 0.173s OK; python3 -m sessionmcp.cli search 'deploy' returned 1 result; python3 -m sessionmcp.cli creds get DATABASE_URL returned plaintext credential; MCP server tools/list returned 13 tools; install.sh completed successfully with indexing
Model tokens used
30,221
Exact commit tested
2f07e91f3571
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

echo \"MCP tools: "'$(cd /work/repo && printf '"'{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initial…
 succeeded in 0ms:
=== VERIFIED ===
Tests: 47/47 passed
CLI help: usage: sessionmcp [-h] [--json]
Stats: session 总数        1(私人排除 0)
Version: 0.1.2
MCP tools: OK, tools listed: 13 tools
All systems checked — everything works. Here's the wrap-up:
tokens used
30,221
All systems checked — everything works. Here's the wrap-up:

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 0.1 minutes, faster than the median of the 123 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 124 ai-agents projects Argusic has installed and timed, session-knowledge was the 6th fastest to reach a running state, and 96 of 124 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 0.1 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.02

Topics (from GitHub)

ai-agentsanthropicclaude-codedeveloper-toolsfull-text-searchknowledge-basellmlocal-firstmcpmcp-serversqlite

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/session-knowledge.svg)](https://argusic.com/subject/session-knowledge)

Questions

Does session-knowledge run?
Yes. session-knowledge runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test session-knowledge?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 2f07e91f3571. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test session-knowledge?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does session-knowledge take to install?
0.1 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does session-knowledge need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing session-knowledge?
Nothing did, in the recorded run: zero errors between clone and running.
How does session-knowledge compare with the alternatives?
Of the 124 ai-agents projects Argusic has installed and timed, session-knowledge was the 6th fastest to reach a running state, and 96 of 124 reached one at all.
Where is the evidence for session-knowledge?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion