explaingit

forstjiri/opencode-history-fulltext-search

Analysis updated 2026-05-18

0TypeScriptAudience · developerComplexity · 2/5LicenseSetup · easy

TLDR

A plugin for the opencode terminal coding tool that adds full text search over your past session titles and messages, searchable by current folder or across everything.

Mindmap

mindmap
  root((opencode history search))
    What it does
      Full text search
      Session titles
      Message content
    Scopes
      Current directory
      Anywhere
    Filtering
      Text and reasoning only
      Skips tool noise
    Tech Stack
      TypeScript
      SQLite
      Node.js
    Usage
      Command palette
      Copy resume command

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

Quickly find an old coding session by searching what you remember typing or discussing.

USE CASE 2

Search across every opencode session on your machine, not just the current project folder.

USE CASE 3

Jump back into a session from a different directory without losing your current context.

What is it built with?

TypeScriptSQLiteNode.js

How does it compare?

forstjiri/opencode-history-fulltext-search0xradioac7iv/tempfs7vignesh/pgpulse
Stars000
LanguageTypeScriptTypeScriptTypeScript
Setup difficultyeasymoderatemoderate
Complexity2/53/54/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

Experimental, reads a large local SQLite database on every search which may slow opencode down.

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

In plain English

opencode-history-fulltext-search is a plugin for opencode, a terminal based coding tool, that adds full text search over your past session history to its command palette. It lets you search across session titles and the actual content of your messages, and you can choose to search just the current directory or every session you have ever had. The plugin adds two new commands to opencode's command palette. Search history, this dir looks only at sessions tied to the folder you are currently working in, while Search history, anywhere searches across all of your sessions no matter where they happened. As you type, results filter live and the part of the message that matched your search is highlighted and centered so you can see it in context. To keep results useful, the plugin only indexes the actual text and reasoning content of messages. It deliberately skips tool input and output, step markers, patches, and other technical noise, which the author says removes about seventy percent of rows that would otherwise clutter the results. If you pick a session from a different directory while searching everywhere, the plugin does not try to switch you into that session. Instead it copies the exact command you would need to resume it, including the correct directory, to your clipboard, and it automatically detects which clipboard tool your system has available. Under the hood, the plugin reads your local opencode history database directly and only in read only mode, so it will not corrupt your data even while opencode itself might be writing to it. You install it by adding one line to your opencode configuration file, or by running a single CLI command that patches the config for you, and opencode installs the plugin and its dependencies automatically the next time it starts. The author notes this is still an experimental, early stage tool: because it reads a large local database on every search, it may slow opencode down somewhat, and it has not yet been published to a package registry, though you can install it straight from GitHub in the meantime. The project is released under the MIT license.

Copy-paste prompts

Prompt 1
I just installed opencode-history-fulltext-search. Show me how to add it to my ~/.config/opencode/tui.json.
Prompt 2
Explain how opencode-history-fulltext-search filters out tool output and noise when indexing session history.
Prompt 3
How does opencode-history-fulltext-search read the opencode.db SQLite file without risking corruption?
Prompt 4
Walk me through using the Search history, anywhere command to resume a session from a different project folder.

Frequently asked questions

What is opencode-history-fulltext-search?

A plugin for the opencode terminal coding tool that adds full text search over your past session titles and messages, searchable by current folder or across everything.

What language is opencode-history-fulltext-search written in?

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

What license does opencode-history-fulltext-search use?

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

How hard is opencode-history-fulltext-search to set up?

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

Who is opencode-history-fulltext-search for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.