Toolkits: reusable bundles of skills and connections, attachable independently of persona and memory

Today a set of skills, connections and MCP servers can only be bundled inside an agent definition (custom agent "Skills & connections", or a saved agent). Reusing the same toolkit with a different persona, or for a single task, means rebuilding it (for example, a research toolkit of document-scanning and summarizing skills plus a connection to a notes app). Tickets can pin skills but not connections or MCP servers. Memory can only be dropped together with the persona (Minimal system prompt).

Proposal:

• "Toolkits" as a first-class library object: skills + connections + MCP servers (optionally env vars and CLI options), attachable at every existing level (agent, ticket, team step, folder, project) with the same merge/replace rules skills already have.
• Agents reference toolkits rather than copying them, so an edit reaches every agent that uses one.
• A separate memory setting per agent and per ticket (off / read-only / read-write), independent of persona and tools.
• Optional, combined with the related request "Deliver a session's attached skills as native CLI skills": a toolkit's skills arrive as native CLI skills in the session.

Outcome: persona, toolkit and memory become three independent controls, so users can give a task capabilities without a persona or memory, an accessible entry point to harness engineering from the UI.

AgentsRoom diagnostics

• App version: 1.225.0
• OS: darwin 27.0.0 (arm64)
• Agent CLI: claude
• App language: system

Problem to solve

Skills, connections and MCP servers can only be bundled inside an agent definition; tickets can't pin connections/MCP; memory can only be removed together with the persona.

Proposed behavior

Toolkits as a library object attachable at agent/ticket/team step/folder/project levels by reference, plus an independent per-agent/per-ticket memory mode (off, read-only, read-write).

Who benefits

Users building specialist agents and teams who want to reuse the same toolkit across roles and tasks.

Acceptance criteria

Persona, toolkit and memory are independent controls: easy harness engineering from the UI.