Providers & integrations.
The Aluy CLI never talks to a model provider directly with your data sitting in the open — the model call goes through the broker (or your own provider) at the edge. Here's everything it connects to: the model providers it routes to, and the open projects it builds on.
model providers
Where the model call goes.
OpenRouter
The default gateway — multi-provider routing the broker uses out of the box.
openrouter.ai →
TokenRouter
Alternative routing gateway (OpenAI-compatible), reachable through the broker.
tokenrouter.com →
Anthropic
Claude models — direct provider (BYO key or OAuth).
anthropic.com →
OpenAI
GPT models — direct provider (BYO key).
openai.com →
Google · Gemini
Gemini models, reached through the OpenAI-compatible API.
ai.google.dev →
DeepSeek
DeepSeek models — direct provider, pairs with the Custom tier.
deepseek.com →
projects we integrate
The open projects it builds on.
MCP
Model Context Protocol — the open standard for connecting tools.
modelcontextprotocol.io →
Ollama
Run models locally — optional sidecar.
ollama.com →
mem0
Long-term memory — optional sidecar.
mem0.ai →
headroom
Context-headroom retrieval — optional sidecar.
github.com/headroomlabs-ai →
WezTerm
The recommended terminal for the Aluy CLI.
wezterm.org →
Node.js
The runtime the CLI runs on (Node ≥ 20).
nodejs.org →
Ink
The React-based terminal UI behind the TUI.
github.com/vadimdemedes/ink →
Codex
Compatibility — reads
AGENTS.md project files.
github.com/openai/codex →
Claude Code
Compatibility — reads CLAUDE.md project files.
anthropic.com/claude-code →