Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

redthread

Latest version: v0.15.0

Overview

Last scanned
18 Nov 2026
Published
18 Nov 2026
PyPI package Publisher: sina5
1 Versions
53 Downloads

Scan summary

redthread was last scanned on 18 Nov 2026 at version 0.15.0. Risk score 0 of 100. No malicious behavior was detected.

  • Releases: First and only release on 18 Nov 2026.
  • Findings: No rules fired in version 0.15.0.
  • Downloads: 53 downloads.

Versions

1 version published
Versions and the rules that fired in each
VersionPublishedStatus
0.15.0 LATEST 18 Nov 2026 No rules fired

No rules fired in 0.15.0

Findings

Findings for v0.15.0. The score is a capped sum of the weights of the rules that fired — not CVSS, not exploitability, and not a probability. It is not comparable across packages with different scan coverage.

The score describes 0.15.0; other versions have their own rules, not their own score.

README

The publisher’s own README, as collected from the registry.

Redthread

Portable, git-backed memory for AI agents and multi-phase workflows.

CI Docs License: MIT Version

A coding agent usually keeps its memory in a local folder (.claude/, .agent/) on one machine. Redthread replaces this folder with a git-backed memory store that an MCP server gives to the agent. Each machine that clones the store shows the same memory to the agent.

The same store also keeps the context of a multi-phase pipeline, for example train → eval → present or build → test → present. This context is an append-only, content-addressed memory. A git remote is its source of truth. Any node can clone the store and continue a run. Each phase publishes a curated handoff to the subsequent phase.

Phase names are data, not code. Each project declares its own pipeline in project.yaml. Code below the adapter layer has no domain-specific terms.

Read the docs →

Features

  • Agent memory over MCP: Set the MCP configuration of a coding agent (Claude Code, Cursor, Windsurf, VS Code, and others) to a Redthread store. Do not use a local .claude/.agent folder.
  • One registration for many projects: Run mcp-serve without --store. Each workspace then gets the store that its committed .redthread.yaml file names. Thus, one global MCP entry (Claude Code user scope, Cursor, Windsurf, VS Code) operates correctly in all your repos. In a repo that has no store yet, the agent's store_init call makes one as an orphan-branch worktree, with no CLI step.
  • Portable by design: The key of each entry is project_id / run_id / phase / entry_id. The key is never a hostname or an absolute path. To move a phase to a different machine during a run, use redthread resume.
  • Domain-neutral phase adapters: The same core operates an ML pipeline (train/eval) and an app pipeline (build/test). It has no special cases for each domain.
  • Content-addressed artifacts: Redthread commits small files inline. Large files go to a blob backend that you can replace. A sha256 hash identifies each file.
  • Curated handoffs: Each phase publishes one small, validated contract for the subsequent phase. The subsequent phase does not read the raw entry log.
  • Report, deck, and docs from handoffs: redthread present makes a markdown report, a slide deck, and a docs-site tree from a run.
  • Worktree mode: The store can be an orphan-branch git worktree of your code repo. Redthread does not change the active branch of that repo.
  • Automatic attach on a new machine: A committed .redthread.yaml marker lets redthread mcp-serve and redthread attach find and attach the store automatically. On a new clone, only git clone and the same MCP command are necessary. You do not have to remember flags.

Install

pip install redthread          # or: uv tool install redthread

Three ways to use Redthread

Option 1 — Let the agent do the setup (recommended)

Copy the AGENTS.md example into your project. The next time an agent opens the project, it uses Redthread as its memory:

  1. If Redthread is not installed, the agent stops and asks you to install it. It gives you the two commands to run.
  2. If the repo has no store yet, the agent asks you, and then calls store_init.

By default, the store is an orphan-branch git worktree of the same repo. Thus, you do not have to set up a second remote, and the active branch of the repo does not change.

Option 2 — Register the MCP server manually

Register the server one time. You do not make a store first, and you do not give a --store path: the same registration serves every project. The first time an agent uses Redthread in a repo, it asks you, then calls store_init, which makes the store as an orphan-branch worktree at ./redthread-store. Select your client:

claude mcp add --scope user redthread -- uvx redthread mcp-serve

If redthread is already installed, remove uvx:

claude mcp add --scope user redthread -- redthread mcp-serve

To make sure that the server operates, type /mcp in Claude Code. The redthread server shows as connected with 19 tools.

Cursor does not install MCP servers with a CLI command. It uses a one-click deeplink. This command makes the deeplink and opens it. It uses only Python, which Redthread already uses:

python -c "
import base64, json, webbrowser
config = {'command': 'uvx', 'args': ['redthread', 'mcp-serve']}
encoded = base64.b64encode(json.dumps(config).encode()).decode()
webbrowser.open(f'cursor://anysphere.cursor-deeplink/mcp/install?name=redthread&config={encoded}')
"

Cursor shows an install confirmation. Accept it to complete the procedure.

code --add-mcp '{"name":"redthread","command":"uvx","args":["redthread","mcp-serve"]}'

If you use the Insiders build, use code-insiders instead of code.

You can also connect Windsurf, Claude Desktop, Codex CLI, Gemini CLI, and the Claude Agent SDK. For each client, refer to MCP client setup.

After you connect the agent, tell it to call agents_md_bootstrap. This tool writes the usage policy from Option 1 into the AGENTS.md/CLAUDE.md file of the project. Future sessions then use this memory automatically.

Option 3 — Use the CLI (no agent necessary)
redthread run start --store ./my-store
redthread log <run_id> build note '{"msg": "hello"}' --store ./my-store
redthread read <run_id> --store ./my-store

If you use a source checkout, run uv sync first. Then put uv run before each command.

Docs

The full docs (usage, architecture, store format) are at sina5.github.io/redthread. The source is in docs/. MkDocs Material builds the site. To show the docs locally, run this command:

uv run --group docs mkdocs serve

Changelog

For release notes, refer to CHANGELOG.md.

Development

uv sync
uv run pytest
uv run ruff check .

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.

Where it’s listed

The probe returned only these fields for this server — auth requirement, protocol and tool list weren’t observed, so they’re not shown (never guessed).

  • pypi-releases redthread

References

The publisher’s own links, as the registry reports them. These are not sources for the assessment on this page.

Scan your whole stack

Group 1261154050 1
Group 1261154050
 

From OX Research Newsroom

Vulnerability Insights

OpenSSH Password Authentication Bypass on Alpine Linux (*sshole) – CVE-2026-123158

PHP CVE 2026 109618 & CVE 2026 109619
Vulnerability Insights

PHP CVE-2026-109618 & CVE-2026-109619: What to Do Before the Details Drop

Nodejs Brotli Flaw
CVE

Node.js Brotli Decoder Out-of-Bounds Write (RCE) – CVE-2026-111497

Frame 2085668439 (1)
Group 1261154229