Skip to content
/

MyCoder.ai

mycoder-ai · drivecore/mycoder · ★ 567 · last commit 2026-01-07

Primitive shape
No installable primitives
00

Summary

MyCoder.ai — Summary

MyCoder is a command-line AI coding agent (npm package mycoder) that spawns parallel sub-agents for concurrent task processing, supporting multiple model providers (Anthropic Claude, OpenAI, Ollama). Installed globally via npm install -g mycoder, it runs as its own runtime rather than a plugin layer on top of another tool. The agent system includes a rich tool set: shell execution, text editor, browser/fetch, MCP servers, sleep, think, and an agentStart/agentDone tool pair that explicitly spawns and tracks sub-agents with unique IDs. GitHub integration mode lets it work directly with issues and PRs; interactive corrections via Ctrl+M mid-run allow human steering. Context window management includes automatic message compaction for long-running agents.

Differs from seeds: closest to claude-flow in spawning parallel sub-agents at runtime for concurrent execution, but MyCoder is a standalone CLI tool (not a Claude Code plugin) and is model-agnostic across three provider families. Unlike taskmaster-ai (which decomposes a spec into tasks) or openspec (which writes delta specs), MyCoder is an autonomous executor that reads project files, writes code, and manages its own sub-agent lifecycle end-to-end without a formal spec layer.

01

Overview

MyCoder.ai — Overview

Origin

MyCoder is developed by DriveCore (github.com/drivecore/mycoder) under the MIT license. The project is a monorepo with three packages: mycoder (CLI), mycoder-agent (core agent library), and mycoder-docs (documentation site). Version analyzed: last commit 2026-01-07. The tool is distributed as a global npm package and described as "Simple to install, powerful command-line based AI agent system for coding."

Philosophy

MyCoder's philosophy centers on autonomous parallel execution with human-in-the-loop correction:

  • Parallel Execution: Sub-agents are spawned for concurrent task processing, reducing wall-clock time
  • Human Compatible: Reads README.md, project files, and runs shell commands to build its own context — no special setup files needed
  • Self-Modification: Can modify its own code; was built and tested by writing itself
  • Interactive Corrections: Users can send corrections mid-run without stopping the agent (Ctrl+M)
  • Message Compaction: Automatically manages context window for long-running agents

Manifesto-Style Quotes

From README:

"Simple to install, powerful command-line based AI agent system for coding."

"AI-Powered: Leverages Anthropic's Claude, OpenAI models, and Ollama for intelligent coding assistance"

"Self-Modification: Can modify code, it was built and tested by writing itself"

"Human Compatible: Uses README.md, project files and shell commands to build its own context"

GitHub Comment Commands

MyCoder extends into GitHub workflows via comment commands:

"/mycoder implement a PR for this issue"
"/mycoder create an implementation plan"
"/mycoder suggest test cases for this feature"

This enables trigger-from-issue automation without a separate orchestration layer.

02

Architecture

MyCoder.ai — Architecture

Distribution

  • npm package: mycoder — global install
  • Monorepo: packages/cli, packages/agent, packages/docs
  • Supported providers: Anthropic Claude, OpenAI models, Ollama (local)

Install

npm install -g mycoder

Repository Structure

packages/
  cli/
    bin/             # CLI entry point (mycoder binary)
    mycoder.config.js
  agent/
    src/
      core/
        toolAgent/
          toolAgentCore.ts    # Main agent loop
          config.ts           # System prompt + agent config
      tools/
        agent/                # agentStart, agentDone, agentMessage, agentExecute, listAgents
        fetch/                # HTTP fetch tool
        interaction/          # userPrompt tool
        mcp.ts                # MCP server integration
        session/              # Session management
        shell/                # Shell command execution
        sleep/                # Sleep/wait tool
        textEditor/           # File editing tool
        think/                # Internal reasoning tool
        utility/              # Utility tools
  docs/               # Documentation website

Required Runtime

  • Node.js (recent LTS)
  • npm/pnpm
  • Git (for GitHub mode)
  • Optional: Ollama (for local model support)

Configuration

MyCoder supports 7 configuration file locations in priority order:

  1. mycoder.config.js in project root
  2. .mycoder.config.js in project root
  3. .config/mycoder.js in project root
  4. .mycoder.rc in project root
  5. .mycoder.rc in home directory
  6. mycoder field in package.json
  7. ~/.config/mycoder/config.js (XDG standard)

Supported formats: .js, .ts, .mjs, .cjs, .json, .jsonc, .json5, .yaml, .yml, .toml

Target AI Tools

Standalone CLI — not a plugin for Claude Code or Cursor. Supports:

  • Anthropic Claude (default: claude-3-7-sonnet-20250219)
  • OpenAI models
  • Ollama (local, via baseUrl: 'http://localhost:11434')

Key Config Options

{
  provider: 'anthropic',
  model: 'claude-3-7-sonnet-20250219',
  maxTokens: 4096,
  temperature: 0.7,
  githubMode: true,
  headless: true,
  interactive: true,
  mcp: { servers: [...] }
}
03

Components

MyCoder.ai — Components

CLI Binary

mycoder — global npm binary with the following invocation modes:

  • mycoder -i — interactive mode
  • mycoder "prompt" — single prompt run
  • mycoder -f prompt.txt — run from file
  • mycoder --interactive "prompt" — with Ctrl+M corrections
  • mycoder --userPrompt false "prompt" — fully automated (no user prompts)
  • mycoder --upgradeCheck false "prompt" — no version check (CI-safe)

Agent Tools (from packages/agent/src/tools/)

Category Tool Purpose
Agent lifecycle agentStart Spawn a named sub-agent with goal/context/workingDirectory
Agent lifecycle agentDone Mark sub-agent complete with result
Agent lifecycle agentMessage Send message to running sub-agent
Agent lifecycle agentExecute Execute sub-agent synchronously
Agent lifecycle listAgents List active sub-agents
Shell shell/ Execute shell commands
Files textEditor/ Read and edit files
Web fetch/ HTTP fetch and web browsing
MCP mcp.ts Connect to Model Context Protocol servers
Interaction interaction/userPrompt Prompt the user (when enabled)
Reasoning think/ Internal chain-of-thought reasoning
Timing sleep/ Wait/sleep
Session session/ Session management and compaction

Sub-Agent System

The agentStart tool accepts:

  • description — brief purpose (max 80 chars)
  • goal — main objective
  • projectContext — environment context
  • workingDirectory — optional working dir
  • relevantFilesDirectories — glob patterns
  • userPrompt — whether sub-agent can prompt user (default false)

Returns agentId for tracking. Sub-agents run with the same tool set as the parent.

MCP Support

MyCoder can connect to any MCP server via config:

mcp: {
  servers: [{ name: 'example', url: '...', auth: {...} }],
  defaultResources: [...],
  defaultTools: [...]
}

Context Management

  • Reads README.md, project files, shell output to build context naturally
  • No special context files required
  • session/ tool handles message compaction when context window pressure grows

GitHub Integration

githubMode: true enables:

  • Working with GitHub issues and PRs
  • Comment-triggered automation (/mycoder <instruction>)
  • PR creation and issue closing
05

Prompts

MyCoder.ai — Prompts

Prompt 1: agentStart Tool Schema

Technique: Schema-constrained sub-agent spawning with explicit context handoff

Verbatim from packages/agent/src/tools/agent/agentStart.ts:

const parameterSchema = z.object({
  description: z
    .string()
    .describe("A brief description of the sub-agent's purpose (max 80 chars)"),
  goal: z
    .string()
    .describe('The main objective that the sub-agent needs to achieve'),
  projectContext: z
    .string()
    .describe('Context about the problem or environment'),
  workingDirectory: z
    .string()
    .optional()
    .describe('The directory where the sub-agent should operate'),
  relevantFilesDirectories: z
    .string()
    .optional()
    .describe('A list of files, which may include ** or * wildcard characters'),
  userPrompt: z
    .boolean()
    .optional()
    .describe(
      'Whether to allow the sub-agent to use the userPrompt tool (default: false)',
    ),
});

const returnSchema = z.object({
  agentId: z.string().describe('The ID of the started agent process'),

Analysis: The Zod schema serves as both runtime validation and LLM guidance via .describe() fields. projectContext and relevantFilesDirectories are the context handoff mechanism. Sub-agents are isolated from parent by default (userPrompt: false).

Prompt 2: MyCoder Config System Prompt Injection

Technique: Configurable system prompt extension for project-specific patterns

From mycoder.config.js:

export default {
  provider: 'anthropic',
  model: 'claude-3-7-sonnet-20250219',
  // customPrompt can be a string or array
  customPrompt: [
    'Custom instruction line 1',
    'Custom instruction line 2',
  ],
};

Analysis: The customPrompt field appends to the default system prompt, allowing project-specific patterns without modifying agent code. Array form supports multi-line structured instructions. This is the closest MyCoder comes to OAC's context file system — lightweight and optional.

Prompt 3: GitHub Comment Command Trigger

Technique: Structured command injection from GitHub issue/PR comments

/mycoder implement a PR for this issue
/mycoder create an implementation plan
/mycoder suggest test cases for this feature

Analysis: Natural language triggers parsed from GitHub comment events. The /mycoder prefix signals intent; everything after is the agent's goal prompt. MyCoder reads the issue/PR context as additional context alongside the comment instruction.

09

Uniqueness

MyCoder.ai — Uniqueness & Positioning

Differs From Seeds

Closest to claude-flow in spawning parallel sub-agents for concurrent execution. The architectural delta: MyCoder is a standalone CLI tool (not a Claude Code plugin) that supports three model providers (Anthropic, OpenAI, Ollama), uses schema-constrained tool calls (Zod) for sub-agent spawning, and requires no special project setup files — it reads README.md and project files organically. Unlike taskmaster-ai (spec → tasks) or kiro (spec-driven interactive workflow), MyCoder has no formal spec or planning layer; the agent plans internally via the think tool. Unlike agent-os or openagentscontrol (both requiring context file setup), MyCoder is context-file-free.

Distinctive Opinion

"Human Compatible: Uses README.md, project files and shell commands to build its own context."

The anti-pattern is explicit: no setup friction. MyCoder bets that a well-written README + project structure is sufficient context for productive coding agents, rather than requiring teams to author dedicated context files.

The agentStart/agentDone pair is a first-class parallel execution primitive, not a workaround — MyCoder treats concurrent sub-agents as the standard mode for complex tasks.

Positioning

MyCoder targets developers who want a powerful autonomous coding agent without setup overhead. It is more autonomous than OAC (no mandatory approval gates) and more provider-flexible than tools locked to Claude. GitHub comment triggers position it for teams wanting asynchronous issue-driven development.

Observable Failure Modes

  1. Context drift: Without structured context files, sub-agents may make different assumptions about project patterns, leading to inconsistent code across parallel executions.
  2. No corpus compounding: Each session starts fresh. Teams cannot leverage accumulated decisions or learnings the way AgentOps does.
  3. Shallow validation: No built-in adversarial reviewer or multi-judge consensus. Quality depends on the main agent's self-checking.
  4. Dormancy: Last commit was 2026-01-07 — project may be in maintenance mode given competitive field.
  5. Sub-agent isolation gap: Sub-agents share the filesystem but have no shared state mechanism. Race conditions on shared files are possible in parallel runs.

Cross-References

  • Website: mycoder.ai (marketing site) + docs.mycoder.ai (docs)
  • Discord: discord.gg/5K6TYrHGHt
  • Mentions Ollama support positioning it for local/private model use
04

Workflow

MyCoder.ai — Workflow

Standard Workflow

  1. Initialize: Read README.md, project files, shell state to build context
  2. Plan (internal): Main agent uses think tool for internal reasoning
  3. Execute: Agent issues shell commands, reads/edits files, fetches URLs
  4. Sub-agent Delegation (optional): Spawn sub-agents for concurrent parallel tasks via agentStart
  5. Wait / Collect: Main agent waits for sub-agents via agentDone
  6. Validate: Run tests via shell; check output
  7. Report: Return result to user

GitHub Mode Workflow

  1. Issue or comment triggers run (/mycoder <instruction>)
  2. MyCoder reads the issue/PR context from GitHub API
  3. Creates a branch, implements changes
  4. Opens PR or posts comment with results
  5. Monitors CI and responds to review feedback (if configured)

Approval Gates

MyCoder has minimal built-in approval gates by default:

  • --interactive flag + Ctrl+M: User can send corrections mid-run
  • --userPrompt true (default off for sub-agents): Sub-agents can request user input
  • No mandatory plan approval before execution

This is a deliberate design: autonomous execution is the primary mode; --interactive corrections are opt-in.

Phase-to-Artifact Map

Phase Artifact
Context building Internal context window (no file)
Planning Think tool output (internal)
Sub-agent spawn agentId + parallel execution
Implementation Code changes in filesystem
Validation Shell test output
GitHub mode PR + issue comment

Execution Modes

Mode Flag Behavior
Batch (default) Runs to completion, no interruption
Interactive --interactive Ctrl+M sends corrections
GitHub --githubMode Triggered by issue/comment
Automated --userPrompt false --upgradeCheck false Fully headless
06

Memory Context

MyCoder.ai — Memory & Context

State Storage

MyCoder uses the conversation/context window as its primary state mechanism — it is not a corpus-compounding framework. State is ephemeral per session.

  • Project context: Built organically by reading README.md, project files, and shell output at session start
  • Session messages: In-memory conversation history
  • Context compaction: The session/ tool handles automatic message compaction when context window pressure grows — older messages are summarized to free capacity

No Persistent State Files

Unlike AgentOps (.agents/) or ccmemory, MyCoder writes no persistent cross-session state files by design. Each session starts fresh from the project's filesystem state.

Sub-Agent Context Handoff

When spawning sub-agents via agentStart, context is passed via:

  • projectContext — explicit string passed to sub-agent
  • relevantFilesDirectories — glob patterns for relevant files
  • workingDirectory — scoped working directory

Sub-agents cannot read parent agent's conversation history; context must be explicitly packaged.

customPrompt as Lightweight Context

The customPrompt config field provides a thin mechanism for injecting project-specific context into every session without creating context files. It appends to the default system prompt.

Message Compaction

From README: "Message Compaction: Automatic management of context window for long-running agents"

The session/ tool module handles compaction — summarizing older turns to maintain conversation within token limits. Details of the compaction strategy are in packages/agent/src/tools/session/.

Persistence

Layer Persistence
Conversation history Session only (not persisted)
Code changes Filesystem (persisted)
Project context files Not written by MyCoder
Sub-agent results Returned via agentDone, not stored
07

Orchestration

MyCoder.ai — Orchestration

Multi-Agent Pattern

Pattern: Parallel fan-out

The main agent spawns multiple sub-agents via agentStart for concurrent execution. Each sub-agent runs the same tool set (shell, textEditor, fetch, etc.) independently. The AgentTracker.ts maintains a registry of active sub-agents with their status.

Sub-Agent Spawn Mechanism

agentStart tool — spawns a new agent process with:

  • Unique agentId (returned to parent)
  • Independent conversation history
  • Scoped working directory
  • Explicit context passed via projectContext field

Communication: agentMessage (send message to running agent), agentDone (collect result).

Subagent Definition Format

None — MyCoder sub-agents have no definition format. They receive a goal string and projectContext string at spawn time. No persona files, no YAML config. Sub-agents are ephemeral and purpose-bound.

Execution Mode

One-shot (default batch mode) or interactive-loop (with --interactive flag). GitHub mode is event-driven (triggered by issue/comment).

Isolation Mechanism

Process — each sub-agent runs as a separate Node.js process. No git worktrees, no containers. Sub-agents share the same filesystem.

Multi-Model

No — single provider/model per session, configured in mycoder.config.js. Multi-provider support exists (Anthropic, OpenAI, Ollama) but is a config choice, not role-based routing.

Orchestration Flow

User prompt (CLI or GitHub comment)
  ↓
Main agent — reads project context (README, files, shell)
  ↓
Plans internally (think tool)
  ↓
For complex tasks: spawn sub-agents (agentStart) in parallel
  ↓
Sub-agents execute independently with their scoped context
  ↓
Main agent collects results (agentDone)
  ↓
Main agent synthesizes and validates
  ↓
Returns result / opens PR

Consensus Mechanism

None. Main agent makes decisions; sub-agents are executors.

Crash Recovery

No documented crash recovery. Context window compaction handles long-running sessions.

Context Compaction

Automatic via session/ tool. Older messages summarized to maintain context window capacity.

08

Ui Cli Surface

MyCoder.ai — UI / CLI Surface

CLI Binary

  • Name: mycoder
  • Package: mycoder (npm global)
  • Is thin wrapper: No — MyCoder IS the runtime. Does not wrap Claude Code, Codex, or Cursor.
  • Subcommands: Primarily flag-based rather than subcommand-based

Key flags:

mycoder -i                          # interactive mode
mycoder "prompt"                    # single run
mycoder -f prompt.txt               # from file
mycoder --interactive "prompt"      # Ctrl+M corrections
mycoder --userPrompt false          # automated (no user prompts)
mycoder --upgradeCheck false        # CI-safe (no version check)
mycoder --githubMode true           # GitHub integration
mycoder --headless false            # show browser
mycoder --profile                   # performance profiling

Local UI

None. Terminal output only.

MyCoder outputs hierarchical, color-coded logs to terminal:

  • Each sub-agent gets a random distinct chalk color for output differentiation
  • Log levels are hierarchical

IDE Integration

None. MyCoder is a standalone CLI tool, not an IDE plugin.

Observability

  • Hierarchical color-coded logging per sub-agent (color assigned at spawn)
  • --profile flag enables performance profiling
  • Sub-agent activity log shows agent IDs, goals, and status
  • No persistent log files or dashboards

GitHub Integration

When githubMode: true:

  • Reads issues and PRs via GitHub API
  • Opens PRs automatically
  • Monitors CI via GitHub API
  • Responds to /mycoder comment commands on issues/PRs

Interactive Corrections

Press Ctrl+M during a run to enter correction mode:

  1. Type correction or additional context
  2. Press Enter
  3. Agent incorporates message into decision-making

MCP Support

Configured via mycoder.config.js:

mcp: {
  servers: [{ name: 'example', url: '...', auth: { type: 'bearer', token: '...' } }],
  defaultResources: ['example://docs/api'],
  defaultTools: ['example://tools/search']
}

CI/Automation

mycoder --userPrompt false --upgradeCheck false "run the test suite and fix failures"

Fully non-interactive. Exit codes indicate success/failure.

Related frameworks

same archetype · same primary tool · same memory type

claude-mem (thedotmack) ★ 78k

Background worker service captures every tool call as an observation, AI-compresses sessions, and auto-injects relevant past…

pi (badlogic/earendil) ★ 55k

A minimal, hackable, multi-provider terminal coding agent that adapts to your workflows via npm-installable TypeScript Extensions…

Agent Skills (Addy Osmani) ★ 46k

Encodes senior-engineer software development lifecycle as 23 auto-routed skills and 7 slash commands for any AI coding agent.

wshobson/agents Plugin Marketplace ★ 36k

Single Markdown source for 83 domain-specialized plugins that auto-generates idiomatic artifacts for five AI coding harnesses.

TabbyML/Tabby ★ 34k

Self-hosted AI coding assistant server (alternative to GitHub Copilot) with admin dashboard, RAG-based completions, and multi-IDE…

Compound Engineering ★ 17k

Make each unit of engineering work compound into easier future work via brainstorm→plan→execute→review→learn cycles.