explaingit

tommy0103/obelisk

Analysis updated 2026-05-18

32JavaScriptAudience · developerComplexity · 2/5LicenseSetup · easy

TLDR

A Claude Code skill that indexes an agent's past sessions, tool calls, and workflows into a local SQLite database so the agent can query its own history.

Mindmap

mindmap
  root((repo))
    What it does
      Indexes past agent sessions
      Answers questions in plain language
    Tech stack
      JavaScript
      Node.js SQLite
      FTS5 search
    Use cases
      Recall past file changes
      Review subagent conclusions
      Search session history
    Audience
      Claude Code users
      Developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Ask the agent which files were changed the last time a specific bug was worked on.

USE CASE 2

Query what conclusions past subagent workflows reached.

USE CASE 3

Search full text across all past session messages and tool calls.

USE CASE 4

Build the index automatically the first time you install the skill.

What is it built with?

JavaScriptNode.jsSQLiteFTS5

How does it compare?

tommy0103/obeliska6216abcd/free-residential-ip-proxy-controllerearthtojake/cad-viewer
Stars323232
LanguageJavaScriptJavaScriptJavaScript
Setup difficultyeasyhardmoderate
Complexity2/54/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

First index build takes about 5 seconds per 100 sessions.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

In plain English

Obelisk is a skill for Claude Code that gives an AI agent queryable access to its own past work. Most session history tools are built for humans who want to scroll through old conversations and find a specific chat. Obelisk is built differently: it indexes past sessions, tool calls, subagents, and workflows into a local SQLite database so that the agent itself can write and run queries against that history and answer questions in plain language. The idea is that you ask a question like "which files did we change last time we worked on the authentication bug" or "what did the review workflow subagents each conclude" and the agent figures out the right query, runs it, and gives you a structured answer. You do not browse or tag anything manually. The index covers several layers of recorded activity. Sessions are stored with their title, timestamps, and git branch. Individual messages from both user and assistant turns are indexed with full text. Every tool call is captured with its name, inputs, and which file paths it touched. Subagent conversations and workflow runs are also indexed, including per-agent transcripts linked back to the workflow that spawned them. Full-text search runs across all of these through SQLite's built-in FTS5 engine. Installation is a single command using the Claude Code skills system. The first run builds the index from your existing session files, which the README says takes about five seconds for 100 sessions. After that, the index updates only when new or changed session files are detected. The runtime has no npm dependencies and is about 400 lines of JavaScript using Node 22's built-in SQLite module. The license is MIT.

Copy-paste prompts

Prompt 1
Which files did we change the last time we worked on the authentication bug?
Prompt 2
What did the review workflow subagents each conclude in my last session?
Prompt 3
Search my past sessions for any tool calls that touched the database migration file.
Prompt 4
Show me a summary of every subagent workflow I've run this week.

Frequently asked questions

What is obelisk?

A Claude Code skill that indexes an agent's past sessions, tool calls, and workflows into a local SQLite database so the agent can query its own history.

What language is obelisk written in?

Mainly JavaScript. The stack also includes JavaScript, Node.js, SQLite.

What license does obelisk use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is obelisk to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is obelisk for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.