Skip to content
← Trylle Journal
ChangelogAutomation

Changelog: scoped bots and repository automations

Bots now carry their own permission scope, automations can be pinned to a workspace, and every run reports the credits it consumed.

Trylle1 min read

Scoped bots

A bot is now a first-class service identity with its own grants. You can give one bot write access to the merge queue and nothing else, and the permission set is visible on the repository access page next to human collaborators.

Workspace-pinned automations

Automations inherit the scope of the workspace they were created in. They cannot reach repositories you never connected, and moving a repository between workspaces moves its automations with it.

Credit reporting

Every automation run now reports the credits it consumed, broken down by model and runtime, on the run detail page and in the organization usage view.