docs/GETTING-STARTED.md and docs/guides/getting-started.md covered the same ground; keep one guide in docs/guides that follows the current setup flow, the two model paths, memory on mem0 and the real keyboard shortcuts. Drop the product tiers, the signed-Windows-only install, the .mind files, install.sh and the external coding-agent sign-in. The workspaces guide loses team workspaces, the .mind files, FTS5 search and the knowledge graph, and describes virtual and local storage, the shipped personas and what deleting a workspace removes.
75 lines
3.4 KiB
Markdown
75 lines
3.4 KiB
Markdown
# Workspaces
|
|
|
|
A workspace holds one project or area of work: its chats, its files, its memory and the persona
|
|
the agent uses there. Your personal memory is shared by all workspaces; everything else stays in
|
|
its workspace.
|
|
|
|
## Creating a workspace
|
|
|
|
Create a workspace from **Home** or the workspace list. You choose:
|
|
|
|
| Field | Description |
|
|
|---|---|
|
|
| Name | "What project or area is this for?", for example "Acme Client" or "Q3 Launch" |
|
|
| Template | Optional. A starting setup with a matching persona, such as Research Hub or Engineering |
|
|
| Group | A category for grouping workspaces in the list, such as Work or Personal |
|
|
| Storage type | **Virtual**: Waggle keeps the workspace's files in its data directory. **Local**: the workspace uses a folder on your disk |
|
|
| Agent | Optional. The persona to use in this workspace |
|
|
|
|
The first setup creates your first workspace from the template you pick.
|
|
|
|
## Storage: virtual or a folder on disk
|
|
|
|
- **Virtual** workspaces keep their files in `<data>/workspaces/<id>/files`.
|
|
- **Local** workspaces point at a folder you choose. The agent's file tools (read, write, edit,
|
|
search) work in that folder, and its git tools work on the repository there. Writes go
|
|
through the approval rules in Settings → Permissions. Shell commands run with your user's
|
|
rights and are not sandboxed; see the [threat model](../../THREAT_MODEL.md).
|
|
|
|
## Chats (sessions)
|
|
|
|
Each conversation in a workspace is a session. Sessions are stored as JSON Lines files in
|
|
`<data>/workspaces/<id>/sessions/`.
|
|
|
|
- Start a new chat from the workspace, or just type: a session is created on the first message.
|
|
- A session is titled from its first message; you can rename it.
|
|
- Search finds messages across the sessions of the current workspace.
|
|
- A session can be exported as Markdown.
|
|
|
|
## Personas
|
|
|
|
A persona sets how the agent works in a workspace: its instructions, the tools it prefers, the
|
|
commands it suggests and, for some, a default workflow. Waggle ships with 22 personas: General
|
|
Purpose, Researcher, Writer, Analyst, Coder, Planner, Verifier, Coordinator, Project Manager,
|
|
Senior PM, Executive Assistant, Sales Rep, Marketer, Customer Support, Operations Manager, Data
|
|
Engineer, HR Manager, Recruiter, Legal Counsel, Business Finance, Strategy Consultant and
|
|
Creative Director.
|
|
|
|
Switch the persona with `Ctrl+Shift+P` (`Cmd+Shift+P` on macOS). Some personas are read-only:
|
|
they cannot use tools that write. You can also create your own agents in **Agents** (at the
|
|
Everything interface level).
|
|
|
|
## Workspace memory
|
|
|
|
Each workspace has its own memory, separate from your personal memory:
|
|
|
|
- **Workspace memory** holds project context: decisions, findings, notes.
|
|
- **Personal memory** holds what is true across workspaces: your preferences, your role,
|
|
recurring facts.
|
|
|
|
In a workspace the agent reads both. It does not read other workspaces' memory unless you ask
|
|
it to search all workspaces (`/search-all <query>`). See [memory.md](../memory.md).
|
|
|
|
Open **Memory** to browse, search, correct, confirm or forget memories.
|
|
|
|
## Switching workspaces
|
|
|
|
- Pick a workspace from **Home** or the workspace list.
|
|
- `Ctrl+Tab` opens the workspace switcher; `Ctrl+K` searches everything, workspaces included.
|
|
|
|
## Deleting a workspace
|
|
|
|
Deleting a workspace removes its memory, its sessions and its virtual files
|
|
(`<data>/workspaces/<id>/`). A folder on disk linked as Local storage is not deleted. Personal
|
|
memory is not affected.
|