Skip to content

Configuration

The API listens on the instance only. You reach it through a tunnel, and every request carries the per-instance token.

Where things live

Item What it is
127.0.0.1:7777 AgentOS API. Every route requires a Bearer token.
/home/ubuntu/.config/sushi-agno/settings.json API token and provider key. Mode 0600.
/var/lib/agno/sessions.db SQLite sessions.
/var/lib/agno/workspace/ Task inputs, result.json, and readbacks.
/opt/agno/ Application code and dependencies. Not writable by the service.
sushi-agno Health, configure, demo, and session commands. The helper keeps the token off the command line.

A task directory

Create a directory under /var/lib/agno/workspace/ as ubuntu. The task name is letters, numbers, and hyphens, at most 80 characters. input.csv has exactly one column of integers. Ask the agent to use calculate_csv with that task name as run_id. Use a new directory for another calculation.

POST /agents/csv-analyst/runs accepts form fields message, session_id, user_id, and stream=false. Read a session with GET /sessions/SESSION_ID/runs?type=agent&db_id=sushi-agno-sqlite.

For your own client, read api_token from the settings file and set Authorization: Bearer in memory. Do not print the file, the header, or the token.

From your workstation

Keep the listener on loopback. The instance login banner prints a Session Manager port-forward command. For SSH, add -N -L 7777:127.0.0.1:7777 to the connection command from the EC2 console. Point the client at http://127.0.0.1:7777 through that tunnel. No public application port is required.

Provider file

sushi-agno configure refuses to be the place you paste a key into a recorded session. Run it in an unrecorded terminal. Restart sushi-agno after a change. Do not put the provider key in user data, shell arguments, or support mail.

Last updated November 11, 2026 · Suggest an improvement