The storm has passed. The data is cold. Now you bring it to the oracle and ask: what did I learn, and what should I do with it?
typhon-ask
Typhon sends your hardware profile and benchmark results to an LLM and streams back a personalized recommendation — optimal --ctx-size, suggested launch flags, and an interpretation of what the numbers reveal.
The oracle is reached via environment variables:
| Variable | Default | Description |
|---|---|---|
TYPHON_LLM_URL |
auto-detect | Base URL of the LLM server |
TYPHON_LLM_KEY |
none |
API key — none for local servers |
TYPHON_LLM_MODEL |
auto |
Model name — auto reads from the scan |
By default — with no configuration — typhon-ask speaks to the same local server you just benchmarked. If you ran a trial against llama-server on port 8080, the oracle is already there. No key. No ceremony.
Default — the server you just measured:
typhon-ask
Ollama, specific model:
TYPHON_LLM_URL=http://localhost:11434 TYPHON_LLM_MODEL=llama3 typhon-ask
OpenAI:
TYPHON_LLM_URL=https://api.openai.com/v1 \
TYPHON_LLM_KEY=sk-... \
TYPHON_LLM_MODEL=gpt-4o \
typhon-ask
Any OpenAI-compatible endpoint:
TYPHON_LLM_URL=https://api.your-provider.com/v1 \
TYPHON_LLM_KEY=your-key \
TYPHON_LLM_MODEL=your-model \
typhon-ask
Any server that speaks the OpenAI Chat Completions protocol (POST /v1/chat/completions):
TYPHON_LLM_URL=http://localhost:11434 and TYPHON_LLM_MODEL=<name>TYPHON_LLM_URL=http://localhost:1234TYPHON_LLM_URL=http://localhost:8000The scroll sent to the LLM contains:
typhon-zeus at least onceNo personal information, file paths, or hostnames are included.
typhon-ask is also available through the herald when typhon-api is running:
curl http://localhost:8000/ask