Start here by intent

You do not have to read this site in order. Find the line closest to what you want, read the pages it names, and come back when you want the next thing.

I want to talk to my agent from my phone

1. Install q15: the four commands the binary will bring, and the Compose path that runs today.
2. Chat for the browser app: passkey enrolment, sessions, attachments. On your phone it installs to the home screen like any other web app, and it can receive a photo or a PDF straight from Android’s share sheet.
3. Telegram if you would rather answer there. It is a second client for the same agent, not a second agent.

I want it to work while I am not looking

1. Jobs for scheduled work: what a job is, what it costs, and how to see whether it ran.
2. Tools for what it can actually do with the rest of its turn.
3. Chat or Telegram for where a job’s report arrives.

I want to run a local model

1. Models for the provider block, the roster, and how the agent picks what answers.
2. Reference for the exact configuration keys.
3. Give it room: the stack itself needs about 2 GB of RAM, and a local model needs whatever that model needs on top.

Local by default is the goal, not the current state

The shipped Compose configuration points at a hosted Ollama endpoint. Running against your own Ollama server is one provider block, and shipping Ollama inside the stack is filed work.

I want my memory in files I own

1. Memory for the layers, the transcript, and the background jobs that maintain them.
2. Workspace for the project tree, media store and what survives a rebuild.
3. Backups for what to copy, in what order, and what not to restore.

I want to give it a shell without giving it my credentials

1. Security for prompt injection, the class of attack the architecture is built around.
2. Credentials for the proxy, the injection rules, and the two credential stores.
3. Architecture for the four services and where the boundaries actually are.
4. Why q15 for what none of this protects.

I want to know what it can do

1. Tools for the surface: files, commands, search, media, subagents.
2. Skills for teaching it procedures it can reuse.
3. Jobs for the work it does with nobody watching.

I want to keep it running

• Updating for the releases, the tag scheme and what does not roll back.
• Backups before you need them.
• Troubleshooting when something is not healthy.
• Reference for every key, path and command in one place.

Every page

Start here — What is q15? · Install q15 · Why q15 · this page

Using q15 — Chat · Telegram · Models · Memory · Workspace · Tools · Skills · Jobs

How it works — Architecture · Security · Credentials

Operating it — Updating · Backups · Troubleshooting · Reference

Nothing in the sidebar is hidden from this list, and nothing here is missing from the sidebar. If a page you were sent to is not one of these, it has been folded into one that is.