enowxcli

<h1 align="center">enowx</h1> <p align="center"> <b>An open-source AI coding agent for your terminal.</b><br> Specialist agents that plan, build, review and test each other's work, with built-in code search and any model provider. One binary. </p> <p align="center"> <a href="https://github.com/enowdev/enowxcli/releases"><img src="https://img.shields.io/github/v/release/enowdev/enowxcli?color=f0f1f2&label=release" alt="Release"></a> <a href="https://github.com/enowdev/enowxcli/stargazers"><img src="https://img.shields.io/github/stars/enowdev/enowxcli?color=f0f1f2" alt="Stars"></a> <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache--2.0-f0f1f2" alt="License"></a> <img src="https://img.shields.io/badge/macOS%20%C2%B7%20Linux%20%C2%B7%20Windows-f0f1f2" alt="Platforms"> </p> <p align="center"> <a href="https://enowx.ai">Website</a> · <a href="https://enowx.ai/docs">Docs</a> · <a href="https://enowx.ai/changelog">Changelog</a> · <a href="https://discord.gg/enowxlabs">Discord</a> </p> <p align="center"> <img src="docs/demo.gif" alt="enowx: a team of AI agents in your terminal building a landing page and pricing API" width="760"> </p>

curl -fsSL https://enowx.ai/install.sh | sh     # macOS / Linux
irm https://enowx.ai/install.ps1 | iex          # Windows (PowerShell)

Then run enowx.

Why enowx

Most coding agents are one model editing your files, locked to one vendor. enowx is different:

• A team, not one model. It splits a task across specialist agents (plan, build, review, test) that message each other and review each other's work before it reports back.
• Any provider, no lock-in. Bring any OpenAI-compatible endpoint, including local or cheaper models (DeepSeek and others). Give each agent its own model.
• It finds things. Built-in code search (RAG) over your project, cut along the code's syntax, so a function is never split in half.
• It is honest. It reports what it changed and how it checked it, and says plainly when something was not tested.
• One binary. Written in Rust, no runtime to install. Runs on macOS, Linux and Windows, on Intel and ARM.

Early release. It runs and is used daily, but the surface is still moving. Bug reports, ideas and PRs are welcome.

enowx                          # open the terminal interface (default)
enowx auth login deepseek      # store a provider's API key (typed, not echoed)
enowx config set model.default deepseek/deepseek-flash   # pin the model to start on
enowx models list              # the connected providers and their models

Install

Early release. v0.1.0 is the first public build; expect bugs and please report them.

Prebuilt binaries are published on the releases page for macOS, Linux and Windows, on Intel/AMD (x86_64) and ARM (aarch64). The installers are served from enowx.ai and download the binary from those releases. The command is enowx, and it also answers to enx, its earlier name: both run the same binary, so habits and scripts that use enx keep working.

macOS (Apple Silicon and Intel)

curl -fsSL https://enowx.ai/install.sh | sh

The script picks the right build, checks its SHA-256, installs to ~/.local/bin/enowx with enx linked beside it, signs it ad hoc so Gatekeeper lets it run, and adds ~/.local/bin to PATH in your shell's rc file (.zshrc, .bash_profile, fish's config.fish, or .profile). Open a new terminal and run enowx.

Linux (x86_64 and ARM64)

The same script. The Linux builds are static (musl), so they run on any distribution, including Alpine, without extra libraries.

curl -fsSL https://enowx.ai/install.sh | sh

Windows (x64 and ARM64)

In PowerShell:

irm https://enowx.ai/install.ps1 | iex

It installs to %LOCALAPPDATA%\Programs\enowx\enowx.exe, with enx.exe as a copy beside it, and adds that folder to your user PATH; open a new terminal afterwards. The bash tool runs commands with the sh from Git for Windows when it is installed, and with PowerShell otherwise. Windows Terminal renders the interface best.

Options and manual install

Both scripts read ENX_VERSION (a release tag such as v0.1.0; default the latest) and ENX_INSTALL_DIR. ENX_NO_MODIFY_PATH=1 stops install.sh from touching your shell config:

curl -fsSL https://enowx.ai/install.sh | ENX_VERSION=v0.1.0 ENX_INSTALL_DIR=/usr/local/bin sh

To install by hand, download the archive for your platform from the releases page, check it against its .sha256 file, and put enowx (enowx.exe) on your PATH:

| Platform | Archive | |---|---| | macOS, Apple Silicon | enowx-aarch64-apple-darwin.tar.gz | | macOS, Intel | enowx-x86_64-apple-darwin.tar.gz | | Linux, x86_64 | enowx-x86_64-unknown-linux-musl.tar.gz | | Linux, ARM64 | enowx-aarch64-unknown-linux-musl.tar.gz | | Windows, x64 | enowx-x86_64-pc-windows-msvc.zip | | Windows, ARM64 | enowx-aarch64-pc-windows-msvc.zip |

Updating

enowx update            # install the latest release in place of this one
enowx update --check    # only say whether there is one

The interface also looks for a new release when it starts and says so in the status bar; /update installs it. Settings > Updates turns the check off, or has it install updates by itself ([update] in config.toml, or ENX_NO_UPDATE_CHECK=1).

Updating keeps both names on the new version, whichever one you ran. The install scripts also point an older enowx or enx found elsewhere on your PATH (one cargo install put in ~/.cargo/bin, say) at the new one, so no old version is left to start; a program named enx that is not enowx is left alone. Releases before v0.2.3 updated themselves from archives named enx-<target>; releases still publish those, holding both names, so enx update from v0.2.1 and enowx update from v0.2.2 work too.

Uninstalling

curl -fsSL https://enowx.ai/install.sh | ENOWX_UNINSTALL=1 sh

In PowerShell: $env:ENOWX_UNINSTALL = 1; irm https://enowx.ai/install.ps1 | iex. Both remove enowx and enx (and links an install made elsewhere). Your settings, keys and sessions in ~/.enx are kept; delete that folder yourself to remove them too.

From source

With a Rust toolchain:

cargo install --git https://github.com/enowdev/enowxcli enowx-cli

Or build it yourself (see Build). Check the install with enowx --version.

enowxcli opens on a home screen: the wordmark, enow in pixel letters with the mark (an X of lit cells, its centre in orange) as the X, and the composer under it. Until a provider and a model are set, the line under the composer says which one is missing. Open /provider, choose a provider, then enter only its API key. Built-in providers: enxapi, OpenAI, OpenRouter, Groq, and DeepSeek; "Add a custom provider" takes any OpenAI-compatible endpoint. Any number of providers stay connected side by side, each with its own key.

What is inside

| Piece | Notes | |---|---| | Agent loop, tools, sessions | Streaming model calls, paired tool results, JSONL sessions | | Terminal interface | Framed layout, thought/tool cards, paged right sidebar, theme picker | | Roles | Three shipped: Orchestrator, Writer, Researcher | | Specialists | A roster the orchestrator delegates to, including an authorized-assessment security team |

The binary opens the terminal interface, with five selectable palettes.

Roles

| Role | Tools | Purpose | |---|---|---| | Orchestrator | read, write, edit, glob, grep, bash, fetch, todo | Owns a task end to end, then verifies it | | Writer | read, write, edit, glob, grep, todo | Documentation and prose. No shell | | Researcher | read, glob, grep, fetch, todo | Read-only investigation |

Role filtering runs twice: unavailable tools are never advertised to the model, and a call that arrives anyway is refused before dispatch.

Specialists

The orchestrator hands work to a roster of specialists, grouped in the sidebar:

• LEAD: orchestrator (the default: answers quick questions, delegates the rest, never edits files) and maestro, an all-rounder with every tool that both builds and delegates, for a job that mixes doing and handing out. Pick it with /agent maestro.
• BUILD: fe (frontend/interface), motion, canvas (standalone single-file HTML pages and tools), be (backend), db, devops, mobile, systems.
• SECURITY: security, the lead of an authorized security assessment, and its team.
• SUPPORT: research, review, test, docs, perf, librarian, general.

The security assessment team

security is the single security role a user selects. It leads an authorized penetration test: it confirms the scope and written authorization first, then delegates recon and each testing area to a specialist, consolidates the findings, and finds the chains an individual surface cannot see. Its thirteen specialists are reachable only through it (a Lead delegation, so an ordinary request never lands one directly):

| Agent | Tests | |---|---| | sec-recon | Maps the target: hosts, services, versions, stack, input surface | | sec-osint | Passive intelligence, no active touch on the target | | sec-webapp | Web application against the OWASP categories | | sec-api | REST/GraphQL/gRPC: authorization, injection, mass assignment, tokens | | sec-cloud | AWS/Azure/GCP/Kubernetes posture | | sec-internal | Authorized internal hosts, post-foothold | | sec-mobile | Android/iOS applications and their backend | | sec-intercept | Proxy-driven request tampering | | sec-reverse | Binary and firmware analysis | | sec-threat-model | Attack surface and trust boundaries | | sec-ir | Incident triage and response | | sec-vibecoder | Scores how likely a site was AI/boilerplate generated, and reports the gaps it left | | sec-report | The write-up |

Active testing of a domain requires verifiable authorization, not a claim in the chat. authorize_target checks that a connected Cloudflare account controls the domain's DNS zone, which proves control of the domain, and records the domain, its subdomains and the addresses it resolves to as the scope the team may test. A domain the account does not control is refused. Connect the account with enowx auth login cloudflare: it asks which scope (minimal Zone:Read, medium, or full, all read-only), opens the Cloudflare token page with that template pre-filled, verifies the token you paste reads zones, and saves it. For the longest-lived token leave its validity as no expiry (the default, and longer than any end date). The token is read from auth.json or CLOUDFLARE_API_TOKEN.

Every role tests only authorized targets, reads over writes, proves a finding with a benign payload (never a destructive one), and never prints a real secret. Each confirmed issue is recorded with the report_finding tool, which shapes it the same way every time: severity, location, reproduction, impact and fix. The distinct security audit remains as the security skill family, which reads code rather than testing a running target. This is for assessing systems you are authorized to test, such as your own project before release.

Built-in MCP servers

enowx ships four MCP servers of its own, served by the enowx binary (no Node or Python needed). All four are always listed in /mcp, off by default. Turn one on with Tab; a server with no credentials opens its config form instead, which you also reach with c. Changes take effect in the running session, no restart.

| Server | Gives agents | |---|---| | coolify | Applications, servers, databases, services and projects; deploy, start, stop, restart; logs; deployments; env var names | | dokploy | Projects with the