Skip to content
davidpp.com

channelcoder, an SDK for Claude Code before there was one

Claude Code could only be driven by hand, so I wrote a TypeScript SDK around it. Three weeks later Anthropic shipped the official one and I stopped.

Earlier project · May – Jun 2025 · 3 min read

Project
channelcoder
When
May – Jun 2025
The question
Could I drive Claude Code from code before it had an SDK?
Written by
his AI agent · Claude

Where it landed

The official Claude Code SDK shipped in June 2025 and covered the need.

[Retired]

The build and the opinions are David's. The words are the agent's, drafted from his build records; he edits when he disagrees.

The itch

In May 2025 Claude Code was generally available and I used it every day, the same way everyone did: one terminal, me typing. There was no SDK to drive it from code. I was building a task orchestration tool at the time, and it needed to start sessions, give them context, follow their output and run several at once. So I wrapped an API around the CLI.

What I built

channelcoder was a TypeScript SDK over the Claude Code CLI. First commit on May 22, on npm the next day. I needed it working more than I needed it polished.

It covered what scripting a coding agent needs:

channelcoder
TypeScript SDK · npm
Sessions
Multi-turn session management.
Isolation
Git worktree mode, so parallel sessions each got their own copy of the repo.
Containers
Docker mode, for contained runs.
Execution
Detached background execution.
Streaming
An NDJSON parser, so a program could follow what a session was doing.
A prompt file, end to end
markdown + YAML frontmatterdeclared input schemaZod under the hoodvalidated, typed variablesinterpolationoptional output schema

What happened to it

channelcoder became the execution layer of my orchestration harness, scopecraft-command, which has its own page. It did that job for about three weeks.

The arc
  1. May 22, 2025First commit.
  2. May 23, 2025Published to npm.
  3. ~June 11, 2025Anthropic ships the official Claude Code SDK for TypeScript and Python. I stopped maintaining channelcoder almost right away.

The official SDK was the better long-term bet, so dropping mine was easy. For those three weeks it filled a real gap, and building it showed me what the problem looks like: sessions, isolation, streams and typed inputs.

David Paquet Pitts
Head of Delivery & Solutions at Botpress