Day 11: The Ecosystem Day

Two npm releases, audit trail upgrades, and three calls with people who want to build with us.

← Day 10: Context Belongs to People, Not Agents

Not every day is about the product

Some days you write features. Some days you build the ground they stand on.

Today was an ecosystem day. No new UI. No new agent capabilities. Instead: infrastructure, tooling, and conversations.

openclaw-node v0.2.0 and v0.2.1

openclaw-node is the Node.js client library for OpenClaw — the runtime Pinchy is built on. I started it as a standalone open-source package a week ago. Today it got its first real feature upgrade.

v0.2.0 added tool stream event support. When an OpenClaw agent uses a tool — reads a file, searches the web, runs a command — those events now flow through the chat() async generator. Before, you'd only see the final response. Now you see everything the agent does along the way.

Why does this matter? Because Pinchy needs to log what agents do, not just what they say.

v0.2.1 followed a few hours later: reduced package size, dropped Node 18 support (it's EOL), and added a proper CI gate with branch protection on main. The kind of release hygiene that makes a package trustworthy.

8 commits. Two releases. The foundation that the next feature builds on.

Audit trail: now with tools

Pinchy's audit trail logs every message, every agent creation, every settings change. Immutable. HMAC-signed. The kind of thing a compliance officer wants to see.

But there was a gap: tool usage. When an agent reads a document or executes a command, that wasn't being recorded. For a personal project, fine. For an enterprise deployment where someone needs to answer "what exactly did the AI do with our data?" — not fine.

Today's PR closes that gap. Tool calls now appear in the audit log with structured data: which tool, what input, what result. Built directly on the new openclaw-node tool stream support. The npm package wasn't just a side project — it was a dependency I needed.

This is the part of open source I love. Build a library. Use the library. Find the gaps. Fix the library. Ship both.

Three calls, one pattern

Between coding sessions, I had three video calls today. All with people from the AI and software architecture space. All initiated through LinkedIn.

I'm staying vague on purpose — these are early conversations, not announcements. But the pattern is clear: people are interested. Not in the abstract "cool project" way. In the "how can we work together" way.

Software architects who want to evaluate Pinchy for their clients. Developers building complementary tools who see integration opportunities. People who've been looking for exactly this: a self-hosted, enterprise-ready layer on top of OpenClaw.

Two weeks ago, Pinchy was a README and a Docker Compose file. Today, people are scheduling calls to talk about collaboration. Build in Public works. Not because of reach or impressions — but because building openly attracts the people who think the same way you do.

The flywheel

Today made something visible that I've been feeling all week: the ecosystem flywheel is starting to turn.

openclaw-node makes it easier to build on OpenClaw. Pinchy uses openclaw-node. Features I build for Pinchy (like tool stream support) flow back into openclaw-node. People discover Pinchy through the npm package, or through LinkedIn, or through the blog. Some of them reach out. Some of those conversations turn into collaborations.

None of this was planned as a growth strategy. It's just what happens when you build useful things in the open.

What's next

Merge the audit trail PR. Start working on the security hardening that multiple people have asked about — agent permissions, prompt injection mitigations, the questions that enterprise buyers always ask and that most AI tools can't answer yet.

Day 12: The Audit Trail Closes →

Follow the build: github.com/heypinchy/pinchy