Request an owner’s permission to use a listed keychain credential needed by a command. An approval card appears in the conversation, and owner approval automatically reruns the blocked command with access shared across that conversation.
Ask a person for access to one of their keychain credentials when a command needs it and this conversation has no grant yet. The platform posts an approval card where this conversation is happening; the owner clicks it, and the blocked command re-runs.
Review the instructions the agent will receive before you install.
Use this when the keychain manifest lists a credential you need but shows no grant for this conversation. Your own credentials in your own personal conversation never need this.
One call, from this session or any sub-agent. The approval belongs to the whole conversation, so every session in it sees the same grant.
curl -fsS -X POST "$AGENT_API_URL/v1/keychain/asks" \
-H "x-agent-capability: $AGENT_API_TOKEN" -H 'content-type: application/json' \
-d '{"credential":"<credential id>","purpose":"<what the command will do>"}'
purpose is one plain sentence about the command, not the whole task.You don't choose. The card appears where this conversation is: the Slack thread or channel, inline in the web session (and in its parent when you are a sub-agent), or the scheduled job's destination. Only the credential's owner can click it; nothing said in chat is approval.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Help QM organization admins inspect settings, stored memory, conversations, files, and operational records across the organization. It also supports confirmed configuration changes and external user management, while keeping admin grant changes in the dashboard.
Carry out website tasks in a remote browser, including expense submissions, authorized orders, and retrieving data behind a login. Personal browser profiles preserve sign-ins, while users handle login and verification screens themselves.
Sign in to a cloud provider’s command-line tool using a verification URL and one-time code approved on the user’s device. Check installation and account identity, save the login, and run commands within that user’s permissions.
Help users discover and connect apps, then run available app tools through QM’s authenticated backend. It checks connection status, presents consent options, and keeps Composio project keys out of user-facing setup.
Connect supported work apps through browser consent without sharing passwords with the agent. The skill checks available connection methods, provides a single-use authorization link when appropriate, and guides personal Slack account linking.
Set up recurring agent work for issues, tickets, or small fixes. The skill tests one real item first, then defines a repeatable procedure, tracks work to prevent duplicates, and holds outputs for human review.