Omniscio

Agent Tools (consolidated dashboard)

Agent Tools is the sidebar group that nests Omniscio's tool and key views under one collapsible row, plus a dashboard panel that counts CLI Tools, Skills and MCP Servers, with API Keys, Agent Email and Browser Logins nested below them.

On this page

What it is

Agent Tools is one of the nine categories on the Installed Plugins page. It gathers the tool- and key-related views your agents run on under one heading — CLI Tools, Skills, MCP Servers, API Keys, Agent Email, Browser Logins and the other tools filed under it — and it owns a dashboard panel. Three of them are tracked by the dashboard usage roll-up: CLI Tools, Skills, and MCP Servers. API Keys is a tabbed hub combining your personal gateway key + credit balance with a read-only inventory of every key/secret on the machine; it is full-pane and is NOT part of the dashboard roll-up, and neither are Agent Email and Browser Logins. The side nav does not draw an Agent Tools row or nest these tools: each one keeps its own row, view and settings, and appears in the side nav only if you add it.

The category is purely a filing label on the Installed Plugins page — there's no new database table, no new scanner, and no new auth surface. The Overview link in the section heading opens the Agent Tools dashboard: a three-tile count grid (CLI Tools / Skills / MCP Servers), a "Top invoked · last 30 days" table, and a "Recent activity" list. Clicking any tile or row jumps you into the child view that owns the detail.

Where to find it

How to use it

  1. Find the Agent Tools section on the Installed Plugins page. Open Installed Plugins at the bottom of the side nav and look for the Agent Tools section. It is a section of that page, not a row in the side nav.
  2. Click the section's Overview link to open the dashboard. The link is shown when the category's overview row is visible. The right pane shows three tiles, a top-invoked table, and a recent-activity list. Loading from a cold cache takes <300ms; subsequent loads in the same 30-second window are instant.
  3. Click a tile to jump into a child view. The CLI Tools tile opens the existing tools view; Skills opens the skills catalog; MCP Servers opens the configured-servers list. Each child still owns its own kebab actions, sort dropdowns, and detail panes — the dashboard doesn't replace them.
  4. Top invoked / recent activity rows are clickable. Each row in either table jumps to the owning child view (skills row → Skills, MCP row → MCP Servers). The CLI Tools tile is the only way to reach the tools child from the dashboard — tool invocations aren't tracked in tool_invocations (which is skill/MCP only), so they don't appear in the top-invoked or recent tables.
  5. Put a tool in the side nav. Each tool in the section has Open and an In side nav switch. The switch adds a row for it to the side nav (or takes it off); once it is there you can drag it into one of your own folders. A tool whose feature is switched off shows Turn on instead.

How it behaves

How it works

The parent is registered as a virtual project via AGENT_TOOLS_PROJECT_ID = '__agent_tools__' in virtual-project-ids.ts, with a manifest entry in integration-registry.ts. Membership is a rule, not a list: every manifest that carries parentGroupId: 'agent-tools' is filed under the category and listed in the Installed Plugins page section (src/renderer/src/features/tools-hub/tools-catalog.ts). The registry validator enforces four invariants on parentGroupId (referenced parent exists, parent is kind: 'amc-builtin', no nesting deeper than one level, no self-reference). The side nav no longer draws category rows, so none of this depends on how the side nav is arranged.

The dashboard panel is AgentToolsDashboard.tsx, lazy-imported directly from the integration UI registry ui-registry.ts (via import('../features/agent-tools/AgentToolsDashboard')). It fires a single IPC call — AGENT_TOOLS_DASHBOARD_SUMMARY — and re-fires on tool-invocations:scanner-progress and skills:list-changed push events so counts and recent rows stay live without polling. The backend handler in agent-tools-handlers.ts builds the summary by reading the skills service's listInstalled(), counting mcpServers keys from ~/.claude.json, reading listDetectedTools() from SQLite, and querying tool_invocations for top-N (30-day window, capped at 10) + recent-N (capped at 10). A 30-second in-memory cache absorbs repeated mounts; the cache is wiped when either invalidating channel fires through the onPush bus, so the dashboard auto-refreshes when a session finishes invoking new tools or the user installs a new skill. There's no schema change — tool_invocations, skills, and detected_tools already exist for the child views; the dashboard handler just aggregates over them.

  • tools-hub.md — the Installed Plugins page, its sections and the In side nav switch
  • use-skills.md — the Skills child view (browse, install, edit skills)
  • mcp-servers.md — the MCP Servers child view (configured servers + usage tracking)

Last verified 2026-09-25