Choose tools from the composer
Use the @ menu to give a task the right files, work surface, reusable instructions, or connected tools.
Your workspaceThree ways to provide context#
Use @ for Onevium capability tags, project files, and previous-session references. Use / for commands and invocable Skills. Open Plugins in the left sidebar to manage saved plugins, Skills, and MCP connections together; the right-side tabs still provide their compact views.
A capability tag stays in the composer until you send the message. It asks the assistant to perform the named workflow; it is not the same as clicking a management tab.
Open the relevant menu#
Place the cursor in the active conversation's input and type @. Bare @ shows the capability choices; typing a filename or session title narrows the file/session results. Select the actual item rather than leaving an ambiguous name in plain text.
For saved capabilities, open Plugins in the left sidebar, switch between Plugins / Skills / MCP, and check the selected project or personal scope. The right-side tabs still expose Skills, Memory, Agents, MCP Servers, and Plugins. Settings → Tools controls the availability of tool groups; see the Tools settings reference for when changes take effect.
To reuse a saved Skill, open its details under Plugins → Skills and click Use skill. Check the project, add your request to the prepared draft, and send it. This opens a new conversation with the selected Skill reference; @Skill instead starts the workflow for creating a Skill. Follow Skills for both paths.
Create a visual from supplied data#
- Type
@and select Widget. - Add this complete small dataset and request.
- Send, open the result, and verify each value.
Make a bar chart from these sample counts:
April: 12
May: 18
June: 15
Title: Sample tickets. Unit: tickets.
Show the original values beside the bars and label the data as illustrative.
Follow up with one change, such as “Keep the values; use a horizontal layout.” You do not need to select Widget repeatedly for every refinement of the same artifact.
Capability tags#
Choose a tag available in your composer; follow its linked tutorial for setup requirements.
| Tag | What the request does | What to include |
|---|---|---|
| Widget | Builds charts, diagrams, mockups, or small interactive outputs | Source values, audience, output type |
| Browser | Requests browser automation | Exact URL and which browser surface to use |
| Schedule | Creates a recurring task | Project, timing, prompt, and intended destination |
| Recap | Summarizes work over a date range, optionally by project | Explicit period and project scope |
| Channel | Guides Feishu, DingTalk, Discord, or WeChat setup | Platform and project; scan for WeChat in its dedicated dialog, never put credentials in chat |
| Skill | Creates reusable instructions | Task, scope, input, and expected output |
| Memory | Helps create/edit Claude Code rules or topic-memory files | The fact/rule and file scope |
| Agent | Creates a focused delegated role | Responsibilities, allowed tools, output |
| Team | Uses the team Skill to coordinate real child sessions | Goal, member roles, file ownership, and acceptance criteria; confirm the plan first, then follow Teams |
| MCP | Helps configure an external server | Transport, URL or command, and scope |
| Plugin | Helps install/manage a plugin | Exact plugin name and source |
@Memory is not a shortcut to Onevium's database-memory settings. See memory and recap for those separate controls.
Team starts in a conversation. Check that the matching team Skill is callable, then use @Team. It has no separate right-panel management tab and is different from a channel bot team.
Browser choice matters. The @Browser guidance targets the Control Chrome connector. The built-in browser is a separate work surface, opened with its panel button or default Shift+Command/Ctrl+B. If you want that surface, explicitly say “Use Onevium's built-in browser.” Do not install an extension solely to open an internal preview.
Attach files and previous work#
For a README task, type @README, pick the intended project file, then add “Explain its setup steps and cite the relevant section.” To supply another conversation, type part of its title and choose it under Sessions.
Previous-session references supply contextual material, not a guaranteed copy of its complete history or current filesystem. A message expands at most three session references; use a concise recap if the handoff needs more.
Check the selected target#
Before sending, inspect the visible tags and attachments. Confirm the project, file, browser, or session matches the request. Afterwards, verify an actual artifact or tool result. For the chart, the values must remain 12, 18, and 15 with an illustrative-data label.
Common problems#
- No file/session result: type a more specific name and check the selected project.
- Tag inserted but nothing happens: send the message with a concrete request; selecting the tag alone is not execution.
- Tool unavailable: check its group in Settings → Tools and follow the linked reference for activation steps.
- Browser goes to the wrong surface: name built-in browser or Control Chrome explicitly and check the returned target.
Next steps#
Use workflow tips for commands and shortcuts, Widget for artifacts, and browser automation for page checks.