sync spec: add Slack destinations to AI routines - #68
Merged
Conversation
Routines can now deliver through Slack in addition to email. The
destination response shape moved from an email-only object to a union:
- RoutineEmailDestination -> RoutineDestinationResponse (oneOf email | slack)
- new RoutineSlackDestination schema (single channel or DM recipient)
- routine-create/update bodies accept an email destination (recipient
emails + user group IDs) or a Slack destination (recipientId +
slackRecipientType)
These are request/response body changes on the existing ai-routines
operations, so they surface via --body rather than new flags.
Side-effect change pulled in by the full sync:
- new documentsUpgradeLayout operation: POST /api/v1/documents/{identifier}/upgrade
(documents upgrade-layout)
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
n8agrin
approved these changes
Jul 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Syncs the embedded OpenAPI spec from
exploreomni/omni@main. Headline change is Slack delivery for AI routines.RoutineEmailDestination→RoutineDestinationResponse(oneOfRoutineEmailDestinationResponse|RoutineSlackDestination).RoutineSlackDestinationschema — a single Slack channel ID (e.g.C01234567) or user DM (U01234567); exactly one recipient per Slack routine.routine-create/routine-updaterequest bodies now accept either an email destination (recipientEmails+userGroupIds) or a Slack destination (recipientId+slackRecipientType). These are body-schema changes on the existingai-routinesoperations, so they surface via--body(visible with--schema), not new flags.Side-effect change (pulled in by the full sync)
documentsUpgradeLayout→POST /api/v1/documents/{identifier}/upgrade, wired up asdocuments upgrade-layout <identifier>.Test plan
make buildmake test(all packages pass)./bin/omni documents upgrade-layout --help— new command present with<identifier>positional./bin/omni ai-routines routine-create --schema— body reflects the email/Slack destination union