Explore guides
Agents, tools, and permissions
Understand host execution, provider setup, and the limits of permission policies.
Choose a provider for the work
The coding agent runs on the selected runtime computer. Desktop, web, and mobile use that runtime adapter. Providers retain their own authentication, configuration, and release channels.
Many providers need a separately installed CLI; Cursor uses its SDK integration without requiring a CLI. Consult the source provider guide for current setup details and model support.
Give the task useful context and tools
Start with the project and instructions the task needs. Reusable agent configurations, skills, MCP servers, and host terminals extend the workflow. Make the scope clear so the agent knows which system and repository it operates on.
Configure tool credentials on the host. A phone client does not move the work or provider credentials to the phone.
Permission modes differ by provider
Read-only, supervised, and automatic execution are provider capabilities, not interchangeable promises. Some adapters cannot enforce read-only or tool-free execution. Choose a provider that supports the restrictions your task needs.
When an agent does not start
Check the selected runtime, executable path, authentication, and model availability. Inspect diagnostics and tool output before retrying the same configuration. Provider SDK and host CLI versions can differ; the source guide describes their requirements separately.