Type moragent. Log in with what you already have. Talk to one executive orchestrator while specialized subagents run inside the same native terminal app, sharing tasks, specs and memory.
curl -fsSL https://raw.githubusercontent.com/EduardoMoraga/moragent/master/install.sh | shThen: moragent — Node ≥ 18, zero npm dependencies, MIT.
◆ Hola. Conectado: Claude (suscripción), Codex. ¿Qué construimos?
tú › API de tareas con tests
◆ Plan (M · 2 subagentes): backend escribe la API; frontend arma el cliente de prueba.
◆ backend (codex) terminó T-0001 ✓
◆ Revisión lista: tests verdes, memoria actualizada.
Connect what you already have
The app detects subscription CLIs already logged in on your machine and can also run native API loops with your own keys or local Ollama. Credentials stay local in ~/.moragent/credentials.json or environment variables.
Use vendor CLIs headlessly for subagents and orchestration. MORAGENT normalizes their streams into one in-app event format.
Native tool loop with project-confined read_file, write_file, edit_file, grep and bash.
Run the orchestrator or workers against a local OpenAI-compatible endpoint. Useful when you want fully local execution.
Inside the app
The native TUI is the default entry point. The older mora CLI still works for scripts, CI and external agents.
/helpShow available commands./loginConnect subscriptions, API keys or Ollama./equipoView or reassign the crew; English alias: /crew./orquestador <motor>Pick the orchestrator engine; English alias: /orchestrator./memoria [texto]Show memory or search notes; English alias: /memory./plan <texto>Ask for an explicit plan before running subagents./abrir <rol|id>Pop an agent out into Orca, herdr or tmux; English alias: /open./cancel · /salirCancel running work or quit; English alias: /exit.Why MORAGENT
Running one AI coding agent is easy. Running a crew that shares context, respects decisions and avoids stepping on each other needs a native harness plus a disk-backed engine room.
| Capability | MORAGENT v5 | Notes |
|---|---|---|
| Full-screen native TUI | ✓ | moragent opens the app; no tmux required. |
| Subagents inside the app | ✓ | Streams appear in the chat and sidebar. |
| Optional external panes | ✓ | /abrir can pop out to Orca, herdr or tmux. |
| Layered memory | ✓ | canonical · episodic · transient · skills. |
| Spec-driven phases | ✓ | explore → propose → spec → design → tasks → apply → verify → archive. |
| Obsidian second brain | ✓ | mora brain link connects the project graph. |
Probado con
Verified live on September 27, 2026 with subscription CLIs and the native API loop.
Headless streaming execution, workspace-write, no prompts.
Streaming JSON with auto permission mode and allowed tools.
Sandboxed streaming execution.
JSON streaming and session recovery.
Tested with qwen3.5:9b writing and reading files.
Platforms.
Apple Silicon, native app and external pane workflows.
Node 18, 20 and 22.
CI passes on Node 18, 20 and 22. The terminal app and external panes still need live Windows verification.
FAQ
No. MORAGENT v5 is a standalone terminal app. Multiplexers are optional and only used when you choose to pop an agent out with /open or /abrir.
One executive orchestrator coordinates specialized subagents. Each role can use a different subscription CLI, API model, or the same engine if that is all you have.
No. There is no MORAGENT account, server or telemetry. Your configured providers talk directly from your machine to their own services; Ollama stays local.
MORAGENT is free and MIT-licensed. You pay only for your existing subscriptions or API usage.
Yes. In a folder without .moragent/, the TUI asks what you want to build and initializes the project inline.
Everything lives in .moragent/ plus managed comment blocks in instruction files such as AGENTS.md and CLAUDE.md. Remove those and the repo is back to its prior shape.