Documentation
Install the app, connect your servers, and run coding agents side by side. These pages follow the app as it is built.
Start
Getting started
Download the installers from GitHub Releases:
Agent presets
How enowX starts each agent (core/agent). Sessions start with permission prompts skipped when Skip permission prompts is on in the New session dialog (the default), and keep that…
Agent accounts
An agent's other accounts are configs of it (configs.md), as its model APIs are: a work and a personal Claude, say. Each is signed in once on a host, then picked per session, with…
Model APIs
A model API of the user's (a company gateway, OpenRouter, LiteLLM, a local server) is a config of an agent for the agents that can take one per session: Claude Code, Codex,…
Servers
Creating a server
Create a server… on the Hosts page makes a server at a cloud provider with the user's own account and API token, then adds it to the hosts and connects, which installs enowX there…
Setting up a server like this device
Set up… on the connected server's card (Hosts page), or Set up this host in the host switcher or the command palette, brings a server to what this device has, so its agents work as…
Environment sync
Sync environment… in the host switcher copies your agents' setup between this device and the connected server, in either direction. Nothing syncs on its own: you pick the items…
Copying a project to another host
A project's menu (right-click it, or its More button) has Copy to host…: the project and the sessions picked go from the connected host to another, from this machine to a server, a…
Your data on every host
Notes, their groups, canvases, settings and the vault's encrypted data are the same on every host: this device, your servers, your other computers. Moving from the Mac to a VPS…
Working with agents
GOD of Agents
GOD of Agents (GOA) is one session the user drives that controls every enowX session on every host: this device, servers, teammates' shared hosts. It doesn't do the coding itself:…
Fan-out
One prompt, given to several agents at once, each on a branch and in a worktree of its own, to compare what they make and keep the best.
Pipelines
A pipeline runs coding agents one after another on one task: plan, then implement, then review, by default, each stage starting from what the one before ended with…
Automations
An automation is a prompt an agent gets on a schedule, each run in a session of its own, kept and run by the host's daemon whether or not an app is connected (core/automation,…
Chat view
The chat button in a session's header shows the session as a conversation instead of a terminal. The terminal keeps running behind it: the message box types into it, and approvals,…
RAG: a project found by meaning
Agents find a project's code, docs, attached notes and memories by meaning, without reading it all. enowX indexes a project itself (core/rag), on the host that has the project,…
Decisions: enowX's judge
The judge is a small, cheap model that enowX asks instead of guessing. It is given one situation and answers with a verdict, how sure it is, and why, in one line. enowX's own code…
Hooks
A hook is something enowX does when something happens in a session: run a command, give the agent context, refuse or change what the agent is about to do, show a notification, or…
Token usage
enowX tracks the tokens every agent uses on each host: input, cache read, cache write, output and reasoning, per session, project, agent, config, model and host, with costs,…
Agent configs
An agent's configs are what its sessions can run with. The official config is the agent as installed: its own sign-in and settings, which enowX never writes to. The others are…
Reviewing and previewing
Review and merge
The Git tab of the side panel shows what the selected session changed and takes it on from there. The panel sits right of the workspace: the panel button in a session's header, or…
Side panel
The panel right of the workspace holds tools about the selected session. The panel button at the right of a session's header, or ⌘⇧D, shows it; the same button at the right of its…
Preview
The Browser tool of the side panel (⌘⇧P, or Preview on a port's card and in the Ports tool) shows what the selected session's dev server serves, in a web view of this device:…
Traffic: see, mock and change HTTP
The side panel's Traffic tool shows the HTTP that what a session runs sends and receives, on its host, live: requests and responses with their headers and bodies, WebSocket,…
Running Android apps
The side panel's Android tool runs the session's app on an Android device and shows what it logs. The device may be on the session's host or on this machine: a project on a server…
Notes, canvas and credentials
Notes
The rail's Notes page keeps pages of notes on the connected host: plans, checklists, what an agent found. Pages nest under one another, as a notebook's, and every app connected to…
Canvas
The rail's Canvas page keeps canvases on the connected host: mockups of UIs in HTML and CSS, wireframes, diagrams (flows, architectures) and free boards. The user and agents design…
Credentials
The Credentials page (More › Credentials) keeps the user's logins to platforms (GitHub and other git hosts, cloud providers, edge and hosting, databases, registries, AI APIs, SSH…
Settings
Settings
The rail's Settings (or the command palette) has these sections, for the connected host where they are a host's.
Features
Settings → Features decides which of enowX's features agents are told of and get MCP tools for. A feature turned off costs agents no tokens; the app itself keeps it. The page shows…
A project's settings
A project can keep settings for enowX in .enowx.toml at its root, committed with it, so everyone working on it gets them (core/project/config.go). Today they say what new worktrees…
Floating control
A round panel over whatever is on screen: six actions around a button and a menu at its front for the sessions of this machine or a server, one shortcut away (ui/floating.go). It…
The tray
enowX keeps an icon in the menu bar (macOS) or the notification area (Windows, Linux) while it runs (ui/tray.go). Closing the window leaves the app there, following its sessions,…
Updates
The app updates itself (ui/updates.go), with MyGo's updater: it downloads the new version's signed archive, or a delta from the running version, checks the signature against the…
Reference
Command line
enowx-app (the desktop app's binary, linked by that name: enowx is another app's) and enowxd (the server daemon's) take the same commands, which talk to the daemon of the host they…
The daemon's lifetime
Each host runs one daemon (enowxd, or enowx daemon on a desktop), which owns its sessions. The app connects to it and can come and go.
Protocol
The app and the daemon (and the command line) talk over one byte stream: the daemon's Unix socket (~/.enowx-app/enowxd.sock) on the same machine, or enowxd bridge over SSH for a…