Onevium
GitHubDownload
Core Workflows

Tools menu and work surfaces

Use the @ tools menu to choose whether Onevium should build a widget, browse the web, schedule work, connect a channel, save memory, run an agent, or call MCP tools.

Updated 2026-06-03

What the @ menu is for

The @ menu turns a plain prompt into a typed workflow. Instead of asking users to remember every capability Onevium has, it shows the available work surfaces directly inside the composer.

Use it when the task needs a specific kind of action: visual output, browser automation, recurring execution, team notification, saved context, delegated agents, external tools, or project files.

Available tools

Each entry maps to a user-facing workflow rather than an implementation detail.

  • Widget: Build charts, mockups, SVG diagrams, draw.io-style flows, and small interactive apps.
  • Browser: Open pages, inspect UI, click through flows, capture screenshots, and collect evidence from the live web.
  • Schedule: Turn a prompt into a recurring job, reminder, monitor, or periodic report.
  • Channel: Connect DingTalk, Feishu, or Discord bots so results land where the team already works.
  • Skill: Save reusable instructions for work you repeat often.
  • Memory: Preserve durable project facts, decisions, preferences, and corrections.
  • Agent: Delegate focused work to specialized sub-agents.
  • MCP: Connect tools, APIs, files, and data sources beyond the built-in desktop surface.
  • Plugin: Install capability bundles that add tools, skills, and workflows.
  • Files: Search and attach project files so Onevium starts with the right context.

How to choose the right tool

Start with the shape of the output. If the answer should be visual, choose Widget. If it needs proof from a live site, choose Browser. If it should happen later or repeat, choose Schedule. If the output belongs in a team room, choose Channel.

For project knowledge, choose Memory when Onevium should remember a fact across sessions. Choose Skill when the same process should be reusable. Choose Agent when a large job should split into focused workers. Choose MCP when the assistant needs access to systems outside the default desktop tools.

Example workflow

For a release review, attach the changelog with Files, ask Agent to split QA and documentation checks, use Browser to test the production page, use Widget to turn the results into a visual status summary, then create a Schedule that repeats the smoke test tomorrow morning.

The value is not that each tool exists in isolation. The value is that a user can combine them in one visible workflow without switching products.