Claude Node

claude-node

A thin subprocess-based Python bridge for persistent Claude Code sessions.

claude-node drives the local claude CLI as a long-lived subprocess and communicates with it over stream-json. Because it runs the installed CLI directly as its runtime, Python code gets access to Claude Code's native behavior through the CLI itself — achieving maximum compatibility with the CLI.

This is not a higher-level reimplementation or a message API wrapper. It is a direct bridge to the installed claude executable.

The CLI bridge

claude-node sits at the subprocess boundary:

- Maximum compatibility: because claude-node delegates entirely to the local claude CLI, any capability the CLI exposes is available — skills, slash commands, tools, agent modes, and session management.
- Process isolation: the Claude runtime lives in its own OS process, independent of the Python interpreter.
- Protocol transparency: raw stream-json behavior is visible and debuggable.
- Easy embedding: drop it into any Python environment — workers, web backends, job runners, or supervisor processes.

Positioning

claude-node gives Python direct control over the real local Claude Code runtime. It preserves native CLI capabilities with stream-json, explicit session lifecycle, and process-level supervision — built for embedding and integration, not for hiding Claude behind another framework.

What this is not

* Not another high-level agent framework
* Not a reimplementation of Claude
* Not a wrapper that hides the CLI behind a new abstraction
* Not a workflow or memory platform

What this is

* A thin Python runtime layer for controlling the real local Claude Code process
* A subprocess-first integration surface with explicit session and process control
* A practical foundation for embedding Claude Code…