Getting a workspace running takes about two minutes, most of which is waiting. There is nothing to install and no terminal involved.
Get one running
- Sign in at gbrain.io with Google, or ask us for a link.
- Create a workspace and pick a plan.
- Wait for it to show as Running. The first one takes a few minutes, because we are building you a real machine, not a row in a table.
Have the first conversation
Open Chats and ask it something. It will not know much yet, which is the point of the next step.
A good first move is to tell it who you are and what you are working on. That lands in its memory and shapes how it reads everything you give it afterward.
Give it something to read
A workspace is only as useful as what it has seen. Three ways to feed it, roughly in order of how much they pay off:
Paste things into chat. The fastest start. Drop in a document, a thread, a set of notes, and say what it is. It reads and files it.
Connect an account. Google, GitHub or Telegram. Then it can pull from the source instead of waiting for you to paste. See connect your accounts.
Let it work on a schedule. Once material is flowing in, scheduled jobs read and organize it overnight. See skills.
Check what it learned
Open Memory. Everything it has filed is there, as folders and notes you can read.
If something looks wrong, say so in chat. Correcting it in conversation is the intended way to fix its memory, and the fix survives the conversation.
Memory explains how the tree is organized and what a note carries.
Bring in your team
Invite people from your organization’s settings. They get an emailed invitation and sign in with Google or a link, with no password to create.
Everyone in the organization shares the workspace: same threads, same memory, and each question attributed to whoever asked it.
If it stops responding
Check Settings for its status. A workspace that has been idle can take a moment to come back. If it stays stuck, reply to any email from us and we will look.