ai · ⌘K · five features

AI that does the boring part.

No chat sidebar you have to babysit. Five keystrokes. Each one runs in the window you were already working in. Your key, your model, your machine.

0

bytes leaked

5

providers · 1 local

~40ms

first token · local

⌘K

01 · natural language → shell

Say what you want. Get a command that runs.

Type "find all files bigger than 1 GB touched this week" — vev drops the find incantation into your prompt, highlighted, cursor blinking. You read it. Then it runs.

ᚦshell · git · kubectl · Terraform · jq · SQL — all of it
ᚦcite-before-run: never touches anything until you hit return
ᚦfuzzy-ranked across history, hosts, and local files

02 + 03 · diagnose · generate

From "what broke" to "here's the fix."

⌘L

Paste a stack trace. Get a hypothesis.

Select a log region. Hit ⌘L. vev summarizes the failure mode, names the likely root cause, points at the log line that matters. No chat thread. One answer, one scroll.

in →47 × 502 on POST /v1/pay

out →edge-04 · connection-reset mid-stream

iac

Describe infra. Get Terraform.

"A Postgres 15 on RDS, multi-AZ, in eu-west-1, with a dev read-replica." vev writes the .tf, names the resources sensibly, flags the variables to fill. You review. You plan. You apply.

in →postgres 15 · multi-AZ · eu-west-1

out →resource 'aws_db_instance' 'primary'

[1]shellᚦ

ssh edge-03 && uptime

Last login: Sat Apr 19 17:04:11 2026
17:09:22 up 11 days, 22:14,  2 users,  load average: 0.41, 0.38, 0.35

[2]sqlᚦ

select status, count(*) from requests
where ts > now() - interval '5 min'
group by 1

statuscount

20048213

3041102

50247

[3]aiᚦ

@ai summarize the 502s by endpoint and suggest the next check

▸

47 × 502 concentrated on POST /v1/pay (81%). edge-04 returning connection-reset mid-stream. Check: `journalctl -u api --since '5 min ago' | grep -i upstream` on edge-04.

⌘/

04 · one buffer · every cell

Shell, SQL, Python, AI. One notebook.

Mix them. Chain them. The SQL output of cell 2 is a dataframe in cell 3. The AI in cell 4 reads both and suggests the next check. Export as markdown. Commit to the repo.

ᚦshell · SQL · Python · AI cells — one kernel, one file
ᚦoutputs flow downstream automatically
ᚦmarkdown export that still renders on GitHub

05 · byok · no middleman

You bring the key. We bring the wire.

providers

Five to choose from.

Anthropic · OpenAI · Groq · Gemini · any OpenAI-compatible endpoint (Ollama, LM Studio, vLLM).

storage

Keychain, not cloud.

Your API keys live in your OS keychain (macOS / gnome-keyring / Credential Manager). Nowhere else.

wire

Direct to the provider.

Your prompts go from your laptop to api.anthropic.com (or wherever) — never through our servers. We don't have servers for this.

the contract · three lines

ᚦYour prompts go directly to the provider you configured.
ᚦWe log nothing. We route nothing.
ᚦRun mitmproxy on the binary. You'll see exactly two destinations: your provider, and the update server (which you can turn off).

try it

One binary. Every key. Zero cloud.

Install in a second. Paste your key. Start typing.

install →read the docs

AI that doesAI that does the boring part.the boring part.