What is logs-locally-plugin?

A plugin for storing AI agent session logs in a local SQLite database and browsing them through a web interface. SQLite is a small database stored as a file on your computer.

Use it to save agent logs locally and browse recorded sessions in a browser.

It keeps session history available for later review and makes it easier to inspect than scattered log files.

logs-locally-plugin — Plugin for Claude Code by Laotree

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/Laotree/logs-locally-plugin

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/plugins/laotree/logs-locally-plugin/logs-locally-plugin/github.svg)](https://agentmods.dev/plugins/laotree/logs-locally-plugin/logs-locally-plugin)

Your own site

<a href="https://agentmods.dev/plugins/laotree/logs-locally-plugin/logs-locally-plugin"><img src="https://agentmods.dev/badge/plugins/laotree/logs-locally-plugin/logs-locally-plugin/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/plugins/laotree/logs-locally-plugin/logs-locally-plugin"><img src="https://agentmods.dev/badge/plugins/laotree/logs-locally-plugin/logs-locally-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session not measured What this adds to a session before it is invoked.

When invoked not measured The manifest loads nothing itself; its 1 skill, 1 hook cost 14 tokens a session between them.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

logs-locally-plugin scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude-plugin/plugin.json · 15 lines

What it actually says

{
  "name": "logs-locally-plugin",
  "description": "Store and browse AI agent session logs locally with a SQLite database and web UI",
  "version": "1.0.0",
  "author": {
    "name": "raypar"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/Laotree/logs-locally-plugin"
  },
  "homepage": "https://laotree.github.io/logs-locally-plugin/",
  "license": "MIT"
}

Contents

What it installs

The manifest is a name and a version. 1 skill, 1 hook travel with it, and installing the plugin installs all of them — 14 tokens a session between them. Each is measured on its own page, and each can be installed alone.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 15 lines scan A 78a41d642b86

Subscribe to this mod's changes

logs-locally-plugin is a plugin published in the GitHub repository Laotree/logs-locally-plugin (4 stars, last pushed 11d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Analytics and metrics Claude Code Memory and context Rust ai-tools cli developer-tools session-logging

dead-end-registry

Approach-level negative-knowledge memory for Claude Code. Mines your transcripts (Stop/PreCompact, both async and zero added latency) for approaches you TRIED and then REVERTED (with the reason, date, and estimated token cost of the detour) into a per-repo registry. On UserPromptSubmit it injects a 'you already tried…

karanb192/claude-code-hooks · not measured

alive

Local, user-owned context for Claude Code. Keep your work in files you control.

alivecontext/alive · not measured

claude-brain

Sync and evolve your Claude Code brain across machines. Automatically exports, merges, and applies your accumulated knowledge (memory, skills, agents, rules, settings) across all your development machines via Git.

toroleapinc/claude-brain · not measured

homunculus

A Claude Code plugin that's alive. Observes everything, learns instincts, evolves capabilities. Bound to one maker.

humanplane/homunculus · not measured

pr-provenance-stamp

Embeds a reviewer-facing provenance receipt into your PR body when Claude runs gh pr create (or glab mr create). A PostToolUse hook (async, zero added latency) records a per-session ledger: tool calls, agent-authored lines, and every test/typecheck command with its real exit code; a PreToolUse (Bash) hook then rewr.