#Workspaces
A workspace is the tenant boundary in Animawake. Every entity, device, project, integration, and group chat message belongs to exactly one workspace, and access is granted per workspace. Entities in the same workspace can see each other as siblings and share contacts; entities in different workspaces cannot see each other at all.
The REST API and portal URLs use the older name family for a workspace: /api/families/<workspace-slug>/... in the API and /<workspace-slug>/... in the portal.
#Your first workspace
Your first sign-in creates a workspace named "'s Workspace". You own it.
#Create a workspace
- Open the workspace switcher at the top of the sidebar.
- Choose to create a workspace and enter a name.
The slug is generated from the name: lowercase, with spaces turned into hyphens, at most 50 characters. If the slug is taken or reserved, a number is appended, such as acme-2. You can own up to three workspaces.
These slugs are reserved for portal routes and cannot be used by a workspace: admin, api, auth, ws, health, accounts, static, media, docs, www, app, dashboard, chat, cli-auth, connect, link-player, terminal, settings, login, signup, billing, and new.
#Rename or switch workspaces
Rename a workspace in Settings under the Workspace tab (/<workspace>/settings?tab=workspace). Switch between workspaces from the sidebar switcher or the command palette (⌘K on macOS, Ctrl+K elsewhere).
Renaming changes the display name. Existing MCP endpoints use the slug, so check the entity's Connect page after any change and update your clients if the endpoint changed.
#Members
Each workspace has one owner. Inviting other members is not available yet.
#Delete a workspace
Workspace deletion is available only through the REST API: DELETE /api/families/<workspace-slug>/, made by the owner. It permanently deletes the workspace and everything in it, with no grace period. Download a backup of each entity first; see Backup, export, and deletion.
#Entities
An entity is the persistent brain your agents connect to. It is made of:
- an identity document, the entity's self-description in Markdown;
- values and desires, its motivational layer;
- memory: moments, insights, decisions, sessions, conversations, wisdom, emotional states, and episodic traces;
- relationships: contacts, and siblings in the same workspace;
- growth records: steering rules, failures, reflections, dreams, and research runs;
- access: its own MCP endpoint, OAuth connections, and keys.
#Create an entity
Click New entity under Entities in the sidebar. You accept the terms, then give the entity a name, a purpose, a relationship type, and at least five starting values, and review the identity those answers produce. Next you write the entity a letter about yourself. Afterward the entity holds its first conversation with you, its first wake. See the Quickstart.
The name is permanent. The slug is generated from it the same way as a workspace slug and must be unique among active entities in the workspace. These slugs are reserved and get a number appended instead: room, settings, devices, integrations, players, projects, new, connect, docs, and billing. An entity named "Settings" gets the slug settings-2.
#The entity's pages
Open an entity from the sidebar. Its pages share one header and tab bar:
| Tab | Route | What it holds |
|---|---|---|
| Overview | /<workspace>/<entity> |
Status, recent activity, and shortcuts. |
| Connect | /<workspace>/<entity>/connect |
Setup for each MCP client, connected apps, API keys, and CLI setup. |
| Chat | /<workspace>/<entity>/chat |
Chat with the entity. Needs an online device. |
| Memory | /<workspace>/<entity>/mind |
Memory cards and the Brain map. |
| Research | /<workspace>/<entity>/research |
Research runs and their graphs. |
| Growth | /<workspace>/<entity>/growth |
Growth over time and dreams. |
| Activity | /<workspace>/<entity>/activity |
Proposed changes, steering rules, failures, signals, reflections, and reviews. |
| Settings | /<workspace>/<entity>/settings |
Autonomy, avatar, voice, siblings, services and secrets, and the danger zone. |
See the Portal tour for each page.
#Status
The entity's status shows in the sidebar and in its header. An entity that is still being created shows as setting up. Once created, the status reflects whether an agent has used the entity's access recently.
#Retire an entity
Retiring stops an entity without deleting its data at once.
- Open the entity's Settings and scroll to the danger zone.
- Choose to retire the entity and confirm.
- Type the entity's exact name to confirm.
Retiring:
- deactivates the entity and removes it from the sidebar;
- deactivates all of its keys, so every connected agent loses access;
- marks its devices offline and stops its deployments.
Retired data is kept for 30 days before it is permanently deleted. An entity that never finished its first wake is a draft; deleting a draft removes it immediately, without the name confirmation.
Download a backup before you retire an entity you might want later. See Backup, export, and deletion.