Give each agent
its own identity.
A profile is an identity an agent or bot acts as, instead of acting as you. You choose the access it starts with, and it never holds more than you do.
Connect your agentProfiles are an early access experiment. Turn them on at Experiments.
profileCreate({
name: 'release-bot',
expires_at: '2026-12-31T00:00:00Z',
grants: [
{
resource_type: 'package',
resource_id: '<package id>',
permissions: ['package:read', 'package:execute'],
},
],
})Create a profile with a name, an expiry, and the grants it starts with.
Access that
only narrows.
A profile starts with the grants you pick. It gets more only when someone shares something with it, or when it creates something itself.
- You can hand over only permissions you hold on that resource right now.
- Grants are a snapshot. When you gain access later, the profile does not.
- Expiry only moves earlier. For more time, create a new profile.
Every layer has to agree
A request running as a profile reaches something only when your own live access, the profile's grants, every parent profile's grants, and the credential's scopes all allow it.
Being an org Owner does not skip a profile's limits. When a request is denied, the message names the layer that blocked it.
Sub-agents get less,
never more.
When your agent starts another agent, it can hand over a sub-profile with its own token. A sub-profile gets only what every parent holds, and it never outlives its parents.
Profiles nest up to 5 levels deep. Profile tokens work with the Kody Open API and the CLI.
Hand a sub-agent its own tokenSee which agent did it. End it in one step.
Runs record the profile and its parents, so activity shows which agent did the work. The Agent profiles page shows your profiles as a tree.
Revoking a profile ends it and everything below it, and cannot be undone. Jobs and triggers it turned on pause. Anything it created stays manageable by you.