Docs

Enough to get running. The repository carries the rest.

Install

./install.sh
hosia --version

Connect a model

Hosia works before you have an account, a card, or a key.

hosia keys                       # what is connected, and what is free
hosia keys add sk-or-v1-...      # best quality, free, no card
ollama pull llama3.2             # or entirely local, no account

Keys added with hosia keys add are verified against the provider before they are saved, stored at 0600 in ~/.hosia/keys.json, and never placed in your environment. Keys entered through hosia setup, the model wizards or the dashboard go to ~/.hosia/.env instead, which every Hosia process loads into its environment at start.

Use it

hosia                            # interactive
hosia -z "what changed today?"   # one-shot
hosia -z "..." --stream          # stream the reply
hosia desktop                    # the native app

Bots

hosia bot new outbound --role "Draft follow-ups" --model deepseek-chat
hosia bot list
hosia bot run outbound -q "draft a reply"

The Wall

Config may narrow what is permitted, never widen it:

# ~/.hosia/config.yaml
wall:
  deny: [terraform]
  ask: [kubectl]

Any other key under wall: — allow: included — is a hard error: Hosia refuses to run any tool until it is removed, rather than loading the file with the extra key quietly ignored. Approvals are remembered per session and per rule, so approving one install covers the next install in that session and nothing else.

Where things live

~/.hosia/ holds config, keys, bots, sessions and memory. Deleting it removes everything Hosia knows. The program directory can be moved or wiped without touching it.

Version 0.17.0. Questions: support@hosia.com.au