Advanced extension points

This part covers what else can belong to a plugin: the agent, the place it runs, the machine itself, utility inference and the browser. The guiding principle, repeated throughout the documentation: core owns the minimum, “every special case is a public primitive or is deleted”, and core “never branches on a provider id”.

• Agent providers and the provider bridge: two halves in one artifact, the ACP dialects, and bridge record mode.
• Environment providers: where a thread’s workspace lives; core owns the passage.
• Machine providers: the plugin creates compute, core owns enrollment and the daemon install.
• Host workers: your own Node code on an enrolled machine (files, wake lock, processes).
• AI services: bb’s utility inference and transcription.
• Desktop browsers: a real browser window on a host.
• Thread plugin metadata: a JSON namespace that travels with the thread.