You’re installed, signed in, chatting with Prime. Here’s the order most operators find useful for the next hour.

The quick wins

1. Install the local CA

sudo qorven tls install-ca on every laptop that’ll visit this Qorven install. Browser warnings disappear; the green lock stays. One-time per machine.

2. Connect Telegram

5 minutes end-to-end: create a bot with @BotFather, paste the token into Settings → Channels, and message your Qor from your phone. It lands in the same canonical chat as the web UI.

3. Try the 🧠 Memory button

Click the Memory button above the composer. Search anything you’ve told this Qor. Every archived compaction is indexed.

4. Share your screen

Toolbar → Share screen. Your Qor gets a frame every second. Useful for “what am I looking at?” and “how do I fix this error?”.

Deeper explorations

5. Spawn a specialist Qor

“Create a Qor called ‘Inbox Triage’ that reads my mail, flags VIP senders, and drafts responses for review.” Prime creates it on the fly.

6. Give it a tool budget

Each Qor has an allowlist of tools. Default is “everything”; for a focused Qor, restrict it to just read_document, web_fetch, and send_email.

7. Set up a cron Qor

“Every morning at 7am, summarise my calendar + unread mail and send it to Telegram.” Qorven’s cron is Qor-based — the runs feed into memory, not a cold log.

8. Open a Room

Drop 3 Qors into a shared room. Assign roles. Watch them iterate. Rooms are where multi-agent work actually happens.

9. Add a connector

Google Drive, Gmail, Notion, GitHub, Linear, Jira — 52 OAuth integrations. Register your OAuth app once in Settings → Connectors, every tenant on this install uses it.

10. Back up the encryption key

cat /etc/qorven/config.toml | grep encryption_key. Put that value in your password manager. This is the only copy. If it goes, every encrypted secret in Postgres is unrecoverable.

Architecture reading order

When you have 20 minutes, read these in order:
1

Architecture overview

Read → — the full request path, who holds what state.
2

One Qor, one chat

Read → — why there’s no “new session” button, how channels merge.
3

Delegation

Read → — how Prime picks specialists, how specialists can delegate further.
4

Memory system

Read → — compaction, pgvector, knowledge graph, dreaming.
5

Security model

Read → — tenant isolation, encryption key, prompt-injection defense.

If something breaks

Start with qorven doctor

One command, checks everything: DB connection, TLS cert, config validity, provider keys, channel webhooks.

Check logs

journalctl -u qorven -f on Linux, /var/log/qorven/*.log always, docker compose logs -f in Docker.