> Source: Onevium official documentation > Article: Everyday workflow tips and shortcuts > Original URL: https://onevium.com/docs/workflows/tips > Language: English > Updated: 2026-09-09 > Applies to: 1.1.22+ --- # Everyday workflow tips and shortcuts Use file references, commands, recaps, models, permissions, terminal, and Review in practical tasks. ## Use the controls that fit the task Shortcuts below are defaults; **Settings → Keyboard shortcuts** shows your current bindings. Runtime commands appear only when the connected Claude runtime reports them. ## Give a file task exact input Type `@` followed by a filename and select the result. Attach the smallest useful set instead of asking the agent to search everything first. ```text Read the attached README.md and package.json. List the documented start and test commands with file references. Do not install dependencies or run those commands yet. ``` If the task concerns a screen, attach its screenshot and name the relevant file or component. For a handoff, search an earlier session by title in the @ menu; use at most three session references in one message. ## Know what slash commands do here Type `/` and select a visible entry. A command chip stays at the start of the message; add details after it when appropriate. | Entry | Onevium behavior | | ---------- | --------------------------------------------------------------------------------------------- | | `/help` | Shows available commands and usage help | | `/cost` | Shows the conversation's recorded token-usage statistics | | `/loop` | Opens Create Automation; no recurring task is saved until you create it | | `/memory` | Asks to review/edit the project's CLAUDE.md file | | `/review` | Requests a code review; it is not the same action as opening the Review panel | | `/context` | Runtime-reported context breakdown, when available | | `/usage` | Runtime-reported usage/limits, when available | | `/config` | Runtime configuration interaction, when available; not a replacement for all Onevium Settings | | `/recap` | Runtime session recap, when available | | `/goal` | Goal status/control, when available; see its separate guide | Custom Skills can also appear here. Use the listed name, including a plugin namespace if shown. Do not assume commands from an upstream article are enabled merely because they start with `/`. ## Choose a session recap or a period report Use `/recap` for the current runtime's session recap. Use **@Recap** for Onevium work activity over dates and projects: ```text Summarize my work from 2026-09-01 through 2026-09-07 in this project. Group completed work, decisions, and open questions. Use the available activity records; distinguish missing records from no activity. ``` Select @Recap before sending. If its tool group is off, enable **Settings → Tools → Recap** and open a new conversation. This date-based report differs from both saved memory and the current session summary. ## Check model and mode before a longer run Open the model picker with **Option/Alt+M**, then select a provider and model actually configured for the task. Model choice and reasoning controls depend on that provider; the picker is not a guarantee that every optional capability works. Use **Shift+Tab** in the composer to switch Code/Plan. For example: ```text Plan a clearer empty state for this component. Identify the affected file and acceptance checks before editing. ``` Check the separate permission control before implementation. Switching to Plan does not change the provider, and choosing a model does not grant tool permissions. ## Connect terminal output and Review Open the terminal with **Command/Ctrl+J**. Confirm its current directory before running the project's documented command; a reused terminal can retain earlier state. Open Review with **Shift+Command/Ctrl+G** after an edit. Inspect the actual changed files, then ask about a specific difference: ```text Explain the changes in this component and the checks actually run. Identify any unrelated edits without reverting them. ``` Review displays diffs. `/review` asks the agent to analyze code. Neither automatically commits or pushes the changes. ## Default shortcuts worth learning | Action | macOS | Windows/Linux | | ------------------------- | --------------- | ------------- | | Search projects and chats | Command+K | Ctrl+K | | New chat in active column | Command+N | Ctrl+N | | Open project folder | Shift+Command+O | Ctrl+Shift+O | | Browse all files | Shift+Command+E | Ctrl+Shift+E | | Toggle terminal | Command+J | Ctrl+J | | Toggle Review | Shift+Command+G | Ctrl+Shift+G | | Toggle built-in browser | Shift+Command+B | Ctrl+Shift+B | | Open model picker | Option+M | Alt+M | | Open add-files menu | Option+A | Alt+A | | Focus composer | Shift+Escape | Shift+Escape | | Switch Code/Plan | Shift+Tab | Shift+Tab | | Stop the current response | Escape twice | Escape twice | Shortcut behavior depends on focus and your saved bindings. Stopping the response is not the same as stopping every separately managed development service. ## Try a complete small loop Open a project, attach README.md, request its documented commands, and verify the references. Then ask for a small wording edit, open Review, and inspect the diff. Finish with a short recap listing the edit, checks, and next step. This exercise uses ordinary controls you can inspect at each stage; it needs neither extra plugins nor a new automation. ## Next steps See the [tools menu](https://onevium.com/docs/tools-menu), [files, terminal, and Review](https://onevium.com/docs/files-terminal-review), [Goal Mode](https://onevium.com/docs/goal-mode), or [settings reference](https://onevium.com/docs/settings/reference) for fuller instructions.