Capsule-native
Assistants share only the resource budget and collaboration boundary of the Capsule that owns them.
Specification preview
Assistants
Capsule-native software that performs declared operations, follows opt-in routines, and collaborates through explicit capabilities.
Assistant Spec v1 and its developer workflow are in preview. Public installation is not available yet.
Assistant model // v1
Useful by design. Bounded by contract.
Every Assistant lives inside one Capsule. Its manifest declares what it can do, which Service operations it may request, and which other Assistants it may call.
Declared capabilities
Collaboration uses named operations. Installing one Assistant never grants open access to another.
Opt-in routines
Scheduled work starts disabled. The Capsule owner chooses if and when each declared routine runs.
Secrets stay in Services
Provider credentials belong to Services. Assistants request allowed operations instead of receiving raw API tokens.
For creators
A small contract. A clear path to ship.
The preview workflow starts with one operation, declares only the capabilities it needs, validates the manifest, and prepares an immutable artifact for the Capsule runtime.
Read the Assistant development preview (opens in a new tab)- 01Describe identity and immutable artifact
- 02Expose typed, named operations
- 03Request least-privilege capabilities
- 04Keep every routine opt-in
Future reference // not available yet
Salesnator
A planned Meta Ads specialist. Its first validation slice is read-only campaign health: inspect declared account data, produce a recommendation, and optionally request a notification—without changing campaigns or handling provider tokens.
- campaign-health
- meta-ads.read
- notifications.send