Language: English
Instrumentarium
The agent can use the terminal, files, web, browser, memory, and more. Most power lives in skills and plugins so the core stays lean. The matrix below is a novice bridge: job → start surface → toolsets.
New here? Start with scenarios or the capabilities catalog. Use cases · Capabilities
Back to capabilities Ecosystem Getting started
How the product looks
Desktop chat with Plan · Report · Design · Runs, Work inbox, approvals, and skills — the same surfaces the product pages claim.

Privacy-scrubbed Desktop captures and marketing-demo loops — not a live customer session, credential, or private project.
Where to start
Novice bridge: match the job to a starting surface, then enable the toolsets you need. Prefer skills / plugins / MCP before asking for a new core tool.
| Job | Start here | Toolsets & edges |
|---|---|---|
| Ship code | Desktop chat + Plan rail, or CLI/TUI | terminal · file · code_execution · skills (lang/PR) |
| Research brief | Desktop + Research Pro preset | web · browser · research skills · optional MCP |
| Ops digest | Desktop or Work Mode goal | terminal · web · cron · approvals |
| Messaging agent | Self-hosted gateway | messaging toolset · approvals · platform adapter |
| Standing automation | Cron job or kanban board | cronjob · kanban · delegation (process-local) |
| Custom capability | Ecosystem page → footprint ladder | skill → plugin → MCP → core tool (last) |
Enable/disable per platform with `vibeos tools` or config.yaml. Service-gated tools (kanban, Home Assistant, …) stay off the schema until configured.
What it can touch
Files & code
Web & browser
Memory & session search
More tool families
Built-in tool families
Cron, kanban, delegate
Vision, image, TTS
Research Pro
Cited multi-source research without growing the core tool schema: search backends, skills that grade evidence, MCP for apps, and scheduled briefings.
Search & extract
Research skills
Workspaces & CLI
Apps & literature MCP
How capability grows
Skills
MCP servers
Plugins
Model providers
Hooks
Run custom code at lifecycle points — observe, rewrite, or block — without crashing the agent if a hook fails.
Control surface
Enable or disable toolsets per platform with `vibeos tools` or config.yaml. Security approvals, checkpoints/rollback, and credential pools stay under your control.