Groups

Groups are workspace-scoped tags that bundle agents for shared config (API keys, env vars, feature flags) and organisational hygiene.

Group CRUD

List

athena group list
athena group list --all

Get

athena group get support
athena group get 019f902b-db73-7ea4-8ef2-60a8ff5747cd

Create

athena group create --name "Customer Support" --slug support
athena group create --name "Marketing" --slug marketing --description "Outbound + ops agents"

Update

athena group update support --name "Support Tier 1"
athena group update support --description "Updated description"

Delete

athena group delete support

Group membership

athena group add-agent support email-drafter
athena group remove-agent support email-drafter

Both are GET-then-PUT under the hood. There’s a known race if two clients modify the same group’s agent list concurrently — use idempotency keys or a single coordinator if you need strict ordering. See [D4 in the v1.1 issues] (tracked separately).

Group config

Groups carry three named config buckets — settings, environment, api_keys — that any agent in the group can read at execution time.

Get a bucket

athena group config get support --bucket settings
athena group config get support --bucket api_keys

Returns the full bucket as JSON:

{
  "openai_model": "gpt-4o-mini",
  "max_retries": 3
}

Set keys

athena group config set support \
  --bucket settings \
  --key openai_model --value gpt-4o \
  --key max_retries --value 5

--key and --value are paired in order — they must appear the same number of times. Mismatched counts exit 2 with a clear error.

Unset keys

athena group config unset support --bucket settings --key max_retries

Buckets

Bucket	Purpose	Visibility in agent runtime
`settings`	Default model, retries, anything tweakable	Read via `{{ settings.foo }}` in node templates
`environment`	Per-deployment env vars (region, base URLs)	Read via `{{ environment.foo }}`
`api_keys`	API keys, secrets — encrypted at rest	Read via `{{ api_keys.openai }}`; never logged or echoed by the engine