Is Smoke Monkey an AI model?

No. Smoke Monkey is not an LLM. It is an embeddable, framework-agnostic runtime that turns LLMs (NVIDIA, Gemini, OpenAI, Claude, Ollama) into autonomous engineering agents capable of multi-step planning, calling tools, editing files, and running test loops with zero runtime dependencies.

Do I need a database (Postgres, SQLite, or Redis)?

No database is required. State is persisted through lean session files on disk, or you can plug in your own custom storage adapter. You can deploy it as a CLI, a desktop app, or inside a serverless function without provisioning a database.

How does human-in-the-loop permission gating work?

Smoke Monkey comes with three permission policies: allow-all, deny-all, and ask-default (or a custom function resolver). When a sensitive tool like edit_file or run_command is called under "ask", the runtime emits a permission.required event, pausing execution until your code or UI calls agent.resolvePermission(id, "allow" | "deny").

How does the Model Context Protocol (MCP) server work?

Smoke Monkey ships an official stdio MCP server in smoke-monkey-harness-mcp. Point Claude Code, Cursor, Codex, or opencode at it using npx -y smoke-monkey-harness-mcp to let other AI tools plan, scaffold, verify, and run agents using Smoke Monkey automatically.

What are SKILL.md skills and how do they prevent context bloat?

Skills are directories containing a SKILL.md workflow file. The system prompt only includes a one-line catalog of available skills. When a task requires specialized expertise (e.g. frontend-ui-engineering, test-driven-development, or security-hardening), the agent calls use_skill to load instructions just-in-time, saving thousands of tokens.

What is an AI Agent Harness?

An AI agent harness is the execution environment that bridges raw Large Language Models (LLMs) to real-world software engineering capabilities. While an LLM generates tokens, an AI harness manages deterministic phase loops (explore, plan, edit, verify, recover), tool execution sandboxing, token budget compaction, and safety gates needed for autonomous problem-solving.

What makes Smoke Monkey an Agentic AI runtime rather than a simple wrapper?

Unlike basic prompt-response chains, Smoke Monkey implements true agentic AI architecture: a deterministic 6-phase state machine with automatic failure recovery, runaway loop guards, 24 built-in developer tools, dynamic subcontext isolation, and interactive human-in-the-loop permission pauses.

Is Smoke Monkey Harness 100% Open Source AI?

Yes. Smoke Monkey Harness is 100% open source under the permissive MIT license with zero runtime dependencies. There is no telemetry lock-in, no mandatory cloud backend, and no database requirement—giving engineering teams complete sovereignty over their agent code.

What Agent APIs does Smoke Monkey Harness provide?

Smoke Monkey provides composable TypeScript Agent APIs: createAgent() for initialization, agent.run() for multi-turn execution, agent.on() for fine-grained lifecycle and streaming events, agent.resolvePermission() for interactive human authorization, subcontext switching APIs, and stdio Model Context Protocol (MCP) server endpoints.

Can I run completely offline without API keys?

Yes! Smoke Monkey natively supports Ollama out of the box. Set provider: "ollama" and model: "qwen3:8b" with workspacePath, and the agent will run locally on your machine with zero external network requests.

Smoke Monkey vs Anthropic Claude Code

Proprietary Terminal AI AgentUpdated: October 2026

Claude Code Runtime Alternative: Open Source Stdio MCP Agent Harness

Claude Code is Anthropic’s impressive CLI agent, but it is locked to Claude models and Anthropic’s proprietary billing. Smoke Monkey Harness provides the same developer ergonomics—AST chunk editing, bash execution, MCP servers, and permission gates—while allowing you to run NVIDIA, Gemini, OpenAI, or local Ollama models.

Comparative Benchmark: Smoke Monkey Harness TypeScript vs Anthropic Claude Code

|Verified for Node.js 18+ & Bun|100% MIT Open Source

The Executive Verdict (Quick Answer)

Why choose Smoke Monkey over Anthropic Claude Code? Use Smoke Monkey Harness if you love the developer tool suite of Claude Code but require multi-provider freedom, embeddable React UI integration, and 100% open source MIT code.

Why Developers Switch from Anthropic Claude Code to Smoke Monkey

Model Freedom: Run Claude 3.7 Sonnet, Gemini 2.0 Flash, OpenAI o3-mini, NVIDIA Nemotron, or offline Ollama.

Embeddable Everywhere: Embed inside web apps, desktop tools, or CLIs, unlike Claude Code which is strictly a terminal application.

Native Model Context Protocol (MCP): Connects directly to Claude Code via stdio (`npx -y smoke-monkey-harness-mcp`).

Drop-In UI Package: Use `@smoke-monkey/ui` to build web-based code editors like Cursor or Devin.

Detailed Feature-by-Feature Matrix

Direct side-by-side comparison of core runtime capabilities and architectural trade-offs.

Capability	Smoke Monkey Harness	Anthropic Claude Code	Key Architectural Difference
Model Support	✅ Anthropic, OpenAI, Gemini, NVIDIA, Ollama	❌ Anthropic Claude models only	Switch to local models for cost reduction or compliance.
Extensibility Format	✅ Native MCP + custom TS tools + SKILL.md	✅ MCP support + bash tools	Smoke Monkey can even serve as an MCP backend for Claude Code itself.
Embeddability	✅ Embed in React, Next.js, Node.js, Electron	❌ Standalone CLI terminal tool only	Build custom consumer or internal SaaS products on top of Smoke Monkey.

Code Implementation Comparison

Running an Engineering Task with Multi-Model Flexibility

Smoke Monkey (TypeScript)Zero Dependencies

smoke-monkey.tstypescript

1import { createAgent } from 'smoke-monkey-harness';
2
3// Switch between Claude, Gemini, or local models instantly
4const agent = createAgent({
5  provider: process.env.PROVIDER || 'anthropic',
6  model: 'claude-3-7-sonnet',
7  workspacePath: process.cwd(),
8});
9
10const result = await agent.run('Search for security vulnerabilities in API endpoints');

Anthropic Claude CodeAnthropic Claude Locked

terminalbash

1# Strictly CLI terminal execution tied to Anthropic billing
2claude "Search for security vulnerabilities in API endpoints"

Architecture Note: Smoke Monkey can be run via CLI, terminal, or embedded into full web and desktop applications.

Using Smoke Monkey as an MCP Tool for Claude Code

You don’t even have to choose between Claude Code and Smoke Monkey. By running npx -y smoke-monkey-harness-mcp, Smoke Monkey exposes its 24 tools and subcontext orchestration as an MCP server directly inside your Claude Code session.

Frequently Asked Questions

Questions Developers Ask About Anthropic Claude Code Alternatives

Q:Can Smoke Monkey edit files without wiping out untouched code?

Yes! Smoke Monkey includes `replace_file_content` and `multi_replace_file_content`, which perform surgical chunk replacements rather than rewriting entire files.

Switch to Smoke Monkey Harness Today

Build autonomous coding agents with zero runtime dependencies, deterministic 6-phase loops, and Model Context Protocol (MCP) in pure TypeScript.

npm install smoke-monkey-harness

Claude Code Runtime Alternative: Open Source Stdio MCP Agent Harness

Why Developers Switch from Anthropic Claude Code to Smoke Monkey

Detailed Feature-by-Feature Matrix

Code Implementation Comparison

Using Smoke Monkey as an MCP Tool for Claude Code

Questions Developers Ask About Anthropic Claude Code Alternatives

Q:Can Smoke Monkey edit files without wiping out untouched code?

Related Solutions & Topics

Model Context Protocol (MCP) for AI Agents: Native Stdio & SSE Integration

AST-Aware Code Editing: How AI Agents Modify Files Safely Without Full Rewrites

How to Build an Autonomous AI Coding Agent in TypeScript from Scratch

Switch to Smoke Monkey Harness Today