QUICKSTART
From nothing to a running workspace.
A few steps in the browser, or the same steps from a terminal if you would rather stay there.
1
Sign in and connect a repository account
Sign in to console.smedja.app with GitHub. Signing in identifies you; access to your repositories is a separate account you connect, and can disconnect, in the app.
2
Add an agent
Claude Code, Codex or Gemini CLI, on a credential of yours. smedja asks the provider whether it works before it stores it.
3
Install the CLI (optional)
Everything below is also a button in the app. The CLI is for scripts, CI, and agents that open their own workspaces. It is a single Linux x86-64 binary, checked against a published checksum.
$ curl -fsSL https://console.smedja.app/dl/install.sh | sh$ smedja login
4
Launch a workspace
Pick a template —
smedja template list shows the ones you can use — and say what you want. The message waits for the machine, so there is nothing to wait for yourself.$ smedja workspace create --template ubuntu --name first$ smedja conversation start first \ -m "clone acme/ledger and add pagination to its audit log"
5
Come back to it
The workspace list is where it lives. Attach to the conversation, pause it and keep the disk, or archive it when the work is done.
COMMANDS WORTH KNOWING
smedja workspace listWorkspaces in your current projectsmedja attachFollow a conversation live, in the terminalsmedja workspace pauseGive back the compute, keep the disksmedja search findFind a workspace or a conversation by namesmedja launcher upOffer this computer as a runtimesmedja mcpHand the same operations to your own agentsEvery command documents itself: smedja help, or --help after any of them. Stuck on the first launch? Write to us.