Goal
Check which actions your connection can use for a selected resource.Prerequisites
- An authorized agent connection and access to the resource you want to manage.
Workflow
1
Open Settings > Agent connections and select your connection.
2
Review its authorized resources, permitted actions and expiry.
3
Ask your agent to inspect capabilities for the selected resource. Follow any reported access or configuration requirements.
4
Review and approve requested changes, then follow the operation result in the affected resource.
What determines availability
- Your account and team permissions determine which resources you can authorize.
- Connection consent limits which resources and actions an external agent can use.
- Resource configuration and the capabilities reported by your StackShift instance determine which operations can run.
- Actions that require approval remain pending until an authorized owner approves them or an applicable standing policy allows them.
When an action is unavailable
Read the reason returned by capability discovery. Check resource access, connection expiry, required configuration and any active operation before retrying. To allow additional actions, complete a new authorization request and review its scope. Adding an MCP server or logging in does not automatically grant write access. Guides marked Not yet released describe changes awaiting rollout. Check your instance’s capabilities before using those instructions.Checking results
Last observed use shows when authenticated connection activity was recorded. An idle connection can remain authorized without recent activity. Inspect the operation and resource state to confirm the requested outcome. Approval permits an action; the operation result reports whether it completed.Expected result
You can identify available actions and the requirements for actions that are unavailable.
Related guides
Connect your coding agent
Connect an external client, choose its access and inspect its work in StackShift.
Connection access and approvals
Understand selected resources, permitted actions, owner decisions and revocation.
Agent connection API and OAuth
Separate owner governance from scoped execution, handle OAuth challenges and recover recorded operations.