Skip to content

feat(bot): add owner-bounded application capabilities - #2017

Open
hmans wants to merge 1 commit into
hmans/plan-bot-accountsfrom
hmans/bot-capabilities
Open

feat(bot): add owner-bounded application capabilities#2017
hmans wants to merge 1 commit into
hmans/plan-bot-accountsfrom
hmans/bot-capabilities

Conversation

@hmans

@hmans hmans commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • define a shared, server-owned application capability catalogue with human-readable disclosure metadata
  • require every bot operation to intersect an explicit grant, the owner's live authority, and an explicit conversation context
  • show approved capabilities and the bot's owner-written data-handling description on management and profile surfaces
  • add the bot-only direct-message runtime API for listing/reading explicit bot DMs and posting text replies

This is PR 2 of the bot-account stack and depends on the bot identity/credential foundation.

Design

Verification

  • mise test-cli
  • mise test-frontend
  • docs website build
  • protobuf generation and compatibility check
  • mise license-check

Stack

  1. Bot account foundation
  2. Owner-bounded application capabilities (this PR)
  3. Contextual room and thread access

@hmans
hmans force-pushed the hmans/bot-capabilities branch from 55bd89f to 05cc196 Compare August 12, 2026 10:59
@hmans
hmans force-pushed the hmans/bot-capabilities branch from 05cc196 to 4b534b6 Compare August 12, 2026 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant