Open Harness
mifunedev/openharness
Sandbox por projeto com agente IA contínuo rodando em Docker
Ver no GitHubSandbox Docker isolado para um projeto com agente IA atuando de forma contínua. Fornece ambiente controlado onde Claude ou outro agente executa tarefas agendadas contra um repositório único, mantendo sua máquina limpa e permitindo automação enquanto você dorme.
Instalação
npx convez-ai mifunedev/openharness1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automação de tarefas agendadas em repositórios Git
- Desenvolvimento assistido por agente IA de longa duração
- CI/CD customizado com execução de agentes Claude
- Integração com Slack para agentes controlados remotamente
Veredito

Solução prática para quem quer agentes IA rodando continuamente contra um projeto, com Docker como única dependência e arquitetura clara. Bem documentada, possui integração Slack nativa e é extensível via overlays Compose.
README
A tradução para o português deste README ainda está na fila.
🏗️ Open Harness
Open Harness is a Docker-based agent harness for one project, agent-tended over time. One docker compose up gives you a long-lived sandbox where Claude (or another agent of your choice) runs against a single repo, branch, and identity — not a multi-tenant comparison rig.
- One project, one sandbox. A single container scoped to a single repo. The agent owns its branch and its workspace; you keep your laptop clean.
- Agents that work while you sleep. A tiny croner runtime reads
crons/*.mdmarkdown and wakes the agent on a schedule. - Only host dependency: Docker. No Node, no Python, no toolchain rot on your laptop.
- Composable infra. Cherry-pick Cloudflare tunnels, SSH, Caddy gateway, or pack-supplied services via Compose overlays.
- Slack-ready. The in-tree Pi extension at
.pi/extensions/slack/bridges Slack to a Pi agent — see docs/integrations/slack.md. - Multi-agent? Add a pack. Other multi-agent setups ship as separate packs — see
@ryaneggz/mifune.
📦 Install
Option A — Upstream (try it without any setup):
curl -fsSL https://oh.mifune.dev/install.sh | bash
Review-first alternative (no extra dependency):
curl -fsSL -o openharness-install.sh https://oh.mifune.dev/install.sh
# Review openharness-install.sh in your editor or pager before running it.
bash openharness-install.sh
If you already use vet, you can review and approve the same installer with vet https://oh.mifune.dev/install.sh. Docker remains the only required host dependency.
Clones into ~/.openharness, offers to share your host gh token, writes .devcontainer/.env, and builds the image (~10 min cold, ~30s warm). Only host dependency: Docker.
Option B — Fork and clone (recommended for self-hosting):
# 1. Fork on GitHub, then clone YOUR fork:
git clone https://github.com/<your-org>/<your-fork>.git && cd <your-fork>
# 2. Bootstrap — installer auto-detects the local clone, no env vars needed:
bash scripts/install.sh
Option C — Clone upstream, then re-point to your repo:
git clone https://github.com/mifunedev/openharness.git my-harness && cd my-harness
git remote set-url origin https://github.com/<your-org>/<your-repo>.git
bash scripts/install.sh
OH_GITHUB_REPO=<your-org>/<your-fork> curl -fsSL \
https://raw.githubusercontent.com/<your-org>/<your-fork>/main/scripts/install.sh | bash
Review-first fork install:
curl -fsSL -o openharness-install.sh \
https://raw.githubusercontent.com/<your-org>/<your-fork>/main/scripts/install.sh
# Review openharness-install.sh, then run it against your fork.
OH_GITHUB_REPO=<your-org>/<your-fork> bash openharness-install.sh
If your fork uses a default branch other than main, set OH_GITHUB_REF=<branch> and replace main in the URL. See Installation docs for all environment overrides.
🚀 Use it
cd ~/.openharness
make shell # enter the isolated sandbox
# inside the sandbox, launch any core agent:
# claude # Claude Code (default)
# codex # OpenAI Codex CLI
# opencode # OpenCode (optional: set install.opencode: true in harness.yaml and rebuild)
# pi # Pi Coding Agent
# deepagents # LangChain DeepAgents (optional: set install.deepagents: true in harness.yaml and rebuild)
# hermes # Nous Research Hermes (optional: set install.hermes: true in harness.yaml and rebuild)
# grok # xAI Grok Build (optional: set install.grok_build: true in harness.yaml and rebuild)
make destroy # stop and remove the sandbox
make help # all targets
🧪 Testing
- Property-based testing convention: docs/property-testing.md
Prefer VS Code or remote SSH? Use the Dev Containers extension's "Attach to Running Container" against openharness, or SSH into your host first and then attach.
⚙️ Configure (optional)
harness.yaml is the tracked config for shared non-secret settings (optional
installs, Slack allowlists, compose overlays, and any sandbox defaults you
intentionally want in git). .devcontainer/.env is gitignored and holds
host-local defaults generated by the installer (SANDBOX_NAME, TZ, git
identity) plus secrets (GH_TOKEN, SLACK_APP_TOKEN, SLACK_BOT_TOKEN).
Active keys in harness.yaml override .devcontainer/.env. Apply changes
with make destroy && make sandbox.
git clone https://github.com/mifunedev/openharness.git && cd openharness
make sandbox
make shell
✨ What you get
| Core agents | Defaults: Claude Code, Codex, Pi. Optional: OpenCode, DeepAgents, Hermes, Grok Build |
| Runtimes | Node 22, pnpm, Bun, uv (Python) |
| DevOps | Docker CLI + Compose, GitHub CLI, cloudflared, tmux, croner |
| Browser | agent-browser + Chromium (headless) |
| One project, one sandbox | A single container scoped to a single repo and branch |
| Crons | Markdown-defined schedules in crons/*.md driven by the in-container croner runtime |
| Multi-agent | Install a harness pack such as @ryaneggz/mifune for additional multi-agent setups |
📚 Where to go next
- Quickstart — full step-by-step
- Crons — markdown-defined autonomous tasks
🧹 Cleanup
make destroy
🤝 Contributing & community
Open Harness is maintained under the mifunedev org — the canonical repo is github.com/mifunedev/openharness. To run your own, fork it (see Option B above) and open PRs back upstream. Issues and PRs welcome; if Open Harness is useful to you, please give us a star.
📄 License
MIT.