v1.1.0

What's New

Actions System

Actions are reusable command configurations that can be shared across runners. This release introduces a layered override system for worker configuration.

Define actions as standalone files in ~/.granary/actions/<name>.toml:

command = "claude"
args = ["code", "--task"]
concurrency = 2
on = "task.unblocked"

[env]
CLAUDE_MODEL = "opus"

Or inline in ~/.granary/config.toml:

[actions.my-action]
command = "claude"
args = ["code", "--task"]
on = "task.unblocked"

Runners can inherit from actions via the action field:

[runners.my-runner]
action = "my-action"
concurrency = 4  # overrides the action's concurrency

Override chain: action defaults → runner config → CLI arguments.

New CLI Commands

• granary config actions — list, add, update, remove, and show actions
• granary worker start --action <name> — start a worker directly from an action

Silo GUI

• Settings screen now has an "Actions" section for managing actions
• Workers screen shows "Available Actions" alongside runners with quick-start buttons

Fully Backwards Compatible

All existing runner configurations and CLI usage continue to work unchanged. The action field on runners is optional and defaults to None.