@assemblyline-agents/margins
v10.4.0
Published
Official Assembly Line connection plugin for resource-scoped collaborative Markdown in Margins.
Maintainers
Readme
@assemblyline-agents/margins
Official Assembly Line connection plugin for resource-scoped collaborative Markdown in Margins. A binding can cover one page, one folder and its descendants, or the whole workspace.
Setup
assembly-line add margins agentNo developer OAuth registration or long-lived token environment variable is
required for the hosted service. In Margins, open the agent invite for the
page, folder, or workspace, choose Comment and suggest or Edit directly,
and paste the generated one-time packet into the agent's chat. Assembly Line
advertises margins__pair, redeems the packet on the host, and stores the
returned rotating access and refresh credentials outside the model sandbox.
For self-hosted Margins, set MARGINS_MCP_URL and optionally
MARGINS_ISSUER. Configure stable collaborator identity with
MARGINS_AGENT_ID, MARGINS_AGENT_NAME, MARGINS_AGENT_RUNTIME, and
MARGINS_AGENT_HARNESS.
Margins confines every claimed agent id to its agent_ namespace so a
binding can never claim a human user_* identity: a configured
agentId: "librarian" is recorded (and attributed in comments, suggestions,
and edits) as agent_librarian. The plugin validates the pairing response
against that namespaced form and stores the server-returned identity in the
credential.
The selected plugin enables every reviewed Margins tool. Gate or remove named
actions through plugins.margins.connections.margins.approval or disable.
Margins still enforces the packet's own scope and permission.
Comments and suggestions are classified as writes because they mutate shared workspace state. Margins applies its own permission check after Assembly Line's connection policy; a Comment and suggest binding can never edit canonical Markdown or create a page.
