User guide · Chapter 6 of 12
Tips and quick commands
Every ODIN quick command for Claude Code, Claude and ChatGPT: turn ODIN on, pause it, turn it off, sign in again, switch project or space, ask about a person or a role, assign work and search the guide. With the exact rules for pausing and turning off.
On this page
By Wednesday Acme's people use ODIN all day, and they want shortcuts. Every agent gets the same commands. Claude Code shows them as slash commands, Claude's desktop and web apps list them in the + menu, and in ChatGPT you type @ODIN followed by the same words.
Which commands are there?
| What you want | Claude Code | ChatGPT (and plain words anywhere) |
|---|---|---|
| Turn ODIN on | /odin:on |
@ODIN turn on |
| Pause ODIN for a while | /odin:pause 30 |
@ODIN pause for 30 minutes |
| Turn ODIN off | /odin:off |
@ODIN turn off |
| See if ODIN is on and where you are working | /odin:status |
@ODIN status |
| Sign in again | /odin:login |
reconnect ODIN in the app's settings |
| Work in one project | /odin:project fleet |
@ODIN switch to project Fleet |
| Work in one space | /odin:space client-review |
@ODIN switch to space Client Review |
| Work in your personal space | /odin:personal |
@ODIN work in my personal space |
| Work across everything | /odin:everything |
@ODIN work across everything |
| Ask who someone is | /odin:who Tracy |
@ODIN who is Tracy? |
| Ask who has a role | /odin:who @release-approver |
@ODIN who is the release approver? |
| Give someone a task | /odin:assign tracy review the invoice by Friday |
@ODIN assign "review the invoice" to Tracy by Friday |
| Plan new work and see what relates to it | /odin:next we are adding team billing to Fleet |
@ODIN we are adding team billing to Fleet, what's next? |
| See how ODIN tailors answers to you | /odin:persona |
@ODIN how do you tailor answers to me? |
| Hand this conversation to a colleague, a role or a team | /odin:handoff tracy |
@ODIN hand this to Tracy |
| What colleagues noted or handed you | /odin:updates |
@ODIN what's new from my team? |
| Search this guide | /odin:docs pause |
@ODIN how do I pause? |
| Finish setting up, security first | /odin:setup |
@ODIN finish my setup |
| Hide setup reminders for a while | /odin:later 24 |
@ODIN remind me about setup tomorrow |
What exactly happens when I pause ODIN or turn it off?
These are the rules, with nothing left out:
| On | Paused | Off | |
|---|---|---|---|
| How long | until you change it | 15 minutes up to your company's maximum (4 hours unless your administrators change it), then on again by itself | until you turn it on |
| Who may | everyone | any member, unless your company turned pausing off | only where your company allows it, and always in a personal workspace |
| Project context when a session starts | yes | no | no |
| The gate checks your project's rules | yes | no | no |
| Your work is recorded | yes | no, only the pause itself | no, only turning off |
Some things never pause. Safety refusals, credentials blanked out of anything you send, the check that stops data leaving the company, restricted projects and private spaces, and alerts when an agent damages a repository all keep working whatever the state. Every change is in your company's audit log, and administrators can see who has ODIN paused or off. Signing in again does not change the state.
Where do administrators set the rules?
An administrator decides whether members may pause, for how long at most, and whether they may turn ODIN off. Ask your agent "ODIN, set our pause policy" or use the tool odin_set_odin_policy. Taking a right away ends what it allowed: if turning off is no longer allowed, everyone who had ODIN off has it on again.
How does ODIN tailor answers to me?
ODIN knows who you are in your company: your roles, your teams and the projects you work on, so your agent never has to guess that. On top of that it learns three things about how you like answers: how long (short, normal or detailed), for whom (a business reader gets the outcome, cost and decision first; a technical reader the mechanism, code and paths) and how they are laid out (bullets or prose).
What you say always wins: tell your agent "keep my answers short" and it is saved. When you react to an answer ("shorter", "more detail", "less technical"), ODIN learns from it. Until it knows, it starts from how your colleagues like answers and from your role, and if it is still unsure, your agent asks you once. ODIN never guesses anything personal about you, such as your age or gender: only these three things are kept. Ask /odin:persona or "how do you tailor answers to me?" to see it and change it.
Tips
- Pause ODIN instead of turning it off when you want a short break. It comes back by itself, so you never forget it.
- Say where you are working at the start of a long task. Your questions get shorter and your answers more precise.
- Ask "who is the @role" before assigning work, so it goes to the person who owns that job.
- Before you stop for the day, hand your conversation over. Whoever picks it up starts where you left off, in whichever agent they use.
Questions
Why can I not turn ODIN off?
Your company keeps ODIN on. You can pause it instead, and an administrator can allow turning it off.
Do quick commands work in every agent?
Claude Code has them as slash commands once the ODIN plugin is installed. Agents that support MCP prompts, such as Claude's apps, list them in their menu. In every other agent, the same plain words work because the agent calls ODIN's tools for you.