PARTNERS CIRCLE OPEN SOURCE

The clearest look at how we build

Tools we needed while building systems and could not buy off the shelf. The source is all on GitHub, free for anyone to use — and the closest look you can get at the standard of our work.

PROJECTS

MeMesh

A local collaboration layer for AI coding agents

Let AI coding agents share project memories, exchange questions and replies, and hand over work. Ask Codex to implement and Claude Code to review, then send feedback to the original conversation. Free and open source, with memories and collaboration records stored locally.

WHO IT FITS
People using Claude Code, Codex, Hermes Agent and other AI coding agents
INSTALL
npm install -g @pcircle/memesh
  • Keep preferences, project decisions and useful fixes
  • Memories stay local, with no extra cloud memory service
  • Share memories across Claude Code, Codex, Hermes Agent and compatible tools
  • Exchange questions, replies and work between Claude Code and Codex conversations

Toonify MCP

Trims large tool output before it fills up the conversation

Commands and file reads in Claude Code often return large, messy output — full API responses, long logs, stack traces. Toonify MCP compresses this automatically before it enters the context window, running in the background with no change to how you already work.

WHO IT FITS
Developers running Claude Code against large JSON, YAML, or test output
INSTALL
git clone https://github.com/PCIRCLE-AI/toonify-mcp.git
  • Automatically compresses large JSON, YAML, and API responses
  • Trims long test failures and stack traces
  • Runs in the background — no change to your existing workflow

XylonStudio

Chip timing analysis: runs OpenROAD for real, reads back measured numbers, and repairs only with your approval

Give it RTL and timing constraints (SDC). XylonStudio runs a resource-bounded OpenROAD flow on your own machine and reads back native measurements — how late the worst path is (WNS), how late all violations are combined (TNS), and the worst path itself. When there is a violation it proposes one bounded repair based on that measurement, waits for your approval, reruns, and shows the before-and-after numbers side by side. Your design files never leave your machine.

WHO IT FITS
Engineers doing digital chip timing analysis, and students learning that work
INSTALL
git clone https://github.com/kevintseng/xylon-studio.git
  • Preflight before anything runs — if the environment, resources, or inputs are wrong it stops there, not halfway through
  • One repair at a time, applied only when you approve it; then a rerun and a side-by-side comparison
  • A number it could not measure is never backfilled from another one, and a run that failed is never shown as done
  • Its own stated boundary: timing analysis and bounded repair — no claim of automatic timing closure or foundry signoff

WHY WE OPEN-SOURCE

Problems we solved for ourselves, shared so others skip the same detour

Each of these started as a real problem in front of us, not a planned open-source release. The code is public — use it directly, read it, or open an issue. This is not a paid service: no customization quotes, no support contracts. If you need us to build a system for you, see our services.

The source is on GitHub

Free to use, source fully public. Reach out if you want to know how it's built, or about working together.