Take the helm in 20 minutes

Your cockpit is ready. This guide takes you from first login to your first agent session working on your project, with your memory. Version française.

1.Log in

Your activation email contains two things: your cockpit URL (you.sokkan.ch) and your login token. Open the URL, paste the token — that's it. Treat the token like a password; you can invite your team and manage roles (viewer / dev / admin) from the cockpit.

2.The grand tour (2 minutes)

• Sessions — your live agent sessions, in a multi-pane grid. Permission requests show up as buttons: nothing irreversible happens without your click.
• Board — the kanban. A card describes a task; ▶ spawn turns it into a session that starts with the context already loaded.
• Memory — your project's accumulated knowledge: notes, links, and a search playground that shows exactly what a session would recall.
• Costs — consumption per day and per session. You know what each task costs.
• Audit — the log of everything that happened: who spawned, moved, deleted what.
• My fleet — your machines: order a worker or a managed PostgreSQL in two clicks; they appear inside your private network.

3.Bring your project

The simplest way: ask your first session. Create a session and give it access:

Clone [email protected]:my-org/my-project.git into the workspace,
then give me a lay of the land: stack, structure, how it runs.

The session will ask permission before running commands (that's the point: you approve), clone the project into its workspace, and hand you a first analysis. For a private repo, add a read-only deploy key — the session will walk you through it if you ask.

4.Seed the memory (the move that changes everything)

SOKKAN becomes valuable once your project memory exists. One note = one markdown file, one fact, with a description: line in the frontmatter:

---
description: The API listens on port 8080 internally; healthcheck = /healthz
---
Decided after the March nginx incident. Every new service follows this
convention.

Your sessions write these notes naturally as they work; the index refreshes in ~2 minutes. To bootstrap, ask your first session:

Write this project's first 5 memory notes: the stack, naming conventions,
how to run the tests, how we deploy, and the known traps you can see
in the code.

💡 The golden rule: one note = one fact. Big notes rot, atomic notes compose. The description: line is the search hook — write it like a commit subject.

5.The daily ritual

• An idea, a bug, a task → a card on the board.
• ▶ spawn → the session starts, searches the memory, reads the code, proposes a plan.
• You approve the plan → it executes. Every sensitive action waits for your click.
• The session writes down what it learned → the next one starts smarter.

That's the helm, not the autopilot: you steer, the agents row.

6.Inference: your key or our credits

In Profile → Model, choose: your own Anthropic key (BYOK — your prompts go straight to Anthropic), or prepaid managed inference (Qwen3 Coder models served from Frankfurt, metered per token, content never retained). You can change your mind at any time.

7.Growing: the fleet

Need a database, a build worker, a staging environment? My fleet → pick from the catalogue → the machine appears in your private network, reachable by name (db.fleet, staging.fleet) from all your sessions. Prorated billing, one-click removal, your data stays in Switzerland.

8.Need help?

Write to [email protected] — you get the founder, not a bot. During your trial, every question is welcome: it's also how we improve the product.