Your shell, with a second brain

Ask your terminal.
Keep your flow.

ash brings AI into bash, Fish, and zsh so questions, investigations, and small automations happen where the work already is. Connect remote MCP servers to bring their tools into the same workflow.

macOS · Linux · FreeBSD · Open source

01Ask in place

No context switching. Prompt from the command line you already use.

02Investigate together

Give AI a deliberate allowlist of commands it can use to explore.

03Connect MCP tools

Register remote MCP servers and let ash broker persistent sessions and OAuth.

04Local control

Use locally hosted models, or a cloud provider, while keeping execution under your control.

A calmer way to use AI

The terminal stays
the center of gravity.

01

Opt in to shell integration

ash works with bash, Fish, and zsh. The verified installer asks before adding its managed shell hook; unknown commands become prompts once you enable it. Snooze when you need a break from automatic prompt processing.

02

Easy updates

Update with your package manager, or use ash update for a Release installed under ~/.local/bin. Choose Release, Beta, or Nightly through supported package repositories. No surprise background updates.

03

Stay in control

Tool execution is constrained by explicit allow and deny lists and runs as your user. You decide what ash is allowed to touch. Add your own Python scripts to $XDG_DATA_HOME/ash/tools or native plugins to $XDG_DATA_HOME/ash/plugins.

Start small

Give your shell
some company.

Start with your package manager on macOS or Linux. Our installation guide walks through prerequisites, local Ollama and free cloud tiers, update channels, and safe removal. FreeBSD archive instructions and the alternative script installer are included too.

Open by design

Useful in the moment.
Understandable afterward.

Read the source, inspect the architecture, or see exactly what gets installed.