hara

A coding agent CLI that runs like an engineering org.

Think "Claude Code, but it operates as a configurable, governed organization of role-agents" — with routing boundaries, a dispatcher, a single source-of-truth data layer, human-in-the-loop approvals, and cron autonomy.

· TypeScript · local-first · Apache-2.0

Highlights

• An org, not just an agent — hara org "<task>" routes work to the role that owns it; hara plan "<task>" decomposes a task into a verified DAG of atoms (frame → atomize → sequence → execute → verify gate), and hara plan --parallel runs independent atoms concurrently.
• Drive it from chat — hara gateway runs your local hara from Telegram · WeChat · Discord · Feishu/Lark · Slack · Mattermost · Matrix · DingTalk · WeCom · Signal (10 platforms), with two-way images where the platform has a byte-upload API, resumable per-chat sessions, project/agent roaming, bounded per-thread queues, and approval-gated group automations. Connects out — no public webhook. See docs/gateway.md.
• Relay native coding sessions through Hara — Hara Live starts an isolated Codex or Claude Code terminal in a selected local workspace and lets Desktop or the owner-only /coding gateway commands message, read, and interrupt it. Provider history stays in its original runtime, Hara exposes only opaque local ids, and ordinary chat is never injected into a terminal.
• Real terminal UX — an ink TUI: bottom-pinned input box, plan mode (read-only investigation → the model submits its plan via exit_plan → approve → execute), narrowly scoped project approvals, private model reasoning, paste images (Ctrl+V) for vision models, light/dark theme.
• Reviewed business learning + durable memory — while tasks run, learning_capture records only bounded, redacted evidence as personal/project candidates or local organization proposals. Nothing changes future behavior until the user approves it, or an administrator approves and versions it in Hara Control; learning never expands permissions. Inspect with hara learning list and approve/reject/revoke explicitly. The separate memory_* layer retains curated facts/preferences, while /evolve status|now distills reviewable candidates and verified skills without rewriting product code, permissions, config, or system prompts.
• Multi-provider, all streamed — Anthropic (Claude), Volcengine Ark Agent Plan, or any OpenAI-compatible endpoint (Qwen/DashScope, GLM, Kimi, OpenAI), with live Markdown answers while provider reasoning stays private.
• Let Hara choose the coding executor — describe the goal to a Hara Agent; personal-space coding delegation defaults to bundled OpenCode, with Pi (experimental), Codex, and Claude Code available in global settings. There is no per-Agent runtime setup or separate OpenCode/Pi app installation. Both bundled engines use Hara's model connection, bounded file tools and in-chat approval/question cards; native Codex/Claude reuse their own installed login and session history. Existing sessions keep their original engine, and non-interactive use remains disabled by default. See coding executors for tool and verification boundaries.
• Honest under a slow network — a live "waiting for the model… Ns" status, a stall watchdog that auto-fails-over instead of hanging, terminal-native bracketed paste, big pastes folding to a token, and a startup update notice — the terminal never feels dead.
• Solid coding core — edit_file / apply_patch (atomic multi-file) with colored diffs · grep/glob/ls/codebase_search (lexical + optional semantic search over the repo) /web_fetch · fuzzy @file · /undo · /compact · Esc-to-interrupt · parallel sub-agents · MCP client · macOS sandbox.

Track it: https://github.com/hara-cli/hara · https://hara.run

Install

The npm package requires Node.js 22.23.1 or newer. If needed, upgrade first with nvm install 22 && nvm use 22. Node.js 20 is end-of-life and is not a supported Hara runtime.

npm i -g @nanhara/hara

Or a standalone binary (no Node required):

curl -fsSL https://raw.githubusercontent.com/hara-cli/hara/main/install.sh | sh

Tab completion (optional): eval "$(hara completions zsh)" in your ~/.zshrc (or bash/fish).

Or in Docker — run hara against any repo without installing Node, and as an isolated/ephemeral environment (handy for CI):

docker run --rm -v "$PWD:/workspace" -e HARA_API_KEY=sk-... ghcr.io/hara-cli/hara -p "summarize this repo"
# interactive TUI:
docker run --rm -it -v "$PWD:/workspace" -e HARA_API_KEY=sk-... ghcr.io/hara-cli/hara
# or build it yourself: docker build -t hara . && docker run --rm -v "$PWD:/workspace" -e HARA_API_KEY=sk-... hara

Or from source:

git clone https://github.com/hara-cli/hara && cd hara
npm install        # builds via the prepare script
npm install -g .   # or: npm link

If a source checkout linked before 0.122.1 later reports zsh: permission denied: hara, the old npm link is still targeting the now-internal dist/index.js. Activate the same Node installation that owns the link, run npm link again from this directory, then run rehash. npm run build and npm run doctor:local-link detect this stale link and print its exact owning bin directory. Do not repair it with chmod; the guarded executable entry is runtime-bootstrap.cjs.

Quickstart

npm i -g @nanhara/hara
hara setup               # choose a provider, masked key, and model from a list
cd your-project
hara                     # offers to write AGENTS.md, then drops you into the TUI

This is the beginning of the README. Read the rest at the original. Read the full README ↗