Selected projects & contributions

The work.
In the open.

Desktop products. Connected systems. The small fix that makes everything work better. A closer look at what we build—and how we contribute.

01 / DESKTOP PRODUCTOpen source · MIT

EzDSH

A desktop home for DeepSeek Harness.

Bringing an AI runtime into a usable desktop application means connecting the interface, the processes behind it and the way it reaches users.

EzDSH combines an Electron and React interface with a bundled runtime, plugin integration and connected workspaces. The public repository includes packaged releases for macOS and Windows.

  • Electron
  • React
  • TypeScript
DeepSeek Harness workspace running inside the EzDSH desktop application
EzDSH / DESKTOP EXPERIENCEDeepSeek Harness workspace running inside EzDSH · Official project image ↗
ENGINEERING FOCUS

Desktop integration
Runtime lifecycle
Release packaging

PUBLIC ARTIFACTS

Source code, project documentation and downloadable desktop releases.

FOLLOW THE WORKBrowse releases ↗Contribution history ↗
02 / INTEGRATION PROTOTYPEPublic source · Testnet demo

ReleaseRail

From contribution evidence to an auditable payment workflow.

ReleaseRail connects GitHub contribution evidence to policy-controlled payments through KeeperHub, with explicit human approval and independently checked transaction receipts.

The TypeScript service exposes a CLI, MCP tools and a local audit console. Its documented demo uses Base Sepolia testnet, demonstrating the integration and approval flow.

  • TypeScript
  • MCP
  • viem
  • Zod
ENGINEERING FOCUS

MCP integration
Approval boundaries
Idempotent execution

PUBLIC ARTIFACTS

CLI and MCP implementation, a documented testnet demonstration and redacted evidence.

FOLLOW THE WORKRead the walkthrough ↗Inspect public evidence ↗
03 / FOCUSED CONTRIBUTIONMerged · 21 Sep 2026

KeeperHub#2525

A small change. A clearer decision for the agent.

Action discovery did not say whether an action could run through the direct protocol execution tool. Callers could discover an action, then learn its limits only when the call failed.

This contribution adds protocolDirectExecution, derived from the execution registry, consistently across MCP and HTTP schemas. The routing guidance explains when to use direct execution, a sibling tool or a workflow.

  • TypeScript
  • MCP
  • API contracts
  • Regression tests
CONTRIBUTION SCOPEPR / 2525
THE MISSING SIGNAL

Discover action Try a call Learn its limits

THE ADDED CONTRACTprotocolDirectExecution
true

Direct protocol
execution

false

Check a sibling tool
or workflow path

Merged into the upstream staging branch on 21 September 2026. Contributed under our earlier GitHub account, WalkmanHenry. A focused open-source contribution to the upstream project.

Merge record ↗
THE RIGHT SCOPE FOR YOUR NEXT STEP

A whole product.
Or the one bug blocking it.

We take on focused fixes, small features, API integrations and QA work as well as larger builds. You get an agreed outcome, appropriate checks and a clear handoff—even when the job is small.