Skip to main content

learnlance 🧠🔍

A learning companion for Claude Code. Every time Claude finishes a turn and has generated or edited code, learnlance quietly:

  1. reads the session transcript and pulls out the code that was just written,
  2. asks Claude "what concepts could a developer learn from this?" — e.g. "you used a delta function, here's what delta encoding is",
  3. merges those concepts into a persistent knowledge graph, and
  4. regenerates an interactive HTML graph you can open any time.

No API key required. By default it reuses the claude CLI you're already logged into (your Claude Code subscription), so there's nothing extra to set up.

So instead of code just appearing, you build up a visual map of everything you've picked up along the way — new nodes light up as 🌱 new topics learned.

Why it won't slow you down or break your session

  • The API call runs in a detached background process — Claude Code never waits.
  • The hook is wrapped so any failure is logged and swallowed; it can never interrupt your coding session.
  • Turns with no substantive code make no API call (no cost, no noise).

Install (no pip, no API key)

# just install the Claude Code Stop hook — it uses your logged-in `claude`
python -m learnlance install

Run this from the learnlance/ project folder. That's it — start (or restart) Claude Code and code as usual.

If claude isn't on your PATH, point learnlance at it:

python -m learnlance config --claude-bin "C:\path\to\claude.cmd"

Prefer a global learnlance command? pip install -e . in this folder, then use learnlance instead of python -m learnlance everywhere.

Prefer a direct API call instead of the CLI? learnlance config --backend api --set-key sk-ant-...

Use it

learnlance show      # render + open the interactive knowledge graph in your browser
learnlance list -v   # list learned concepts (with explanations) in the terminal
learnlance stats     # quick counts, broken down by category
learnlance help      # show every available command

The show view opens with a live loading spinner while it renders, then two declutter controls in the sidebar: show related concepts (reveal the dimmed umbrella nodes) and a min link strength slider (hide one-off links).

Add a concept Claude missed

learnlance add "debouncing"                 # searches the current dir for the topic
learnlance add "topological sort" --path ./src
learnlance add "event sourcing" --force     # add even if it's not found in the code

learnlance greps your codebase for the topic, sends the matching snippets to Claude, and adds the concept (and any tightly-related ones actually present) just like the hook does.

Clear the graph

learnlance clear "delta encoding"   # remove one concept (and any orphaned related nodes)
learnlance clear                    # wipe the entire graph (asks first; -y to skip)

Per-session markdown recaps are written to ~/.learnlance/insights/<session>.md.

Configuration

learnlance config                      # show current settings
learnlance config --cli-model haiku    # make the cli backend use a faster model
learnlance config --max-topics 3       # fewer concepts per turn
learnlance config --background off      # run inline (blocks until analysis is done)
learnlance config --disable             # pause without uninstalling the hook
learnlance config --backend api --set-key sk-ant-...   # switch to the API backend

Everything lives under ~/.learnlance/: graph.json (the graph), graph.html (the visualization), insights/ (markdown recaps), learnlance.log (diagnostics).

Uninstall

python -m learnlance uninstall

How it works (internals)

File Role
hook.py Stop-hook entry; spawns the detached worker
transcript.py Parses Claude Code's JSONL transcript for generated code
insights.py Generates insights — via the claude CLI (default) or the API
codesearch.py Finds where a topic lives in your code (powers add)
graph.py Merges concepts into the persistent knowledge graph
viz.py Renders the offline, self-contained HTML graph
spinner.py The animated terminal loading indicator
install.py Wires the hook into ~/.claude/settings.json

Zero third-party dependencies by design — the hook must run reliably wherever Claude Code launches it.

Metadata

Release files for learnlance-univ 0.2.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for learnlance-univ 0.2.3
File Size Uploaded
learnlance_univ-0.2.3.tar.gz 74.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for learnlance-univ 0.2.3
File Interpreter ABI Platform
learnlance_univ-0.2.3-py3-none-any.whl Python 3 none any Details

Total release size: 139.0 kB

Release files / learnlance_univ-0.2.3.tar.gz

Download URL learnlance_univ-0.2.3.tar.gz
Size 74.1 kB
Tags Source
SHA-256 checksum
How to use checksums
9fa5f9d78427d480672bac171c9d68067df9a5ea6b83972f41072bd73b2f4c21
BLAKE2b-256 checksum
How to use checksums
229ba34793a9c316435c9f6cfe39af00f525317e1254588e56e9b63defb2e3a5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.

Transparency log

Release files / learnlance_univ-0.2.3-py3-none-any.whl

Download URL learnlance_univ-0.2.3-py3-none-any.whl
Size 64.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ed84ec64e03ca01f782bc5217a10e408bd0170ded317ccdac41a35c80fd212c1
BLAKE2b-256 checksum
How to use checksums
f1b9dca6eb0855b41b4e39d6d9ef23ebb6cdc66b07d545c87ca69d980177ceec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 24, 2026.

Transparency log

Release history Release notifications | RSS feed

0.2.7

2 release files

0.2.5

2 release files

This release

0.2.3 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page