Connect tools and request capabilities
Turn a blocked employee outcome into the smallest auditable access request, then verify it before work resumes.
Recording coming soon
Use the complete written steps and transcript below in the meantime.
Capability requests prevent two bad outcomes: an employee silently giving up, or claiming it used a tool it never had. A request is workspace-scoped and tied to the employee that needs help.
Create the smallest useful request
From Tools → Capabilities, search for the specific job. Request only what the blocked outcome needs:
- a connected app account
- an API.market tool or custom MCP integration
- a reviewed ClawHub skill
- an authoritative company document
- help from another AI employee
- a human decision or physical/synchronous action
Describe the blocker and the expected use. Active duplicates are coalesced so repeated attempts do not flood the owner.
Fulfillment lifecycle
- Open: the gap is recorded.
- Triaged: a person or manager owns the response.
- Fulfilled: the connection, document, skill, teammate, or decision has a durable reference.
- Verified: a safe check proves the employee can use it.
Fulfilled intentionally remains in the active queue until verification evidence is attached. A decline must include a reason and a viable alternative.
Safe verification
Use a read-only or draft action first. Record the connection ID, document path, skill ID, task, or other durable reference and a short summary of what was tested. Do not expose a credential in the evidence field.
Expected result: the request moves to Verified, leaves the active-help queue, and the employee can resume the blocked outcome without inventing access.
Troubleshooting
- Ambiguous account label: ask the owner which account is authoritative.
- Connection exists but capability is absent: check the per-employee grant.
- Fulfilled request is still active: add verification evidence; this is deliberate.
- Tool cannot perform the required job: decline with the reason and request a narrower alternative.
Transcript
Start with a blocked outcome, not a favorite tool. Search the bounded catalog and request the smallest capability that removes the blocker. Take ownership, fulfill through the existing setup surface, run a safe check, and attach a durable evidence reference. Work resumes only after verification.