AgentX is a terminal chat agent built on the OpenAI Responses API over WebSocket transport.
For most users, the simplest path is: install it globally, run agentx-setup once, then start agentx.
If you installed the package globally, use:
agentxIf you are working from the repository root, use:
node agentx.mjsagentx-setupUse that to save your OpenAI API key and runtime settings in ~/.agentx.
agentx --helporagentx -hshows quick helpagentx --versionoragentx -vprints the package versionagentx --debugprints raw websocket logs and suppresses live status linesagentx --confirmenables confirmation prompts; approval is the defaultagentx --check-mcp(or-K) validates MCP configuration without contacting APIsagentx --cwd PATH(or-C PATH) runs the session from a specific working directory; relative paths resolve from the launch directoryagentx --quietis useful for one-shot subagents: it keeps reasoning and the final response while suppressing usage, timers, and tool/status output- Use
--no-reasoningwith--quietto suppress reasoning too; output flags only affect rendering and do not disable reasoning in the API request agentx --no-mcp(or-m) omits MCP tools from the request;--no-mcp-output(or-M) keeps MCP enabled but hides MCP call output- Short output flags can be stacked, for example
agentx -qur "run the tests" agentx "message"runs one request, performs tool calls, prints the response and usage summary, then exits- MCP calls and streamed arguments are shown in cyan when configured
Use a quoted argument when you want a single non-interactive request:
agentx "find the failing tests and explain them"One-shot requests branch from the latest successful checkpoint. Their pending tool state is isolated from .agentx_responseid, allowing concurrent subtasks in the same directory.
Set your API key in the shell environment, or let agentx-setup write it into ~/.agentx for you:
export agentx_api_key="your-key-here"
# or: export AGENTX_API_KEY="your-key-here"AgentX prefers agentx_api_key and falls back to AGENTX_API_KEY.
The launchers load ~/.agentx when present. Startup also displays the active model and runtime settings.
To enable MCP tools, place an .agentx.mcp.json file in your home directory. Copy .agentx.mcp.json.example as a starting point and update its server URL and authorization. AgentX loads ~/.agentx.mcp.json automatically; set "enabled": false on individual entries to keep them configured but disabled. A missing file is allowed, while invalid JSON prevents the prompt template from loading. See the MCP smoke tests for live verification commands.
- Start AgentX.
- Type a normal message and press Enter.
- AgentX sends that message to OpenAI.
- The response streams into the terminal as it is generated.
- The prompt shows your user, short hostname, current working directory, and a
#marker. - AgentX waits for your first message before contacting OpenAI.
- Tool calls may stream command arguments and shell summaries live.
- Interactive
!commands have no automatic timeout; Ctrl-C stops the local command and returns to AgentX. Ctrl-T interrupts model-requestedshell_calltools and tells the agent to stop, avoid retries, and report current status. - If
.agentx_responseidexists, the session resumes automatically. If it contains pending tool calls, AgentX asks how you want to continue. Recognized closed/lifetime WebSocket failures are retried with exponential backoff for up to 10 seconds before recovery.
Install or update the latest release at any time with:
npm -g install @eliware/agentx-cli@latestSee AGENTS.md behavior for how project instructions are discovered and loaded. Path handling and shell launchers support Linux, macOS, and Windows.
npm -g uninstall @eliware/agentx-cli
rm -f $HOME/.agentx*