Start with the task.
Identify what the agent needs to read, change, or produce. A task that only needs local project files should not require broad access to unrelated services.
Product / Tools & connections
Bring the tools
the work needs.
Connect agents to the files, commands, and services relevant to their task, with access configured for the job.
A practical starting point
Make each connection
earn its place.
Configure the connection.
Use the supported setup path in your app build. Review the account, workspace, permissions, and any service costs before enabling access.
Verify a small action.
Check a narrow read or reversible operation before starting a larger workflow. Confirm where output appears and what the service recorded.
Put it into practice
Access to a tool is part of the brief.
For repository work, specify the project, branch, and whether the agent should prepare a change or publish it. For a work app, identify the workspace and records that belong in scope. For research, say which sources the agent should use.
Available connectors vary with the app build, the service, and your configuration. The connections shown on the homepage illustrate possible workflows; they are not a promise that every account is connected or every integration is available without setup.
Agents can also use tools inside their Linux computer. Review what you mount, copy, or otherwise make available there, and keep secrets out of shared notes and exported deliverables.