项目介绍

Created By
xiaoxiaoningdesuia year ago
A lightweight large language model input-output tracker—launch with a single command, integrate effortlessly.
Overview

What is LLM-Tracker?

LLM-Tracker is a lightweight input-output tracker for large language models, designed to record interactions between applications and models during development.

How to use LLM-Tracker?

To use LLM-Tracker, compile the project using Go, and launch it with the command ./llm-tracker.exe --configFile=config.toml. Ensure you have the necessary configuration files in place.

Key features of LLM-Tracker?

  • Hides the tools list in input to reduce clutter during interactions.
  • Supports both streaming and non-streaming responses, allowing for efficient processing.
  • Compatible with various modes including mcp/function_call/chat.
  • Escapes special characters in input and output for better readability.

Use cases of LLM-Tracker?

  1. Tracking input-output interactions for large language models in real-time.
  2. Integrating with applications that utilize models like ollama and deepseek.
  3. Debugging and optimizing model interactions by analyzing recorded data.

FAQ from LLM-Tracker?

  • What models does LLM-Tracker support?

LLM-Tracker currently supports models deployed with ollama, deepseek, and theoretically any model compatible with OpenAI SDK.

  • How do I integrate LLM-Tracker with my application?

Change the IP and port in your workflow/client code to 127.0.0.1:1234 to connect to LLM-Tracker.

  • Is LLM-Tracker free to use?

Yes! LLM-Tracker is open-source and available under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
xiaoxiaoningdesui
Star
2
Language
Go
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago