ahel
Start free

Command line

Connect your terminal.

Install the ahel command, sign in once in your browser, and your terminal and your coding agent use your gateway.

Runs on macOS and Linux with Node 22 or newer; Windows through WSL. Same account, same rules as the connector at mcp.ahel.ai.

Install

Copy one line.

This installs the ahel command in your home folder, opens your browser once to sign in, and adds the Ahel skill to the project you run it in.

  1. Choose your coding agent

    The line below adds the Ahel skill where the agent you pick reads it.

  2. Install and sign in

    It installs the ahel command in your home folder, opens your browser once so you can sign in, and adds the Ahel skill to the project you run it in. Finish the sign-in in the browser and the command continues to a live check with ~/.ahel/bin/ahel status --json. If you have several workspaces, it prints the commands to select one.

    curl -fsSL https://install.ahel.ai/cli | sh -s -- --login --init claude-code --yes

  • Downloads from ahel.ai/cli and verifies the checksum before anything is installed.
  • Installs under your home folder. No sudo, no shell files edited.
  • The same account, permissions and spending controls as the connector.
Other ways to install

Install only. Nothing signs in and nothing is written to your project:

curl -fsSL https://install.ahel.ai/cli | sh

Then, when you are ready

~/.ahel/bin/ahel auth login

~/.ahel/bin/ahel init --client claude-code --dry-run

~/.ahel/bin/ahel init --client claude-code --yes

The preview line shows what would be written and writes nothing; the apply line adds the skill for Claude Code.

The executable is ~/.ahel/bin/ahel. To type ahel on its own, add this line to your shell profile yourself: export PATH="$HOME/.ahel/bin:$PATH"

Installation details and questions

Then

How setup works.

Install, sign in, and add the skill. A live check confirms the result.

  1. Sign in in your browser

    The script fetches the command from ahel.ai/cli, checks its checksum, and opens the normal consent screen in your browser. One sign-in covers every workspace you belong to. If you have more than one, setup prints the commands to select a workspace before the final check can pass. Your coding agent can ask you which workspace to use.

  2. Add the skill to your project

    The command writes the Ahel skill where your agent reads it: Claude Code from .claude/skills/ahel/, Codex from.agents/skills/ahel/. Files you already have are left alone; a file you edited yourself stops the run and is named, never overwritten.

  3. Check with ~/.ahel/bin/ahel status

    It reports the workspace the call goes to and the live readiness of your gateway: what is on, what needs setup, and the accounts connected. --json is the shape your agent reads, and the setup line ends with it.

  4. Revoke under Settings, Terminal sign-ins

    Each terminal sign-in is listed in the app under the name it reported, with when it signed in and was last refreshed. Taking the install-only line instead? Run the sign-in line, then the preview and apply lines under Other ways to install in the card above.

The boundary

What it deliberately does not do

The same account permissions and spending controls as the connector apply to every call from the terminal.

Your terminal can

  • Use your connected apps, skills and Knowledge from the command line, yourself or through your coding agent.
  • Preview a call before running it: --dry-run shows the redacted request and makes no execution call.
  • Running an app tool or action requires --yes. Without it the command refuses to run. Use --dry-run to preview.

It never can

  • See or store an app credential. Keys stay sealed on the gateway and are attached server-side, never on your machine.
  • Call your gateway without signing in. That sign-in can be revoked in Settings.
  • Run an app tool or action without --yes. A preview may read action details, but does not run the action.

Questions

Everything else.

Do I need Node?

Yes. The installer needs Node 22 or newer and npm on your PATH, and checks before it downloads anything. If Node is missing or too old it prints the one instruction to fix that and stops; it never installs Node for you.

Does it run on Windows?

Through WSL, yes: run the same line inside your WSL terminal. There is no native Windows installer yet.

Where does it install, and how do I remove it?

Under your home folder, in ~/.ahel, with the executable at ~/.ahel/bin/ahel. Nothing goes into system paths. To remove it, delete the ~/.ahel folder; to remove a skill from a project, delete its .claude/skills/ahel or .agents/skills/ahel folder.

What happens if I run the line again?

The installer checks the installed copy and reuses it if it is verified. When a newer version is published, the same line upgrades it; a failed upgrade leaves the working copy in place. The full setup line also signs in again and checks the project skill.

How do I revoke a terminal sign-in?

Under Settings, Terminal sign-ins, in the app. Each sign-in is listed under the name it reported, with when it signed in and was last refreshed; revoking one ends that sign-in, and the terminal has to sign in again.

Does the installer change my shell or my permissions?

No. It never asks for sudo and never edits a shell profile. It prints the PATH line for you to add yourself if you want to type ahel without the full path; until then, ~/.ahel/bin/ahel works as is.

Add the missing link.

One line, and your terminal reads the same gateway as every agent you use.

Install the commandOpen Your AI