docs
// Getting Started

Basic and Advanced

A project opens one of two ways in the web app. Basic opens into chat. Advanced opens into the dashboard, where you deploy and run models yourself. Each member picks their own, in each project. Whether Erebine sets up and runs the project's models is a separate project setting, managed models, which the owner turns on.

chosen by
Each member, the first time they open the project
applies to
The member who chose, in that project
changed in
The account menu
managed models
A project setting the owner turns on or off in Settings
surface
The web app and Erebine Desktop. The iOS app has its own Basic and Advanced, kept on the device.

Two Experiences

Both experiences run on the same project, the same chats, and the same billing. They differ in where the web app opens and in what it shows, and two members of one project can use different ones.

AspectBasicAdvanced
Opens intoChatThe dashboard
ModelsThe project's models; with managed models on, Erebine sets them up and keeps them currentYou deploy endpoints and pick models
New workspacesEvery chat feature on, except zero data retentionCopy the project's default workspace
ShowsChat with a sidebar, workspaces, scheduled tasks, templates, knowledge, artifacts, usage, billing, team, settingsEverything basic shows, plus endpoints, Erebine Inference Microservices (EIMs), Erebine Execution Managers (EEMs), models, API keys, MCP setup, and operations
Model choice in chatAuto, through the semantic router, or one of the project's models by name, per chatAutomatic, or picked per chat

Basic

Basic is chat first. The project opens into your most recent chat. When you choose basic and have no chat yet, Erebine starts one and opens it, once the project has a model to answer it; otherwise you open into Workspaces.

What basic shows

  • Chat, with a sidebar. Chat carries the same top bar as every other page, with the project's navigation and the account menu. The sidebar holds the chats: search, a new chat, a chat started from a template, and the project's workspaces with their chats.
  • Scheduled. Research topics and prompts that run on a schedule, each run a turn in the task's own chat. See Scheduled Tasks.
  • Templates. Create and edit chat templates with a title and a system prompt.
  • Knowledge and artifacts. The workspace's memories, decisions, and milestones, and the artifacts its chats produced.
  • Usage. What the project spent, and on what.
  • Billing and settings. For the project owner.
  • Team. The project's members, and invitations for new ones.

The chat sidebar

  • From a template opens the same template catalog as the Workspaces page. The chat it starts lands in the workspace on screen.
  • The pen at the end of a workspace's row starts a new chat in that workspace. It shows on the open workspace and on a row you point at or tab to; on a touch screen it shows on every row.
  • The plus beside the Workspaces label creates a workspace, in the same dialog the Workspaces page uses.
  • The magnifier beside it filters the workspace list by name. Escape clears the filter and shows every workspace again.
  • The toggle sits at the top of the sidebar. On a wide screen it collapses the sidebar to a rail of icons, and the browser remembers the choice. On a phone or a narrow window there is one menu: the menu button at the top left opens your chats first, then the pages.
  • The edge of the open sidebar resizes it on a wide screen. Drag it, or focus it and use the arrow keys; Home and End jump to the narrowest and widest. A double click restores the default width, and the browser remembers the choice.

What basic hides

Endpoints, EIMs, EEMs, models, API keys, MCP client setup, the dashboard, and operations. Chat keeps a simpler model choice, the reasoning effort, and the tool options. Settings drops custom domains, approval notifications, and inference tracing. A link or bookmark to a hidden page opens chat instead.

Models in basic

By default chat is on Auto: it picks a model for each message through the semantic router, from the models the project runs. To choose one yourself, open Options from the chat Tools menu (Alt+O) and pick a model by name, or go back to Auto. The choice is kept per chat. Erebine Desktop and the iOS app offer the same choice in their Basic composers. The same panel sets the reasoning effort. With managed models on, Erebine sets those models up for you.

Until the project has a model to answer, chat says so and opens on its own when one serves. With managed models on it reads Setting up your workspace. With them off it says that the project owner can turn on managed models in Settings.

Advanced

Advanced is the full console. The project opens into the dashboard, where you deploy endpoints, EIMs and EEMs, pick models and service tiers, issue API keys, and connect MCP clients. Chat, templates, knowledge, usage, billing, and team are all there too.

Start from the Quickstart to create an endpoint and send a first request, or from MCP Integration to connect an editor.

Choosing

Each member chooses for themselves. The first time you open a project, Erebine asks how it should open for you, with nothing preselected. A project you join or create later asks the same way.

Your choice applies to you alone, in that project. Another member of the same project can choose the other experience, and nothing you choose changes what they see.

Managed Models

Managed models is a project setting. With it on, Erebine sets up a model for the project from each model the platform serves, keeps the set current as the platform adds models, and turns on the default workspace's chat features. Only the project owner turns it on or off, in Settings.

  • An owner who picks basic the first time gets managed models turned on, with no extra question.
  • An owner who switches from advanced to basic is offered managed models in the switch, checked by default. When they are already on, the switch says so.
  • An owner who picks or switches to advanced leaves managed models as they are.
  • A member never sees the option, and a member's choice never sets anything up.

Turning managed models off stops Erebine from adding models. The models it already set up keep running; manage or delete them from Endpoints in advanced.

On the default workspace, managed models turns on tools, speech input and output, spoken replies, and automatic model routing, the first time it is turned on. A setting someone in the project already changed keeps its value. Zero data retention is never touched.

New Workspaces

A workspace you create in basic comes with every chat feature on: tools, speech input and output, spoken replies, images, humanized replies, project intelligence, research, and automatic model routing. Zero data retention stays off, and so does command execution from MCP clients. Budgets and model choices still come from the project's default workspace.

A workspace created in advanced, or from the desktop or iOS app, copies the settings of the project's default workspace, as it always has.

Switching

Any member switches their own experience from the account menu in the top bar, chat included: Switch to basic or Switch to advanced. The switch asks for confirmation, then takes effect for you alone.

After you confirm, the switch shows each step as it completes: your choice saved, for an owner who sets up models the models and chat features, the full console for advanced, and last the page it opens, chat for basic and the dashboard for advanced. Escape and Cancel stay off while the choice saves. A first choice runs the same steps.

Switching to basic

An owner whose project has managed models off is offered them, checked by default. Endpoints an owner deployed are hidden in basic, not stopped: they keep running and keep billing, and the confirmation says how many there are. Switching back to advanced shows them again, and you stop or delete them there.

While managed models are on, Erebine keeps the models it set up in place. One deleted from the desktop or iOS app is set up again.

Switching to advanced

Endpoints, EIMs, EEMs, models, API keys, and MCP client setup come back. Managed models stay as they are; the models Erebine set up show in Endpoints with the rest.

Switching changes what the web app shows. It never deletes a chat, a workspace, a template, or an endpoint.

Desktop and iOS

Erebine Desktop follows the same choice. In basic its sidebar lists Chat, Code, Scheduled and Project; in advanced, every destination. Scheduled is hidden on a deployment that does not run scheduled tasks. Switching in the desktop app, from the bottom of its sidebar or from Settings, switches the web app too. An owner's first choice of basic in the desktop app turns managed models on, as on the web; the desktop switch does not offer managed models, so an owner who switches to basic there leaves them as they are. As on the web, an owner with endpoints they deployed is told that they keep running and billing in basic. See Erebine Desktop Code.

The iOS app has its own Basic and Advanced, chosen in the app and kept on the device; it does not follow or change the choice you make here. Basic lists Chats, Needs you and Scheduled; Advanced adds the Console. See Erebine for iOS. A workspace created in either app copies the default workspace.

Billing

The experience changes what the web app shows, not how usage bills. The models managed models sets up are shared endpoints, billed in credits per token for the requests they serve. Endpoints you deployed yourself bill as they always have, whether basic hides them or not. Usage and Billing has the billing models.