MCP 서버는 1개의 클로드 코드 세션을 스파 종료하고 터미널 백엔드 (tmux 또는 iTerm2)를 통해 다른 클로드 코드 (또는 Codex) 세션의 팀을 관리 할 수 있습니다.

소개

maniple은 MCP 서버이며, Claude Code가 다른 Claude Code 또는 Codex 세션의 "team"을 오케스트라 할 수 있도록 슬래시 명령 세트입니다. 터미널 백엔드 (tmux 또는 iTerm2)를 사용하여 새로운 터미널 세션을 종료하고 Claude Code 또는 Codex를 실행합니다.

왜?

• 주의: 많은 개발 작업은 논리적으로 병렬화 될 수 있지만, 병렬화는 제한된 관심을 가진 인간에게 어렵습니다. Claude, meanwhile, 매우 효과적입니다.
• ** 텍스트 관리 : ** worker에 대한 Offloading 구현은 신선한 컨텍스트 창 (스마트)를 구현하고, 관리자의 컨텍스트를 무료로 유지한다.
• ** 배경 작품 : ** 때때로 Claude Code가 연구해야 하거나 작업의 주요 스레드를 차단하지 않고 질문에 대답합니다. -Visibility: maniple 스파셋 실제 클레임 코드 또는 코덱 세션. 당신은 그들을 볼 수 있습니다, 중지 및 제어를 가지고, 또는 그들을 닫습니다.

Maniple MCP Server

An MCP server that allows one Claude Code session to spawn and manage a team of other Claude Code (or Codex) sessions via terminal backends (tmux or iTerm2).

Introduction

maniple is an MCP server and a set of slash commands for allowing Claude Code to orchestrate a “team” of other Claude Code or Codex sessions. It uses terminal backends (tmux or iTerm2) to spawn new terminal sessions and run Claude Code or Codex within them.

Why?

• Parallelism: Many development tasks can be logically parallelized, but managing that parallelism is difficult for humans with limited attention spans. Claude, meanwhile, is very effective at it.
• Context management: Offloading implementation to a worker gives the implementing agent a fresh context window (smarter), and keeps the manager’s context free of implementation details.
• Background work: Sometimes you want to have Claude Code go research something or answer a question without blocking the main thread of work.
• Visibility: maniple spawns real Claude Code or Codex sessions. You can watch them, interrupt and take control, or close them out.

But, why not just use Claude Code sub-agents, you ask? They’re opaque – they go off and do things and you, the user, cannot effectively monitor their work, interject, or continue a conversation with them. Using a full Claude Code session obviates this problem.

Terminal Backends

maniple supports two terminal backends:

Backend selection order:

1. MANIPLE_TERMINAL_BACKEND environment variable (tmux or iterm)
2. Config file setting (terminal.backend)
3. Auto-detect: if TMUX env var is set, use tmux; otherwise iTerm2

Git Worktrees: Isolated Branches per Worker

A key feature of maniple is git worktree support. When spawning workers with use_worktree: true (the default), each worker gets:

• Its own working directory - A git worktree at {repo}/.worktrees/{name}/
• Its own branch - Automatically created from the current HEAD
• Shared repository history - All worktrees share the same .git database, so commits are immediately visible across workers

Worktree naming depends on how workers are spawned:

• With an issue ID: {repo}/.worktrees/{issue_id}-{badge}/
• Without: {repo}/.worktrees/{worker-name}-{uuid}-{badge}/

The .worktrees directory is automatically added to .gitignore.

Codex Support

Workers can run either Claude Code or OpenAI Codex. Set agent_type: "codex" in the worker config (or set the default in the config file) to spawn Codex workers instead of Claude Code workers.

Features

• Spawn Workers: Create Claude Code or Codex sessions with multi-pane layouts
• Terminal Backends: tmux (cross-platform) and iTerm2 (macOS)