Customizing your project
Shape what your agents know and can do — agents, skills, secrets, connected tools, channels, members, and settings — from one place.
Open Customize from a project to configure everything about how it works.
It's a single overlay with a tab per area; changes are saved to your project as
code (in machine.toml and the agent config), so they're versioned and travel
with the repo.
Agents
Browse the project's agents and read each one's instructions. Agents are the personas your sessions run as — shaped around how your team actually works. Every project ships with sensible defaults so it works out of the box; refine them as you learn what you want.
Skills
See the skills available to your agents. A skill packages a workflow you repeat into a reusable shortcut the agent can invoke. Open one to read its documentation and what it does.
Secrets
Manage the API keys, tokens, and config your agents need. Add a value, control who can use it (the whole project, specific members, or just you), and set personal overrides so your own credentials don't leak into shared runs. Secrets are encrypted at rest and handed to sessions as environment variables — never written into the manifest.
See Managing secrets for the full walkthrough.
Connectors
Connect the external tools your agent should act in — Slack, Gmail, Salesforce, Notion, and many more — so it can do real work without you in the loop. For each connector you can:
- Connect credentials (a one-click connect for supported apps, or your own token).
- Set permissions per action — allow it, require approval, or block it — with rules that match specific tool calls.
- Set a global default policy across all tools, then carve out exceptions.
See Connecting your tools for setup details.
Channels
Drive the project from where your team already talks. Connect a Slack workspace (or Telegram) and pick the default agent, model, and instructions the channel uses, so anyone can kick off work with a message.
Members
Control who can access the project and what they can do. Invite people by email, assign a role — Manager, Editor, or Viewer — and manage pending invites. You can also grant access to whole groups so teams scale without per-person setup.
Settings, Dev, and Commands
- Settings — project name and description, project-level environment configuration, and the default sandbox image sessions boot from.
- Dev — development tooling and endpoints for working on the project locally.
- Commands — define reusable commands your agents can run.
Because every customization is saved as code, you can review it like any other change, roll it back, and see exactly how a project was configured over time.
Related: Managing secrets · Connecting your tools · Agents · Accounts & roles.