Skip to content
BranchesTags

Repository files navigation

CrewCoder

Extensible, security-conscious coding-agent platform

SDK checks npm (sdk) npm (sdk) npm (sdk) npm (client) License Node

CrewCoder Monorepo

This directory is an npm-workspaces monorepo for the CrewCoder Packages. The root package owns shared tooling, workspace scripts, and a single lockfile, while each package keeps its runtime dependencies and build entrypoints. For more thorough Documentation go here CrewCoder Docs

CrewCoder

CrewCoder is an extensible, security-conscious coding-agent platform designed for interactive development, multi-worker orchestration, durable sessions, detached goals, and remote execution. Can also be used for the CrewCode ecosystem.

Packages

Package npm name Runs on What it is
crewcoder-agent @onpoint-dev-tools/crewcoder-agent Node.js 22+ / standalone binary The agent harness: evented agent loop, providers, local tools, durable sessions, goals, crews, extensions, ACP and fleet servers, and the crewcoder / cc CLI.
crewcoder-tui @onpoint-dev-tools/crewcoder-tui Node.js 22+ terminal Custom terminal UI (no Ink/React/blessed/curses) driven by the agent's JSON event stream, locally or over SSH.
crewcoder-sdk @onpoint-dev-tools/crewcoder-sdk Node.js 22+ host process Supported TypeScript API for embedding CrewCoder in-process, plus an authenticated fleet client for remote runners.
crewcoder-client @onpoint-dev-tools/crewcoder-client Browsers, Electron renderers, webviews Browser-safe client for authenticated CrewCoder runners. Web-platform APIs only: no Node.js imports, no local files, no tool execution, no stored provider credentials.

Package READMEs: agent · tui · sdk · client

The CrewCoder agent harness

crewcoder-agent is the harness every other package talks to. The TUI spawns it and reads its JSON events, the SDK embeds it in-process, and the client talks to it over the authenticated fleet HTTP/SSE API. Everything below lives in that package.

Runtime core

  • Evented agent loop. Every turn emits typed JSON events (assistant deltas, thinking deltas, tool calls, approvals, usage, errors) over stdout or SSE, so all frontends share one contract. See TUI_BACKEND_CONTRACT.md.
  • Durable sessions. Sessions persist under the CrewCoder home and support resume, branch, prune, export, checkpoints and rewind, search, compaction, and session why provenance. See SESSION_DURABILITY.md, SESSION_CHECKPOINTS.md, AUTO_COMPACTION.md.
  • State directory. /.crewcoder (override with CREWCODER_HOME, falls back to ~/.crewcoder) holds config.json, fleet-token, sessions/, goals/, extensions/, workers/, cache/, logs/.
  • Modes. general (default coding), plugin (CrewCode app plugin architect), extension (CrewCoder extension architect). See EXTENSION_MODE.md.

Providers

Built-in adapters cover Claude Code Agent SDK, Codex (official app-server threads with a guarded WebSocket/SSE fallback), OpenCode, Grok CLI over ACP stdio, OpenAI, Anthropic, OpenRouter, xAI, DeepSeek, and Mistral, using checked process, HTTP/SSE, WebSocket, continuation, fallback, and replay transport profiles. Thinking/reasoning streams are first-class and user-visible. Context windows resolve from provider metadata first, then a strict-match 24-hour OpenRouter catalog cache. See PROVIDERS.md, CODEX_TRANSPORT.md, CLAUDE_AGENT_SDK.md, MODEL_CONTEXT_WINDOWS.md, PARALLEL_TOOL_CALLS.md.

Tools

Local tools include read/write/edit, transactional edits, grep, list-files, bash and background jobs, git primitives, LSP-backed code intelligence and symbol edits, docs lookup, memory (remember), worker delegation, and plugin/extension scaffolding and validation. Only tools marked parallel-safe run concurrently; sequential tools stay ordering barriers, and tool output is size-limited and redacted. See CODE_INTELLIGENCE_TOOLS.md, GIT_PRIMITIVE_TOOLS.md, TRANSACTIONAL_EDITS_AND_BACKGROUND_JOBS.md, TOOL_OUTPUT_SAFETY.md.

Orchestration

  • Worker crews and teams — named workers with their own identity files, sequential crew runs, declarative teams in crewcoder.json, and session handoffs. See WORKER_CREWS.md.
  • Crew tasks — durable project-wide task IDs with dependency edges, surfaced in the TUI sidebar. See CREW_TASKS.md.
  • Detached durable goals — a CrewCoder-owned supervisor with maker/verifier separation, not a provider feature. See DURABLE_GOALS.md.

Security and trust

Approval modes (never, review, always, full-access, sandboxed), sandbox and trust tiers, runtime guardrails, explicit external-directory grants, repository rules, audit logging and redaction, and a mandatory bearer token for the fleet API. See SANDBOX_AND_TRUST.md, RUNTIME_GUARDRAILS.md, INTERACTIVE_APPROVAL_CONTROL.md, AUDIT_AND_REDACTION.md, EXTERNAL_DIRECTORIES.md.

Extensibility

Capability-based CrewCoder extensions declare contribution points in crewcoder.extension.json — providers, tools, skills, prompt packs, commands, workflows, context providers, validators, approval policies, hooks, and sandboxed Live UI — all gated by config, trust tier, and capability checks. Separately, CrewCoder can generate CrewCode app plugins (crewcode.plugin.json). See EXTENSIONS.md, EXTENSION_HOOKS.md, EXTENSION_REGISTRY.md, LIVE_UI_COMPONENTS.md, WORKFLOWS.md.

STILL WORKING ON EXTENSION REGISTRY

Ways to connect

Method Best for Transport Authentication
Local CLI/TUI Working on the current machine Local subprocess Local OS account
Remote agents Local TUI, remote workspace SSH stdio SSH keys
ACP Third-party ACP-compatible editors ACP over stdio, often through SSH Process boundary or SSH
Fleet mode SDKs, apps, dashboards, automation, concurrent runs HTTP + SSE/WebSocket Fleet bearer token plus tunnel/HTTPS
In-process SDK Embedding in a trusted Node.js host Direct TypeScript calls Host process boundary

See FLEET_MODE.md, ACP_ADAPTER.md, SDK.md, and REMOTE_AGENTS.md.

CLI launch

After linking or installing the CLI packages, crewcoder and its short alias cc invoke the same command. With no arguments, either opens the CrewCoder TUI.

Common commands

npm install
npm run build
npm run typecheck
npm run test
npm run check

Run one workspace directly:

npm run dev -w @onpoint-dev-tools/crewcoder-agent
npm run typecheck -w @onpoint-dev-tools/crewcoder-sdk
npm run dev -w @onpoint-dev-tools/crewcoder-tui

TypeScript SDK and browser client

@onpoint-dev-tools/crewcoder-sdk 0.6.0 is the supported Node.js 22+ API for custom interfaces, automated workflows, custom tools, programmatic agent tests, and authenticated remote fleet clients. It supports typed events/errors, durable or in-memory sessions, approvals, follow-ups, cancellation, persistent fleet history, event cursors, reconnect, HTTP/SSE controls, and safe WebSocket connection metadata.

import { createCrewCoderSession } from "@onpoint-dev-tools/crewcoder-sdk";

const session = createCrewCoderSession({ cwd: process.cwd(), provider: "codex", approval: "review" });
session.subscribe((event) => {
  if (event.type === "assistant_delta") process.stdout.write(event.text);
});
await session.prompt("Explain the failing tests.");
session.dispose();

Browsers, Electron renderers, and webviews should use @onpoint-dev-tools/crewcoder-client instead, which talks to an authenticated runner over HTTP/SSE with web-platform APIs only:

import { CrewCoderClient } from "@onpoint-dev-tools/crewcoder-client";

const client = new CrewCoderClient({ baseUrl: "https://runner.example.com", token });
const run = await client.createRun({ prompt: "Fix the failing tests", cwd: "/workspace/project" });
await client.streamEvents(run.runId, (event) => { /* render */ });

See SDK.md for SDK examples, FLEET_MODE.md for the VPS workflow, and SDK_RELEASE.md for compatibility and release gates.

Detached durable goals

crewcoder goal start "Complete the migration and stop when contract tests pass" --provider codex
crewcoder goal status
crewcoder goal approve

The TUI exposes the same workflow through /goal. Goals survive closing the TUI and pause safely for approvals or recoverable blockers. See DURABLE_GOALS.md.

Standalone VPS runner

Build a Linux x64 executable that does not require Node.js on the VPS:

npm run build:standalone -w @onpoint-dev-tools/crewcoder-agent
crewcoder deploy user@vps --binary crewcoder-agent/dist-bin/crewcoder-linux-x64 --execute
ssh -N -L 8787:127.0.0.1:8787 user@vps

Standalone deployment is loopback-only and intended for SSH terminal, ACP-over-SSH, local-TUI-over-SSH, or tunneled fleet access. Fleet API authentication is mandatory and uses an automatically generated private bearer token.

Run the TUI on your PC while the agent and workspace stay on the VPS:

crewcoder-tui \
  --remote user@vps \
  --remote-cwd /srv/projects/my-project

See REMOTE_AGENTS.md for the remote TUI workflow. The fleet guide includes deployment, token-safe curl, SDK, WebSocket, Python, rotation, and troubleshooting examples at FLEET_MODE.md.

CI integrations

The repository root is a GitHub composite action for crewcoder run --ci. GitLab users can include .gitlab/crewcoder.gitlab-ci.yml, and local repositories can install a managed review hook with:

crewcoder hook install --budget 25k

By default the GitHub action builds the agent from its tagged source checkout; pass a preinstalled executable to skip the build. GitLab requires a runner-provided CrewCoder binary. See CI_INTEGRATIONS.md.

Debugging

CREWCODER_TUI_SYSTEM_LOGS=1 npm run dev -w @onpoint-dev-tools/crewcoder-tui
CREWCODER_DUMP_MODEL_INPUT=1 npm run dev -w @onpoint-dev-tools/crewcoder-tui

Inspired By

  • Pi
  • Hermes

Documentation

Links

About

CrewCoder is an extensible, security-conscious coding-agent platform designed for interactive development, multi-worker orchestration, durable sessions, detached goals, and remote execution. Can also be used for the CrewCode ecosystem.

crewcode-docs.logixhub.icu/

Topics

agent-harnessai-agentscoding-agentcoding-assistantcrewcodecrewcoderdevdeveloperdeveloper-toolsdevelopmentllm-agents

Resources

Readme
Apache-2.0 license
Activity
Custom properties

Stars

0 stars

Watchers

0 watching

Forks

0 forks
Report repository

Releases

Packages

Contributors

Languages