> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gobare.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Build without writing code

> You want something built for you, not an API — start in the Console instead

**Everything else on this site is for people calling an API.** If you would
rather describe what you want and watch it being built, you do not need any of
it. The same agent works in the Console at
[app.gobare.dev](https://app.gobare.dev): you type what you want, it builds it on
a real computer, and you open the result in your browser.

## Getting started

1. **Sign up** at [app.gobare.dev](https://app.gobare.dev).
2. **Connect a model.** Gobare runs on a model account of your own. Get an API
   key from one of Anthropic, OpenAI, xAI, OpenRouter, MiniMax, DeepSeek, Qwen,
   Kimi or GLM, and paste it in when the Console asks. What you spend on the
   model is between you and that provider.
3. **Choose "Try the agent"** on the Console home and describe one concrete
   thing. "A page that lists this week's site visits from a spreadsheet I
   upload" works better than "a system for my company": the agent does best with
   something it can finish and show you.
4. **Open the preview** when it is done, and ask for changes in plain words. It
   is the same computer every time, so the next request starts from what is
   already there.

You can do all of this from a phone, and come back to the same project later on
another device.

## Keeping it private

What you build is **not public unless you publish it.** While you work, the
preview is visible to you, signed in; anyone else who opens that address sees
the Gobare Console, not your project.

Publishing gives the project an address anyone with the link can open. You can
take it down again at any time.

Two limits matter if you are thinking of a tool for your business, and you
should know them before you start:

* **A published project cannot sign people in yet.** Its address does not carry
  cookies, so a login page will not keep anyone logged in.
* **There are no staff accounts or roles.** You cannot give an employee access
  to one project and not another.

So today Gobare suits tools you use yourself, and public pages you want to hand
out. A system your staff log into is not something it can host yet.

## If you do write code

The same agent is an API. Start at the [quickstart](/quickstart), and read
[How Gobare is different](/why-gobare) for what a session gives you that other
agent APIs do not.