PTENES
Local runtime for coding agents

One place to orchestrate your agents

Run DSH, Codex CLI, Claude Code, Git, and GitHub CLI in the same workspace, with persistent sessions and isolated worktrees.

Start the guide View on GitHub
Visual environment for orchestrating coding agents
What it is

Your harness becomes an operations center

A local, auditable layer that connects DSH to interactive agents without handing over control of the host Docker.

🧠 Three agents, one workspace

DSH, Codex, and Claude see the same projects, Git, and persistent authentications.

🧵 Persistent sessions

Tmux keeps each task active even when the browser closes, with input and output through the dashboard.

🌿 Safe parallelism

Optional worktrees create isolated branches and directories to reduce collisions between agents.

How it works

From request to session in a few steps

DSH calls MCP tools; the orchestrator validates the project and opens the agent in a tmux session that you can monitor via the web or CLI.

DSH or dashboard→ Authenticated API→ Optional worktree→ Tmux→ Codex · Claude · Shell
Prerequisites

The basics to get started

The build downloads DSH and the other CLIs. You only need Docker and the accounts you plan to use.

Docker + Compose

On Debian or Ubuntu, use the included installer.

./scripts/install-docker-debian.sh

Interactive accounts

OpenAI, Anthropic, and GitHub are authenticated through their official flows.

./scripts/login.sh all

OpenRouter or Ollama

DSH can use the cloud or a local model on the host.

./scripts/configure-openrouter.sh
User guide · step by step

Install, authenticate, and orchestrate

The commands below are the same ones used by the real project.

1

Clone the project

Download the runtime and enter the folder.

git clone git@github.com:inematds/dsh-orchestrator.git
cd dsh-orchestrator
2

Run the bootstrap

It generates the token, chooses available ports, builds the image, and starts the services.

./scripts/bootstrap.sh
3

Complete the interactive logins

Credentials stay outside the project tree, in the runtime data directory.

./scripts/login.sh codex
./scripts/login.sh claude
./scripts/login.sh github
4

Open an isolated session

Use the dashboard or internal CLI to start an agent in its own worktree.

./scripts/shell.sh
orch start codex --cwd /workspace/meu-repo \
  --name api --prompt "implemente os testes" --worktree
5

Monitor and chat

List sessions, capture output, or send new instructions without losing the process.

orch list
orch output ID --lines 500
orch send ID "rode os testes e corrija as falhas"
Examples

Workflows that are ready to use

The same infrastructure can be operated manually or through DSH via MCP.

🧭 DSH as coordinator

DSH lists sessions, delegates an implementation to Codex, and monitors the output through structured MCP tools.

🔀 Two agents in parallel

Codex works on the API while Claude explores the documentation, each in its own branch and worktree.

Roadmap

A foundation ready to grow

The core already works; upcoming phases can expand observability and governance.

NOW
Local multi-agent runtimeDashboard, API, CLI, MCP, tmux, worktrees, persistent authentication, and backup.
NEXT
Per-project policiesPermission profiles, concurrency limits, and automatic agent selection.
FUTURE
History and metricsStructured events, costs, timings, and dashboard-guided resumption.