Plugin manifest reference

The manifest is the entire contract between a plugin and the host. Get it right and everything else (install, permission grants, slot mounting, capability checks) falls into place automatically.

File location

manifest.yaml lives at the root of the .adosplug archive. The host opens the archive, reads the manifest first, and refuses to unpack anything else if the manifest fails validation.

Top-level shape

Identity and configuration live as flat top-level keys. There is no plugin: wrapper.

schema_version: 1     # 1, 2, or 3
id: com.example.thermal
version: "1.0.0"
name: "Example Thermal"
description: "One sentence."
author: "Example Author"
homepage: "https://example.com/thermal"
license: "GPL-3.0-or-later"
risk: medium          # low | medium | high | critical

compatibility:        # required
agent:                # optional, agent half
gcs:                  # optional, GCS half

At least one of agent or gcs must be present. The host accepts plugins that ship only one half; the com.example.hello-panel plugin in Your first plugin, for example, is GCS-only.

Field	Type	Notes
`schema_version`	int	`1` baseline. `2` unlocks the v2 agent fields (`vendor_attribution`, `subprocess_spawn`, `per_drone_config`, `target_profiles`). `3` unlocks the MCP `tools` / `resources` / `prompts` contributions on both halves. Values outside 1 to 3 are rejected. Every version parses an identical-shape older manifest, so the field is informational: it lets tooling route on schema generation.
`id`	string	Reverse-DNS, lowercase, dotted. Validated against the plugin-id pattern.
`version`	string	Semver.
`name`	string	Operator-facing display name.
`description`	string	One short sentence.
`author`	string	Free-form.
`homepage`	url	Optional.
`license`	string	SPDX expression. `GPL-3.0-or-later` recommended.
`risk`	enum	`low`, `medium`, `high`, `critical`. Defaults to `medium`.

The manifest also accepts optional install-dialog content fields the GCS renders for a richer pre-install summary (description_long, features, hardware_requirements, resource_impact, required_fc_parameters, telemetry_fields, documentation_url, screenshots). The agent does not interpret any of them.

`compatibility`

Field	Notes
`ados_version`	Required. Semver range. Checked by the agent at install for every plugin, including GCS-only ones.
`gcs_version`	Optional. Semver range matched against the running Mission Control build.
`supported_boards`	Optional list of board tokens. Each entry is a board id (the HAL profile stem, such as `cm4` or `rock-5c-lite`) or a SoC (such as `rk3588s2`), compared case-insensitively, or `"*"` for any board. An empty list (the default) also means any board. The agent refuses install or enable on a board that matches no entry. The tokens for each board are listed on Supported hardware.
`min_tier`	Optional integer 1 to 4. Minimum compute-class tier the plugin needs. The supervisor refuses install or enable on a board whose detected tier is below this; a board with an unknown tier is never blocked.

Node profiles are declared on the agent half (agent.target_profiles), not here.

`agent`

agent:
  entrypoint: "agent/plugin.py"
  isolation: "subprocess"        # the only mode the agent runs
  runtime: "python"              # python (default) or rust
  permissions:
    - id: event.publish
    - id: mavlink.read
  resources:
    class: standard              # standard (default) or heavy (first-party only)
    max_ram_mb: 96               # default 96, range 8 to 4096 (heavy: 65536)
    max_cpu_percent: 25          # default 25, range 1 to 100 (heavy: 3200)
    max_pids: 12                 # default 12, range 1 to 256 (heavy: 4096)
  target_profiles: ["drone"]     # subset of drone, ground-station, workstation, compute
  http: false                    # serve an HTTP API under /api/plugins/<id>/x/
  binaries: {}                   # per-architecture binaries, referenced as bin:<name>
  payloads: []                   # files fetched at install instead of packed
  declared_capabilities: []      # capabilities this plugin defines for its own data
  contributes:
    services: []                 # optional extra service units
    shared_topics: []            # event-bus topics this plugin owns

entrypoint is a relative path inside the archive (no absolute paths, no ..). For a file-path entrypoint like agent/plugin.py the runner loads a class named Plugin. A module:Class entrypoint is also accepted and is how built-in plugins declare themselves. A runtime: rust entrypoint may instead be bin:<name>, resolved through binaries. isolation: subprocess is the default and the only mode the agent runs. An inprocess manifest parses but is refused at install, whoever signed it: every plugin runs as its own unit. runtime: rust runs the entrypoint as its own binary.

Agent field reference

Field	Type	Default	Notes
`entrypoint`	string	required	A `module:Class` id (built-in plugins), a relative path to the half’s entrypoint inside the archive, or `bin:<name>` naming a `binaries` entry (`runtime: rust` only). No `..`, no absolute path.
`isolation`	enum	`subprocess`	`subprocess` is the only mode the agent runs. `inprocess` is refused at install.
`runtime`	enum	`python`	`python` runs the entrypoint under the shared Python runner; `rust` execs the plugin’s own cross-compiled binary directly under the service manager. Older manifests without the field load as `python`.
`permissions`	list	`[]`	Capability requests. See permission shape.
`resources`	object	see below	Hard limits the supervisor enforces, and the resource `class`.
`contributes`	object	`{}`	Agent-side contributions: `services`, `shared_topics`, `drivers`, `vision`, and the MCP lists.
`mavlink_components`	list	`[]`	MAVLink components the plugin registers.
`target_profiles`	list	`["drone"]`	Subset of `drone`, `ground-station`, `workstation`, `compute` (`ground_station` reads as `ground-station`). Must list at least one. `drone` is an aircraft node, `ground-station` a ground node, `workstation` the operator’s own machine (a GPU box or a Mac), `compute` a headless worker. The agent refuses to install the agent half on a node whose profile is not listed (`incompatible: target_profiles excludes <profile>`). A GCS-only plugin has no agent half and is not gated. See Node profiles.
`binaries`	map	`{}`	Per-architecture binaries, `{<name>: {<arch>-<os>: <path>}}`. See Per-architecture binaries.
`payloads`	list	`[]`	Files the agent downloads at install instead of shipping them in the archive. See Install-time payloads.
`http`	bool	`false`	Serve an HTTP API for the operator. See Plugin HTTP.
`declared_capabilities`	list	`[]`	Capabilities the plugin defines for its own shared data. See Shared topics and declared capabilities.
`contains_vendor_binary`	bool	`false`	Set true when the archive ships a pre-compiled vendor binary; requires `vendor_attribution`. Schema v2.
`vendor_attribution`	list	`[]`	Source-offer records. Required (non-empty) when `contains_vendor_binary` is true. Schema v2.
`subprocess_spawn`	list	absent	Allowlist of binary basenames the plugin may exec via `ctx.process.spawn`. Requires the `process.spawn` permission. Schema v2.
`per_drone_config`	bool	`false`	Run one process instance per connected drone with a distinct `ctx.agent_id` and a per-drone config file. Schema v2.
`test_fixtures`	map	`{}`	Map of friendly name to fixture YAML path, replayed by the SDK test harness.

`agent.resources`

Field	Default	Range (`standard`)	Range (`heavy`)
`class`	`standard`
`max_ram_mb`	`96`	8 to 4096	8 to 65536
`max_cpu_percent`	`25`	1 to 100	1 to 3200
`max_pids`	`12`	1 to 256	1 to 4096

class: heavy is for a workload such as reconstruction or accelerator inference that needs most of a node. Only a first-party signer may declare it; any other signer is refused with refused: heavy_resources_first_party_only. A value outside its class’s range fails manifest validation.

Per-architecture binaries

A Rust plugin that ships for more than one architecture maps a binary name to one path per <arch>-<os> host. The keys are aarch64-linux, x86_64-linux and aarch64-macos.

agent:
  runtime: rust
  entrypoint: "bin:example-link"
  binaries:
    example-link:
      aarch64-linux: bin/aarch64-linux/example-link
      x86_64-linux: bin/x86_64-linux/example-link
      aarch64-macos: bin/aarch64-macos/example-link
    example-worker:
      aarch64-linux: bin/aarch64-linux/example-worker
  contributes:
    services:
      - name: worker
        command: "bin:example-worker --serve"
        profiles: [workstation, compute]

bin:<name> works as the entrypoint and as the first word of a service command, and resolves to this host’s path when the unit is written. Names match [a-z0-9][a-z0-9_-]{0,63}. Every binary a node would run (the entrypoint, plus each service whose profiles include this node) must have an entry for the node’s architecture, or the install is refused with incompatible: no binary for <arch-os> before anything is unpacked. The file itself must be in the archive or in an applicable payload.

Install-time payloads

Large files (per-architecture binaries, models, a wasm asset) can stay out of the archive. The agent downloads each payload that applies to the node during the install, after the signature and compatibility checks.

agent:
  payloads:
    - path: bin/aarch64-linux/example-worker
      source: "https://github.com/example/example/releases/download/v1.0.0/example-worker-aarch64-linux"
      sha256: "<64 lowercase hex>"
      size_bytes: 8912344
      arch_os: aarch64-linux
      profiles: [workstation, compute]

Field	Required	Notes
`path`	yes	Destination inside the plugin’s install directory. A relative path; each `path` appears once.
`source`	yes	An `https://` URL. It must be on the same host allowlist as a URL install (GitHub release hosts, S3, the cloud relay’s archive hosts, `localhost`), and every redirect hop is checked.
`sha256`	yes	64 lowercase hex characters.
`size_bytes`	yes	The exact size, 1 byte to 1 GiB.
`profiles`	no	Node profiles that fetch it. Absent means every profile.
`arch_os`	no	The one `<arch>-<os>` host that fetches it. Absent means any.

Because the payload list lives in manifest.yaml, the archive signature covers every source, sha256 and size. The agent hashes while it streams, refuses the install on a mismatch, and only then moves the file into place. Payloads do not count toward the archive size caps. The install attestation lists each applied payload with its pinned sha256.

Plugin HTTP

http: true asks the host for an HTTP socket. The host creates a private directory for the plugin under the agent’s run directory, passes the socket path in ADOS_PLUGIN_HTTP_SOCKET, and the plugin serves HTTP on it. The agent’s control surface then forwards /api/plugins/<id>/x/<path> (GET, POST, PUT, PATCH, DELETE and WebSocket upgrades) to the plugin as /<path>, with the query string kept. The control surface authenticates the operator first, so a request that reaches the socket is already an operator request. When nothing is listening the route answers 503. See the REST API. Every plugin process also receives ADOS_NODE_PROFILE (drone, ground-station, workstation or compute), so a plugin that behaves per profile never reads the agent’s config files.

Services

contributes.services declares extra service units beside the main process. A bare string is a service whose name is its command.

agent:
  permissions:
    - id: network.outbound
    - id: network.listen
  contributes:
    services:
      - name: node
        command: "bin:example-node --port 8092"
        restart: always              # on-failure (default), always, or no
        ready_check: "http://127.0.0.1:8092/healthz"
        profiles: [workstation, compute]
        listen_ports: [8092]

Field	Notes
`name`	Lowercase alphanumeric plus `._-`, starting with an alphanumeric. The unit is `ados-plugin-<id>-<hash8>-<name>.service`: dots in the id become hyphens, and `<hash8>` is the first 8 hex digits of the SHA-256 of the id. `GET /api/plugins/<id>` reports each service’s log path.
`command`	The argv. The first word may be `bin:<name>`.
`restart`	`always`, `on-failure` or `no`.
`ready_check`	An `http(s)://127.0.0.1:<port>/...` URL or a command, probed by `GET /api/plugins/<id>/readiness`.
`profiles`	Node profiles the service runs on. Absent means every profile the plugin installs on.
`listen_ports`	TCP ports this service may bind, 1024 to 65535, at most four. Declaring any needs both `network.listen` and `network.outbound`. The service unit gets `SocketBindAllow` for exactly these ports; every plugin unit carries `SocketBindDeny=any`, and the main process never listens.

Shared topics and declared capabilities

A plugin can own event-bus topics and share them with other plugins. Its topics live under plugin.<leaf>., where <leaf> is the last segment of the plugin id (com.example.mapper owns plugin.mapper.*).

id: com.example.mapper
agent:
  permissions:
    - id: event.publish
  declared_capabilities:
    - id: plugin.mapper.map.read
      risk: low
      description: "Read the occupancy maps this plugin publishes."
  contributes:
    shared_topics:
      - topic: plugin.mapper.pose
        subscribe_capability: telemetry.read
      - topic: plugin.mapper.occupancy
        subscribe_capability: plugin.mapper.map.read

shared_topics[].topic must be plugin.<leaf>.<name> over [a-z0-9._-], at most 128 characters, each listed once. The owner may event.publish it. Two installed plugins cannot claim the same namespace.
shared_topics[].subscribe_capability is what a subscriber needs on top of event.subscribe: a catalog capability, or one this plugin declares.
declared_capabilities[] entries take an id of the form plugin.<leaf>.<name>, a risk (low, medium, high or critical) and a description. Another plugin requests one like any catalog capability, and the install dialog shows it with the declared risk and description.

`agent.mavlink_components`

Each entry registers a MAVLink component so the router claims its id and answers component-info on the plugin’s behalf.

mavlink_components:
  - component_id: 100        # 0 to 255
    component_kind: camera   # camera | gimbal | payload | peripheral | generic | vio
    sub_id: 1                # optional, 0 to 255

Permission shape

A permission entry is either a bare string (which means required) or an object with id, required, and an optional degraded_behavior:

permissions:
  - id: mavlink.read                 # required (bare string also works: "mavlink.read")
  - id: hardware.i2c
    required: false                  # optional; the plugin degrades gracefully without it
    degraded_behavior: "Falls back to MAVLink-only telemetry"

Unknown permission ids load with a warning rather than a hard failure, so an experimental manifest still parses. See the Permissions reference.

Schema-2 agent fields

contains_vendor_binary, vendor_attribution, subprocess_spawn, and per_drone_config are schema-2 fields. A schema_version: 1 manifest gets the defaults.

per_drone_config: true runs one process per connected drone, each with its own ctx.agent_id and config at /var/ados/plugin-data/<plugin_id>/config/<agent_id>.yaml.
subprocess_spawn is an allowlist of binary basenames the plugin may exec. The plugin host rejects any spawn whose basename is not on the list, and the manifest validator requires the process.spawn permission whenever the list is non-empty.
contains_vendor_binary plus vendor_attribution travel together: the flag must be set when (and only when) at least one attribution record is present. Each vendor_attribution entry takes license (required) plus optional name, source_url, source_offer_url, upstream_repo, upstream_version, commit_sha, and notice. See Vendor binaries.

agent:
  runtime: rust
  entrypoint: "bin/example-detector"
  isolation: subprocess
  per_drone_config: true
  contains_vendor_binary: true
  vendor_attribution:
    - name: "example-upstream"
      license: "GPL-3.0-only"
      source_url: "https://github.com/example-oem/example-upstream"
      upstream_version: "v2.7"
      notice: "Used by the detector mode."
  permissions:
    - id: vision.frame.read
    - id: process.spawn
  subprocess_spawn:
    - ados_example_shim

Schema-3 fields: MCP tools, resources and prompts

Schema 3 adds three contribution lists, on agent.contributes and on gcs.contributes. They are what makes a plugin reachable by an AI agent through the MCP surface. A schema-2 manifest with no tools block loads exactly as before, so the platform stays inert for every existing plugin. Exposure requires the mcp.expose capability. Without it the lists parse and nothing is registered.

agent:
  permissions:
    - id: mcp.expose
  contributes:
    tools:
      - name: "example_read_state"
        description: "Read the current detector read-back."
        safety_class: read
        inputSchema:
          type: object
          properties: {}
      - name: "example_stop"
        description: "Stop the behaviour."
        safety_class: safe_write
        inputSchema:
          type: object
          properties: {}
    resources: []
    prompts: []

The entries are free-form maps and additive. The agent reads name, inputSchema and safety_class to build the tool registry and to route a host-to-plugin tool.invoke; it does not interpret the rest of the body. Be conservative with what you expose: a tool that commands the aircraft should be the operator’s decision, not an assistant’s, so first-party plugins expose a stop tool and no start tool. See MCP server for the scopes an assistant’s token carries and how they gate a tool call.

`gcs`

gcs:
  entrypoint: "gcs/plugin.bundle.js"
  isolation: "iframe"            # iframe (default) or inline (first-party only)
  permissions:
    - id: ui.slot.fc-tab
    - id: ui.slot.notification-channel
    - id: telemetry.subscribe.battery
  contributes:
    panels:
      - id: power-tab
        slot: fc.tab
        title: "Power"
        icon: "zap"
        order: 30
    notifications:
      - id: power-alert
        title: "Power alert"
  locales:
    - "en"

Field	Notes
`entrypoint`	The built bundle inside the archive. Required only when the half contributes `panels`, `tabs`, `agent_pages` or `node_surfaces`; a parameters- or skills-only half needs no bundle.
`isolation`	`iframe` (default) or `inline`. See below.
`permissions`	GCS capability requests, same shape as the agent half. Mounting in a slot requires the matching `ui.slot.*` permission.
`contributes`	What the half adds to Mission Control. Every key, its fields and its slot are on Contribution points. Keys are snake_case (`mission_templates`, `map_overlays`, `target_actions`); Mission Control also reads the camelCase spelling, but the agent’s validator rejects it.
`locales`	Locale codes the half ships under `locales/<code>.json`. A sibling of `contributes`. The agent serves an installed bundle at `GET /api/plugins/{plugin_id}/locales/{lang}`.

`gcs.isolation`

Value	Who may use it	How the half runs
`iframe`	Everyone (default)	A sandboxed iframe with no same-origin access, talking to Mission Control over the postMessage bridge.
`inline`	First-party signers only	An ES module Mission Control imports into its own page. The agent refuses the install from any other signer, and Mission Control verifies the module before loading it.

An inline module exports mount(root, host) and returns a disposer. The types are in @altnautica/plugin-sdk/inline; the host passes its own React, and the inlineSharedExternals() esbuild plugin from @altnautica/plugin-sdk/esbuild points the module’s react, react-dom/client and react/jsx-runtime imports at it. The host gives the module the same capability-gated context an iframe half gets, plus agent.fetch and agent.websocket against the plugin’s own HTTP passthrough, assetUrl for files in gcs/, the plugin’s cloud records, and navigation between its pages. Before importing, Mission Control fetches the node’s GET /api/plugins/<id>/attestation and GET /api/plugins/<id>/manifest and loads the module only when all of these hold: the signature verifies over the attested file list, the signer is an enrolled first-party key, the manifest’s hash matches its attested digest and it declares isolation: inline, and the module’s hash matches the digest listed for gcs.entrypoint. A module that fails any check shows an error card; it never falls back to an iframe. An inline half loads from the node over the LAN or the relay proxy, not from a cloud-stored bundle.

All fields

The table below is generated from the strict schema that ados plugin lint, sign and test enforce. The agent applies the same shape rules at install: a key that is not in this table, in any block, refuses the manifest.

Field	Type	Required	Default	Description
`agent.binaries`	object	No	n/a	Binaries
`agent.contains_vendor_binary`	boolean	No	`false`	Contains Vendor Binary
`agent.contributes.drivers`	array	No	n/a	Drivers
`agent.contributes.prompts`	array	No	n/a	Prompts
`agent.contributes.resources`	array	No	n/a	Resources
`agent.contributes.services`	array	No	n/a	Services
`agent.contributes.services[].command`	string	Yes	n/a	Command
`agent.contributes.services[].listen_ports`	array	No	n/a	Listen Ports
`agent.contributes.services[].name`	string	Yes	n/a	Name
`agent.contributes.services[].profiles`	array\|null	No	n/a	Profiles
`agent.contributes.services[].ready_check`	string\|null	No	n/a	Ready Check
`agent.contributes.services[].restart`	string	No	`"on-failure"`	Restart One of: `"always"`, `"on-failure"`, `"no"`.
`agent.contributes.services[].slice`	string	No	`"ados-plugins.slice"`	Slice
`agent.contributes.shared_topics`	array	No	n/a	Shared Topics
`agent.contributes.shared_topics[].subscribe_capability`	string	Yes	n/a	Subscribe Capability
`agent.contributes.shared_topics[].topic`	string	Yes	n/a	Topic
`agent.contributes.tools`	array	No	n/a	Tools
`agent.contributes.vision.behaviors`	array	No	n/a	Behaviors
`agent.contributes.vision.detectors`	array	No	n/a	Detectors
`agent.contributes.vision.models`	array	No	n/a	Models
`agent.declared_capabilities`	array	No	n/a	Declared Capabilities
`agent.declared_capabilities[].description`	string	No	`""`	Description
`agent.declared_capabilities[].id`	string	Yes	n/a	Id
`agent.declared_capabilities[].risk`	string	Yes	n/a	Risk One of: `"low"`, `"medium"`, `"high"`, `"critical"`.
`agent.entrypoint`	string	Yes	n/a	Entrypoint
`agent.http`	boolean	No	`false`	Http
`agent.isolation`	string	No	`"subprocess"`	Isolation One of: `"subprocess"`, `"inprocess"`.
`agent.mavlink_components`	array	No	n/a	Mavlink Components
`agent.mavlink_components[].component_id`	integer	Yes	n/a	Component Id
`agent.mavlink_components[].component_kind`	string	Yes	n/a	Component Kind One of: `"camera"`, `"gimbal"`, `"payload"`, `"peripheral"`, `"generic"`, `"vio"`.
`agent.mavlink_components[].sub_id`	integer\|null	No	n/a	Sub Id
`agent.payloads`	array	No	n/a	Payloads
`agent.payloads[].arch_os`	string\|null	No	n/a	Arch Os
`agent.payloads[].path`	string	Yes	n/a	Path
`agent.payloads[].profiles`	array\|null	No	n/a	Profiles
`agent.payloads[].sha256`	string	Yes	n/a	Sha256
`agent.payloads[].size_bytes`	integer	Yes	n/a	Size Bytes
`agent.payloads[].source`	string	Yes	n/a	Source
`agent.per_drone_config`	boolean	No	`false`	Per Drone Config
`agent.permissions`	array	No	n/a	Permissions
`agent.permissions[].degraded_behavior`	string\|null	No	n/a	Degraded Behavior
`agent.permissions[].id`	string	Yes	n/a	Id
`agent.permissions[].required`	boolean	No	`true`	Required
`agent.resources.class`	string	No	`"standard"`	Class One of: `"standard"`, `"heavy"`.
`agent.resources.max_cpu_percent`	integer	No	`25`	Max Cpu Percent
`agent.resources.max_pids`	integer	No	`12`	Max Pids
`agent.resources.max_ram_mb`	integer	No	`96`	Max Ram Mb
`agent.runtime`	string	No	`"python"`	Runtime One of: `"python"`, `"rust"`.
`agent.subprocess_spawn`	array\|null	No	n/a	Subprocess Spawn
`agent.target_profiles`	array	No	n/a	Target Profiles
`agent.test_fixtures`	object	No	n/a	Test Fixtures
`agent.vendor_attribution`	array	No	n/a	Vendor Attribution
`agent.vendor_attribution[].commit_sha`	string\|null	No	n/a	Commit Sha
`agent.vendor_attribution[].license`	string	Yes	n/a	License
`agent.vendor_attribution[].name`	string\|null	No	n/a	Name
`agent.vendor_attribution[].notice`	string\|null	No	n/a	Notice
`agent.vendor_attribution[].source_offer_url`	string\|null	No	n/a	Source Offer Url
`agent.vendor_attribution[].source_url`	string\|null	No	n/a	Source Url
`agent.vendor_attribution[].upstream_repo`	string\|null	No	n/a	Upstream Repo
`agent.vendor_attribution[].upstream_version`	string\|null	No	n/a	Upstream Version
`author`	string	No	`""`	Author
`compatibility.ados_version`	string	Yes	n/a	Ados Version
`compatibility.gcs_version`	string\|null	No	n/a	Gcs Version
`compatibility.min_tier`	integer\|null	No	n/a	Min Tier
`compatibility.supported_boards`	array	No	n/a	Supported Boards
`description`	string	No	`""`	Description
`description_long`	string\|null	No	n/a	Description Long
`documentation_url`	string\|null	No	n/a	Documentation Url
`extra`	object	No	n/a	Extra
`features`	array	No	n/a	Features
`gcs.contributes.agent_pages`	array	No	n/a	Agent Pages
`gcs.contributes.agent_pages[].after`	string\|null	No	n/a	After
`gcs.contributes.agent_pages[].icon`	string\|null	No	n/a	Icon
`gcs.contributes.agent_pages[].id`	string	Yes	n/a	Id
`gcs.contributes.agent_pages[].order`	integer\|null	No	n/a	Order
`gcs.contributes.agent_pages[].profile`	array\|null	No	n/a	Profile
`gcs.contributes.agent_pages[].section`	string\|null	No	n/a	Section
`gcs.contributes.agent_pages[].setup_for`	string\|null	No	n/a	Setup For
`gcs.contributes.agent_pages[].title`	string	Yes	n/a	Title
`gcs.contributes.map_overlays`	array	No	n/a	Map Overlays
`gcs.contributes.mission_templates`	array	No	n/a	Mission Templates
`gcs.contributes.models`	array	No	n/a	Models
`gcs.contributes.node_surfaces`	array	No	n/a	Node Surfaces
`gcs.contributes.node_surfaces[].group`	string\|null	No	n/a	Group One of: `"status"`, `"vehicle"`, `"link"`, `"device"`, `"compute"`.
`gcs.contributes.node_surfaces[].id`	string	Yes	n/a	Id
`gcs.contributes.node_surfaces[].order`	integer\|null	No	n/a	Order
`gcs.contributes.node_surfaces[].profile`	array	Yes	n/a	Profile
`gcs.contributes.node_surfaces[].title`	string	Yes	n/a	Title
`gcs.contributes.notifications`	array	No	n/a	Notifications
`gcs.contributes.overlays`	array	No	n/a	Overlays
`gcs.contributes.panels`	array	No	n/a	Panels
`gcs.contributes.parameters`	array	No	n/a	Parameters
`gcs.contributes.prompts`	array	No	n/a	Prompts
`gcs.contributes.resources`	array	No	n/a	Resources
`gcs.contributes.settings`	array	No	n/a	Settings
`gcs.contributes.skills`	array	No	n/a	Skills
`gcs.contributes.smart_functions`	array	No	n/a	Smart Functions
`gcs.contributes.tabs`	array	No	n/a	Tabs
`gcs.contributes.target_actions`	array	No	n/a	Target Actions
`gcs.contributes.tools`	array	No	n/a	Tools
`gcs.entrypoint`	string\|null	No	n/a	Entrypoint
`gcs.isolation`	string	No	`"iframe"`	Isolation One of: `"iframe"`, `"inline"`.
`gcs.locales`	array	No	n/a	Locales
`gcs.permissions`	array	No	n/a	Permissions
`gcs.permissions[].degraded_behavior`	string\|null	No	n/a	Degraded Behavior
`gcs.permissions[].id`	string	Yes	n/a	Id
`gcs.permissions[].required`	boolean	No	`true`	Required
`hardware_requirements.boards`	array	No	n/a	Boards
`hardware_requirements.cameras`	string\|null	No	n/a	Cameras
`hardware_requirements.fc_firmware`	string\|null	No	n/a	Fc Firmware
`hardware_requirements.optional`	array	No	n/a	Optional
`homepage`	string\|null	No	n/a	Homepage
`id`	string	Yes	n/a	Id
`license`	string	No	`""`	License
`name`	string	Yes	n/a	Name
`required_fc_parameters.ardupilot`	array	No	n/a	Ardupilot
`required_fc_parameters.ardupilot[].note`	string\|null	No	n/a	Note
`required_fc_parameters.ardupilot[].param`	string	Yes	n/a	Param
`required_fc_parameters.ardupilot[].value`	string\|number\|integer\|null	No	n/a	Value
`required_fc_parameters.inav`	array	No	n/a	Inav
`required_fc_parameters.inav[].note`	string\|null	No	n/a	Note
`required_fc_parameters.inav[].param`	string	Yes	n/a	Param
`required_fc_parameters.inav[].value`	string\|number\|integer\|null	No	n/a	Value
`required_fc_parameters.px4`	array	No	n/a	Px4
`required_fc_parameters.px4[].note`	string\|null	No	n/a	Note
`required_fc_parameters.px4[].param`	string	Yes	n/a	Param
`required_fc_parameters.px4[].value`	string\|number\|integer\|null	No	n/a	Value
`resource_impact.cpu_percent_peak`	number\|null	No	n/a	Cpu Percent Peak
`resource_impact.output_rate_hz`	number\|null	No	n/a	Output Rate Hz
`resource_impact.pids`	integer\|null	No	n/a	Pids
`resource_impact.ram_mb`	number\|null	No	n/a	Ram Mb
`resource_impact.startup_time_seconds`	number\|null	No	n/a	Startup Time Seconds
`risk`	string	No	`"medium"`	Risk One of: `"low"`, `"medium"`, `"high"`, `"critical"`.
`schema_version`	integer	No	`1`	Schema Version
`screenshots`	array	No	n/a	Screenshots
`screenshots[].caption`	string\|null	No	n/a	Caption
`screenshots[].url`	string	Yes	n/a	Url
`telemetry_fields`	array	No	n/a	Telemetry Fields
`version`	string	Yes	n/a	Version

Signing and the archive

The .adosplug archive is a zip. There is no per-asset hash list in the manifest and no signing: block. Instead the archive carries a separate top-level SIGNATURE file with two lines: the signer key id, then the base64 Ed25519 signature over a canonical payload hash (the SHA-256 of the sorted <path>\n<sha256-hex>\n lines for every entry except SIGNATURE). Because the hash covers every entry, any tampering after signing fails verification. Archives are size-bounded (50 MB per archive, 25 MB per entry) and reject path-traversal entries (.., absolute paths, symlinks). Payloads do not count toward these caps. A manifest that fails validation raises a manifest error; a signature from an unknown or revoked signer is rejected (see Signing keys). At install the agent writes an attestation beside the unpacked plugin: the archive’s SIGNATURE text and the sha256 of every attested file, payloads marked. GET /api/plugins/<id>/attestation serves it.

Next steps

Contribution points

Every contributes key and the slot it mounts in.

Permissions

The capabilities a manifest can request.

Lifecycle

What happens after install.

Signing keys

Sign the archive the manifest ships in.

Start here

Tutorials

Reference

SDKs

Deep dives

Test and distribute

File location

Top-level shape

`compatibility`

`agent`

Agent field reference

`agent.resources`

Per-architecture binaries

Install-time payloads

Plugin HTTP

Services

Shared topics and declared capabilities

`agent.mavlink_components`

Permission shape

Schema-2 agent fields

Schema-3 fields: MCP tools, resources and prompts

`gcs`

`gcs.isolation`

All fields

Signing and the archive

Next steps

Contribution points

Permissions

Lifecycle

Signing keys

​File location

​Top-level shape

​compatibility

​agent

​Agent field reference

​agent.resources

​Per-architecture binaries

​Install-time payloads

​Plugin HTTP

​Services

​Shared topics and declared capabilities

​agent.mavlink_components

​Permission shape

​Schema-2 agent fields

​Schema-3 fields: MCP tools, resources and prompts

​gcs

​gcs.isolation

​All fields

​Signing and the archive

​Next steps

Contribution points

Permissions

Lifecycle

Signing keys

File location

Top-level shape

`compatibility`

`agent`

Agent field reference

`agent.resources`

Per-architecture binaries

Install-time payloads

Plugin HTTP

Services

Shared topics and declared capabilities

`agent.mavlink_components`

Permission shape

Schema-2 agent fields

Schema-3 fields: MCP tools, resources and prompts

`gcs`

`gcs.isolation`

All fields

Signing and the archive

Next steps