explaingit

rahul06x1/agentsense

Analysis updated 2026-05-18

1PythonAudience · developerComplexity · 3/5LicenseSetup · moderate

TLDR

A local, no-signup tool that records every tool call your AI agent makes via an MCP proxy, stores traces in SQLite with PII redacted, and lets you replay runs against different models to see exactly where decisions diverge.

Mindmap

mindmap
  root((agentsense))
    What it does
      Trace agent runs
      PII redaction
      Replay and diff
    Components
      MCP proxy
      SQLite store
      FastAPI UI
      Capture SDK
    Use Cases
      Debug agents
      Model comparison
      Compliance audits
    Key Properties
      Zero code change
      Local only
      Apache 2.0
Click or tap to explore — scroll the page freely

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

Debug a misbehaving AI agent by capturing its full MCP tool call trace without changing any agent code.

USE CASE 2

Compare how two different AI models would have decided on the same task by replaying a recorded trace against each.

USE CASE 3

Add compliance-ready audit-trail logging to an AI agent that handles user data, with PII automatically redacted before it reaches the database.

What is it built with?

PythonSQLiteFastAPIOpenTelemetryMCP

How does it compare?

rahul06x1/agentsensea-bissell/unleash-liteabhiinnovates/whatsapp-hr-assistant
Stars111
LanguagePythonPythonPython
Setup difficultymoderatehardhard
Complexity3/54/53/5
Audiencedeveloperresearcherdeveloper

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

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires an MCP-compatible agent config to capture, live replay needs an OpenAI-compatible or AWS Bedrock API key.

Use, modify, and distribute freely for any purpose, including commercial use, as long as you include the license notice.

In plain English

This tool helps you understand what an AI agent actually did during a run. If your agent called the wrong tool, made an unexpected decision, or ran up a large bill and you are not sure why, this project records every step at the protocol level so you can look back at exactly what happened. It runs entirely on your own machine with no cloud account required. The core piece is an MCP proxy, a transparent go-between that sits in front of any MCP server your agent uses. You point your agent's configuration at the proxy instead of the real server, and from that moment on every tool call, its inputs and outputs, timing, and cost are captured without any change to your agent's code. The traces are stored in a local SQLite database as complete records with no fields left out. Two additional protections are built in. First, personal information is detected and replaced with consistent placeholder tokens before anything is ever written to the database, so sensitive data from users never lands in your logs. Second, the redaction uses a fixed process so that when you replay a trace later the placeholder values stay consistent and the replay makes sense. After capturing a run you can open a local web interface, built with FastAPI and plain HTML, to browse the trace as a tree of steps with a timeline view. The Compare tab lets you load two different traces side by side and see precisely where their decision sequences first split apart. There is also a live replay feature: you pick any captured trace, choose a different AI model, and the tool re-runs the session using the same recorded tool results rather than calling live services again. It then shows you a diff of what that model would have decided versus what your original agent did. This costs no extra API calls for the tool side. For agents you control directly, a Python SDK lets you record richer detail such as the reasoning steps and model calls that the proxy cannot see. The SDK writes to the same SQLite store and uses the same redaction path. The project is licensed under Apache 2.0.

Copy-paste prompts

Prompt 1
My MCP-based AI agent keeps making wrong tool calls. Show me how to place the agentsense proxy in front of my MCP server so I can see every tool call and its inputs and outputs.
Prompt 2
Using agentsense, how do I replay a captured Claude agent trace against GPT-4o to see where their decisions first diverge?
Prompt 3
Show me how to use the agentsense capture SDK to record reasoning steps and LLM calls from a custom Python agent session.
Prompt 4
How does agentsense redact PII before writing to SQLite, and how can I verify that no sensitive user data is stored in my traces?

Frequently asked questions

What is agentsense?

A local, no-signup tool that records every tool call your AI agent makes via an MCP proxy, stores traces in SQLite with PII redacted, and lets you replay runs against different models to see exactly where decisions diverge.

What language is agentsense written in?

Mainly Python. The stack also includes Python, SQLite, FastAPI.

What license does agentsense use?

Use, modify, and distribute freely for any purpose, including commercial use, as long as you include the license notice.

How hard is agentsense to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is agentsense for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub rahul06x1 on gitmyhub

Verify against the repo before relying on details.