openfabriq
Reference

Permissions

Every word of can, and what it does for each source.

Every word of can, its effect for each source of a run, and what the engine refuses whatever can says. Without can, an agent can only read.

Words of can

WordEffect on GitHub
add_commentComments on the issue or the pull request
add_labelsAdds labels; { add_labels: [a, b] } allows only those
remove_labelsRemoves labels, with the same restriction
create_pull_requestPushes a branch and opens a pull request; { create_pull_request: [a, b] } puts those labels on every pull request it opens
push_to_pull_requestPushes commits to the current pull request
request_changesPublishes a review that requests changes
create_issueCreates an issue; { create_issue: [a, b] } puts those labels on every issue it opens
close_issueCloses the issue of the run, never another one
close_prCloses the pull request of the run, without merging it
merge_pull_requestMerges the pull request of the run, only under its conditions (labels, only_paths, except_paths; paths is the old name of only_paths, still read) and the engine's locks

On create_issue and create_pull_request, the agent does not choose the listed labels. Each one starts issue.labeled or pull_request.labeled, so another automation can listen to those only. validate refuses the list when the automation itself listens to that labeled event without a labels filter, or with one of those labels.

merge_pull_request needs at least one condition, and is refused with from: anyone. See Auto-merge. Without it, a person merges.

Per source

WordGitHubSlackLinearSentryWebhook
add_commentIssue or PRReply in the threadComment on the Linear issueNote on the Sentry issueNowhere to answer
add_labels, remove_labelsIssue or PRRefusedLabels of the Linear issueRefusedRefused
create_pull_requestFrom an issue or a run with no subject; not from a PRYes, link posted in the threadYes, identifier in the titleYes, with the Sentry linkYes
create_issueYesYesYes, with the Linear linkYes, with the Sentry linkYes
push_to_pull_request, request_changes, close_pr, merge_pull_requestOn a PRRefusedRefusedRefusedRefused
close_issueOn an issueRefusedRefusedRefusedRefused

A run with no issue or pull request, such as a schedule or a push, has nothing to comment on, label or close.

validate refuses a word that makes no sense for an automation that only listens to that source. When the automation also listens to GitHub, the engine refuses such an output at run time, by the run's source.

What the engine always refuses

  • Code (create_pull_request, push_to_pull_request) whose checks still fail at the end of the run.
  • Commits that change a file under .github/workflows/.
  • More than one run's share of writes, so an agent looping on a tool cannot flood anyone nor hold up the other projects' writes: 5 issues, 10 comments, 3 change requests, 5 add_labels and 5 remove_labels calls of at most 20 labels each, and one close. A label repeated in a call is written once.
  • Anything outside can.

The engine closes last, after the run's other outputs, so the comment that explains why comes first. Refused outputs are recorded in the run and shown in the studio's Outputs tab.

On this page