Workbench is an in-app AI workspace with a backend capability registry. Each capability has a purpose, expected inputs, outputs, approval rules, and sometimes an asynchronous wait step.
Use this page to understand what Workbench can do. External agents should use TextMine MCP server or API and developer docs when they need direct API or MCP tool access.
Capability rules
- Read capabilities can usually run without approval.
- Mutating configuration or durable data requires approval.
- Long-running actions have matching wait capabilities.
- Workbench should inspect or search documents before acting on a vague source scope.
- Saving files into Vault is different from using files as temporary Workbench context.
Document and Vault capabilities
Legislate and comparison capabilities
MCP provider capabilities
The provider import path is intentionally bounded: Workbench imports selected files, not entire provider repositories. The backend limits a single import batch to selected files and a total size cap.
Playbooks
Reports and templates
Workflows and agents
Records and schemas
Workbench skills and task lifecycle
Safe-use guidance for agents
Agents should return the capability names they used, the IDs they touched, and any approvals they requested. For durable mutations, include enough context for audit: Vault IDs, document IDs, workflow IDs, run IDs, record IDs, report IDs, provider IDs, and imported file names. Last modified on June 16, 2026