Files
hermes-agent/website/docs/developer-guide/plugins/application-declarations.md
Siddharth Balyan 4094ab610d hermes_platform.resolver: locate/inspect/probe tiers, AppResolver, gh lookup migrated (NS-921) (#118065)
* feat(platform): resolver core with locate/inspect/probe tiers and ordered candidates

Every resource lookup needs one result shape and one cost contract. `locate` reads
metadata only, `inspect` may open files and call OS APIs in-process, `probe` is fresh
and the only tier that may spawn or connect. `Resolution.candidates` keeps probe order
so fan-out consumers can try every present binary.
Linear NS-921.

* feat(platform): AppResolver over AppDef with plist, PE, registry, and server.json sources

Desktop apps need presence, version, and liveness as separate observations. The runtime
file's bearer token is parsed, used for one request, and discarded inside the probe;
no public type carries it. Endpoints are accepted only when loopback with a numeric port.

* refactor(copilot): gh candidates through locate_command and the Homebrew table

First consumer of the resolver. The gh token probe still tries every present binary in
order; the allowlist loses its two copilot_auth rows.

* feat(platform): availability() over an application declaration

locate() + inspect() only, never probes; the fail-closed _version in
app.py treats a vendor's plist/PE/registry entry as untrusted input.
Salvaged from PR #118122; reads any object with requires_app,
min_version, app_for(os) — nothing here imports the MCP catalog.

* feat(platform): application declarations parsed into AppDef per OS

The parser slice of PR #118122's catalog manifest, re-homed as a
catalog-free module: whoever owns an MCP server declares the app it
fronts per OS and what it needs, and registers it here. Stdlib +
hermes_platform.resolver only. register/lookup/clear are the one seam
the MCP check_fn and the skill gate both read.

* feat(mcp): check_fn honours a registered application declaration

_make_check_fn ANDs the declared app's availability into the
connection-alive check; with nothing registered for the server the
behaviour is the pre-PR3 connection check. Provenance is explicit
registration, not endpoint matching. Returns a plain bool: the registry
caches bool(fn()).

* feat(skills): requires_apps gate through registered declarations

Offer-time filter beside environments:; names resolve through
hermes_platform.declaration, an unknown name hides the skill (fail
closed). The disk snapshot carries requires_apps and the fast path
re-evaluates it (snapshot version bumped to 3): app presence is a host
fact that changes without SKILL.md changing.

* docs: application declarations page

The plugin-facing schema reference: app: and requires: blocks,
availability() states, and the two gates that read the registry.
Registered under Extending > Plugins in the docs sidebar.

* test(platform): declaration parser, availability, gates

The PR3 app-block tests re-homed off the catalog: fixtures are dicts
passed to parse_declaration, the check_fn gate keys on explicit
registration (not endpoint matching), and the import-hygiene probe now
covers hermes_platform.declaration and resolver.availability.
2026-09-22 17:08:30 +05:30

5.2 KiB

Application declarations

A plugin whose MCP server fronts a desktop application declares which application that is and what the server needs of it. The core evaluates the declaration on the host and gates the server's tools, and any skill that names the application, on the answer. The parser imports only the standard library and hermes_platform.

The vocabulary lives in hermes_platform/declaration.py. A declaration is data plus policy, parsed from plain mappings (already-decoded YAML, JSON, a dict literal — the parser never touches a file):

from hermes_platform import declaration

decl = declaration.parse_declaration(
    "my-server",
    raw_app={"linux": {"presence": "executable", "location": "/opt/my-app/server"}},
    raw_requires={"app": True},
    where="my-plugin/plugin.yaml",   # human label used in error messages
)
declaration.register("my-server", decl)

register(server_name, decl) stores one declaration under the configured server name in a process-local registry. Loader integration is separate work; core does not read plugin YAML automatically.

An unregistered MCP server keeps its connection-only check. A skill that explicitly names an unregistered server is hidden. clear() removes every registration and is not a per-plugin unload operation. Registrations are process-wide, not profile-scoped.

app — how to find the application on each OS

app:
  win32:
    presence: executable
    location: "%ProgramFiles%/Vendor/Vendor App/McpServer/Server.exe"
    version: { kind: uninstall_registry, display_name_prefix: "Vendor App" }
    liveness:
      kind: server_json
      path: "%LOCALAPPDATA%/Vendor/Vendor App/McpServer/server.json"
      pid_key: pid
      url_key: http
      token_key: token
      endpoint_path: /mcp
  darwin:
    presence: bundle
    location: /Applications/Vendor.app
    version: { kind: plist }
field type rule maps to AppDef
<os> win32 | darwin | linux at least one; unknown key is an error AppDef.os_family
presence executable | bundle required per OS .presence
location str required; drive-rooted (C:\\...) on Windows, or starting with ~ / %VAR% / $VAR; UNC paths are rejected so a presence check never touches the network; no .. segment or URL scheme; expansion at lookup .location
version.kind pe_resource | plist | uninstall_registry | none default none; pe_resource/uninstall_registry only under win32, plist only under darwin .version_kind
version.display_name_prefix str required when uninstall_registry .version_arg
liveness.kind server_json | none default none .liveness_kind
liveness.path str required when server_json .liveness_path
liveness.pid_key / url_key / token_key str defaults pid / http / token .liveness_*_key
liveness.endpoint_path str default /mcp; the path used for initialize, never the one in the file .endpoint_path

When requires.app is true, an OS missing from app: gives unsupported_os.

requires — what the server needs before it is offered

requires:
  app: true
  min_version: "2.3.0"
field type rule
app bool when true, app: must exist and the server is gated on presence
min_version str requires app: true; dotted numeric; every applicable app.<os> must declare a real version.kind; compared numerically per segment, non-numeric characters in a segment are dropped (2.3.0.12594 ≥ 2.3.0; prerelease suffixes are not ordered)

requires.app: true with no app: block is a DeclarationError.

Availability: the one evaluation every reader uses

hermes_platform/resolver/availability.py::availability(decl) -> Availability

Availability(
  state:   available | installed_not_running | missing_app | version_too_old
         | unsupported_os | no_requirements,
  version: str | None,       # inspected, when present
  path:    str | None,       # where the app was found or looked for
  min_version: str | None,   # from requires
)
  • no_requirements: no requires.app; the application gate passes, but the connection check still applies.
  • unsupported_os: requires.app and no app.<this os> block. Zero I/O.
  • missing_app: locate found nothing at location.
  • version_too_old: the version is below the minimum or cannot be read.
  • available: present, version acceptable or not required.
  • installed_not_running: reserved vocabulary; this evaluator never produces it.

Evaluation uses locate and optional version inspection. It never probes a server, launches an application, or connects. The tool registry retains its existing availability cache.

The two gates

  • MCP check_fn (tools/mcp_tool_handlers.py::_make_check_fn): connection alive AND, when a declaration with requires.app is registered for the server, availability(decl).offerable. Returns a plain bool because the registry caches bool(fn()).
  • Skill requires_apps: frontmatter (agent/skill_utils.py::skill_matches_apps): each name resolves through declaration.lookup; an unknown name hides the skill (fail closed). Offer-time filter, like environments:.