Quickstart
From nothing to your first agent answer — get an instance, sign in, and send your first message. Five minutes on a ready instance, fifteen if you stand one up on your own machine.
3 min read
This is the shortest path to a working chat with an agent: get an instance, sign in, send a message, watch the reply stream. It takes about five minutes on a ready instance and fifteen if you stand one up on your own machine, and it ends with the screen below — a real answer from an agent over your workspace.
Prefer the tour as a video? Episode 1 walks the same ground in three minutes — captions included.
Get an instance
The two editions run the same product — pick by who should operate the stack.
With Docker running, three commands stand up the whole stack on your machine:
curl -fsSL https://raw.githubusercontent.com/tale-project/tale/main/scripts/install-cli.sh | bash
tale init my-project && cd my-project
tale devThe first run pulls images — expect five to ten minutes. When the browser opens, sign up: the first account claims the Owner role and creates your organization. The self-hosted quickstart covers every step in depth, including Windows and troubleshooting.
Send your first message
Open a new chat
Click New chat in the sidebar. The composer at the bottom of the screen is where everything starts: the message field, and one picker naming the model the reply will come from. A model already showing on the picker means you are ready to send — the assistant itself is built in, so there is nothing else to choose.
Ask something real
Pick any chat model from the picker — every reply comes from the model you named, so nothing is chosen for you behind the scenes. Type a question and send it. The reply streams in token by token; when the agent reasons before answering, a collapsible thinking line appears above the reply.
Where you are now
You have a running instance and an agent that answers. The next fifteen minutes depend on your role: the member journey covers documents and projects, the editor journey publishes your first specialist agent, the admin journey sets up the team and providers, and the developer journey gets you an API key and your first request.