Skip to main content

0.2.4

PTY intelligence reaches stage two: elanous works inside Codex and Claude Code, installs a plugin from an agent's own menu, and passes one mission along several agents.

PTY intelligence, stage two — elanous now works inside the coding agents' own screens. It opens Codex or Claude Code as a real terminal app, answers the folder-trust prompt, types the mission and submits it, watches the screen, and hands the work along a chain — Codex implements, Claude Code reviews, Codex addresses the review, elanous checks the evidence and commits. It can also open an agent's plugin menu, search, check the marketplace name and install a plugin there. You can watch every driven terminal side by side in the web app and take over at any time. See PTY intelligence.

Beta — Elanous is provided as is (Apache-2.0) until the stable release. Get stable release news at elanous.ai. Docs: docs.elanous.ai · Source: ElanvitalAI/elanous

Highlights — stage two (inside the agent)​

  • elanous agent-mission mission --backend codex --chain codex,claude,codex,elanous … — one mission handed along agents; each hand-off carries the diff or summary, and the last step commits only after the evidence check passes.
  • --plugin <plugin>@<marketplace> — installs the plugin from inside the agent's own /plugins menu (search → marketplace name check → install), then sends the mission.
  • Folder-trust prompts (Codex and Claude Code) are answered on a new worktree, including a prompt that appears late.

Highlights — stage one (the command line)​

Stage one — elanous drives terminals itself. It checks the machine first, picks the smallest tool that can do the job (a shell one-liner before a coding agent), installs a missing tool by typing the package-manager line and proving it with a real command, reads an unfamiliar tool's official install page before choosing a safe line, clicks and scrolls in terminal apps that turn on mouse mode, and hands any sudo or sign-in step to you. See PTY intelligence.

  • elanous env profile — what this machine has (OS, shell, package managers, CLIs, sign-in yes/no), read only.

  • elanous agent-mission plan "<mission>" — which rung of the tool ladder a mission starts on, without running anything.

  • elanous research "<query>" — several search engines at once, with the fan-out shown as it happens.

  • elanous agent-mission install-from-docs <tool> --smoke "<cmd>" [--dry-run] — find the official install page, read it, pick a line this machine can run, install and verify. sudo lines and pages without a safe line go to you.

  • elanous pty mouse <ref> <col> <row> — click or scroll in a mouse-enabled terminal app; refused when the app has not turned mouse mode on.

  • Missing CLIs (jq, gh, rg, ffmpeg, node, codex) are installed by typing in the shell and checked with the smallest real job.

  • The web app's Terminal shows each driven terminal side by side with a strip of what elanous just did and why; you can take over with the keyboard or mouse.

  • On a credit policy, the hourly limit alert adds up the credits across your Codex accounts and their combined burn rate, and says when they will run out.