Talking to the Associate
Open the Associate from the bottom-centre control anywhere in the V2 dashboard. Type a request in plain language; you do not need a command for normal work.
Choose a model
Use the model selector or /model to choose from the model tiers allowed by your role and company policy. Use the standard tier for everyday work and the higher-capability tier only when the request needs deeper analysis.
Current commands
Type / to see the commands available in your session. V2.0 exposes these core shortcuts:
| Command | Purpose |
|---|---|
/new | Start a new conversation. |
/model | Choose an allowed model tier. |
/brain | Open the permission-scoped Business Brain inspector. |
/approvals | Review staged changes awaiting a decision. |
/jobs | Open supported Associate job/activity information. |
The palette is the source of truth. Commands from older documentation—such as /compact, /export, /audit, /status, /blocked, /plan, /focus, /tools, /verbose, /concise, and /memory—are not V2.0 commands unless they appear in the live palette.
Add context
When you are inside a project, the current project can appear as a context chip. Remove it when you want a broader company/personal answer. Supported entity and document attachments narrow the request but never expand your permissions.
The Associate re-resolves company/workspace context when you switch. A delayed request or old conversation cannot authorise access to the previous tenant.
While it works
- Responses stream as typed lifecycle events.
- Tool progress is displayed without treating intermediate diagnostics as a second answer.
run.finishis the canonical completion event.- You can cancel a run; cancellation waits for acknowledgement so resume state is not silently lost.
- Reconnecting resumes from the last acknowledged event without intentionally duplicating prior frames.
Conversations
Conversation history is company-scoped. Use /new when you want a clean thread. Reopening a conversation restores its saved messages; the latest request and current authorised scope still control what the Associate may do.
Approvals
When a supported action requires review, the Associate stages it instead of applying it immediately. Open /approvals, inspect the proposed change and scope, then approve, edit, or reject it.
Permissions are always rechecked
A conversation, attachment, task link, account link, or Brain memory cannot grant access by itself. BluPrint checks active membership and object scope on the backend when data is read or an action is applied.
Next
Last updated: 2026-08-05