DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to look up the commands that failed last time with Session Knowledge

Filter past Bash and MCP calls to only the failures so you do not repeat known traps.

Who it is forA developer hitting a flaky deploy, build, or third-party API call who thinks they have seen this error before.

The problemThe fix for a past failure is buried in tool call history, and re-running the failing command wastes time.

The outcomeThe past failed calls for the topic, with arguments and results, so the known trap is visible before retrying.

What you need first

  • Claude Code with session transcripts in ~/.claude/projects/
  • Python 3.10+ with FTS5 in the bundled sqlite3 (on macOS, install from python.org or run brew install python)
  • git and bash to clone and run install.sh
  • Terminal access to run the CLI and restart Claude Code

Steps

  1. git clone https://github.com/nameforjt-afk/session-knowledge.git
  2. cd session-knowledge then bash install.sh
  3. Restart Claude Code.
  4. python3 -m sessionmcp.cli tool "docker build"
  5. python3 -m sessionmcp.cli tool "stripe" --errors

Prompt for your agent

Using the session-knowledge repo, call find_tool_call with a query for <command or service> and errors_only set to true. Expect past failed calls with their arguments and results. Verify the arguments before rerunning any command.

Caveat. The tool history comes from Claude Code transcripts only, so calls made in Cursor, Copilot, or outside Claude Code will not show up.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page