Hosia

Command line

Enough to get running

These notes are for the command line version, for technical users. Most people want the app, which needs none of this: see Help.

Install

Needs Python 3.11, 3.12 or 3.13. The archive is not on the download page yet: email support@hosia.com.au for it. Then paste this into Terminal:

cd ~ && tar -xzf ~/Downloads/hosia-0.29.18.tar.gz && cd hosia-0.29.18 && bash install.sh

If your browser already unpacked the file, paste this instead: mv ~/Downloads/hosia-0.29.18 ~ && cd ~/hosia-0.29.18 && bash install.sh

If the installer tells you to paste a PATH line, paste it, then close the window and open a new one. After that, hosia --version should answer.

On Windows, the command line version runs inside WSL:

  1. Open PowerShell as administrator, run wsl --install, then restart your PC.
  2. Open Ubuntu from the Start menu and choose a username and password.
  3. Run sudo apt update && sudo apt install -y python3-venv
  4. Paste this, changing YOURNAME to your Windows user name:
cd ~ && tar -xzf /mnt/c/Users/YOURNAME/Downloads/hosia-0.29.18.tar.gz && cd hosia-0.29.18 && bash install.sh

If the installer tells you to paste a PATH line, paste it, then close the window and open a new one. After that, hosia --version should answer.

Connect a model

Hosia works before you have an account, a card, or a key. hosia keys shows what is connected and what is free.

For a free OpenRouter key, sign up at openrouter.ai/keys (no card), run this, and paste the key when it asks:

hosia keys add

Or run a model on your own computer through Ollama, with no account:

ollama pull llama3.2

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. Typing the key at the prompt, rather than after the command, keeps it out of your shell history. 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

Start an interactive session, ask one question and exit, or ask one question with the reply streamed:

hosia
hosia -z "what changed today?"
hosia -z "what changed today?" --stream

Bots

Create a bot (it uses the model you connected), list your bots, and give one a task:

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

The Wall

Config may narrow what is permitted, never widen it. In ~/.hosia/config.yaml:

wall:
  deny: [terraform]
  ask: [kubectl]
  deny_paths: [~/Private]

deny and ask are patterns matched against shell commands. deny_paths lists directories Hosia may not read or write under; each must be absolute or start with ~. Any key other than deny, ask and deny_paths, 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.29.18. Questions: support@hosia.com.au