airlock.yaml 5.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768
  1. name: airlock
  2. title: airlock
  3. repo: https://github.com/otsoa-dubief/airlock
  4. sha: 4d3919745b97cd21d1448c04fc776b40f4552aa3
  5. subdir: airlock
  6. version: "0.3.0"
  7. description: >-
  8. Guardrails that follow what a conversation has read. Once a session reads untrusted content (a web page, a
  9. browser snapshot, an MCP or third-party plugin's output, a customer's message), airlock seals it: messages to
  10. anyone but the owner, network writes, pushes and deploys, memory, skill and cron writes, browser input, URLs
  11. that could carry data out and code that reaches the network go through Hermes's own approval gate. Walls hold
  12. in every session: credential paths and secret files, the guard's own files and Hermes's config, shell startup
  13. files, other profiles, commands that switch approvals off. Shell commands are read the way the shell reads
  14. them, so a command that computes or hides what it runs (eval, base64 | sh, $G push, wildcards, write-then-run)
  15. is refused until written in clear. Subagents inherit the seal. A project's AGENTS.md, CLAUDE.md,
  16. .cursorrules or .hermes.md that Hermes loads at startup seals the session from its first turn until the owner
  17. has reviewed it (`hermes airlock trust`), and again when its content changes (a cloned repository, a pull). It also catches an injection by its signature:
  18. recognized secrets never leave in a call; a private marker in the agent's context locks the session if it shows
  19. up in a tool call; a send to an address the untrusted content named is blocked; repeated refusals lock the
  20. session; lookalike Unicode in commands is refused. A file behind a wall cannot leave as a message
  21. attachment, and attached files are checked for secrets. A call that names a cloud metadata service is
  22. refused. Plugin and MCP tools nobody admitted need approval. Observe mode, stop switch,
  23. `hermes airlock check|demo|log|trust`. On Windows, paths are read in every form Windows and Git Bash give them, and
  24. a path on another machine is refused without being opened. Tested on a corpus of 362 attacks and everyday
  25. commands, on Linux, macOS and Windows, and end to end in the official image.
  26. Disclosure — hooks only (pre_tool_call, post_tool_call, pre_llm_call, subagent_start, on_session_reset,
  27. post_approval_response), no tools. No network, no LLM call, runs no command. Reads the profile's config.yaml
  28. (home channels, approvals mode) and its own policy file (<HERMES_HOME>/airlock.yaml); lists directories to
  29. expand wildcards in commands it checks; reads the first 200 KB of each file a send_message attaches, locally, to
  30. look for secrets. On Windows, reads the machine's own name (no lookup), tests which drive letters exist, and
  31. imports tools.environments.local._find_bash to know Git Bash's root. On a session's first turn, imports
  32. agent.prompt_builder.discover_context_files and _project_context_suppressed and
  33. agent.runtime_cwd.resolve_context_cwd (guarded) to know which project context files Hermes loaded, and hashes
  34. them (sha256). Imports Hermes's attachment reader (gateway.platforms.base.BasePlatformAdapter.extract_media)
  35. to see exactly what a message would attach, with its own reader as a fallback.
  36. Writes under plugin-data/airlock: a journal of decisions, taints and
  37. approvals that includes tool arguments, truncated (journal.args: none leaves them out), the taint state, the
  38. stop switch and the context files the owner trusted (path and sha256). When nobody can approve (--yolo, /yolo, hermes -z, approvals.mode: off, cron, -q or webhook set to
  39. approve, a subagent under delegation.subagent_auto_approve) it blocks instead of letting Hermes auto-approve;
  40. to know it, it imports gateway.session_finite.unattended_turn and reads tools.approval (_yolo_active,
  41. _unattended_contexts, approval_context._get_approval_mode), each guarded, config.yaml as fallback (policy
  42. approvals_off: follow restores Hermes's behaviour). Install scan: caution,
  43. because the default policy and the shell reader name the patterns airlock guards against (startup files,
  44. crontab, credential commands, exfiltration shapes).
  45. maintainer: otsoa-dubief
  46. tier: community
  47. category: tools
  48. requires_hermes: ">=0.21.6"
  49. docs_url: https://github.com/otsoa-dubief/airlock#readme
  50. image: https://raw.githubusercontent.com/otsoa-dubief/airlock/4d3919745b97cd21d1448c04fc776b40f4552aa3/docs/images/social-preview.png
  51. screenshots:
  52. - https://raw.githubusercontent.com/otsoa-dubief/airlock/4d3919745b97cd21d1448c04fc776b40f4552aa3/docs/images/live-session.gif
  53. - https://raw.githubusercontent.com/otsoa-dubief/airlock/4d3919745b97cd21d1448c04fc776b40f4552aa3/docs/images/how-it-works.png
  54. - https://raw.githubusercontent.com/otsoa-dubief/airlock/4d3919745b97cd21d1448c04fc776b40f4552aa3/docs/images/check.png
  55. platforms: []
  56. known_issues:
  57. - "Built for in-process plugins (Hermes's default): under plugins.isolation: host it cannot tell third-party plugin tools from Hermes's own."
  58. capabilities:
  59. provides_tools: []
  60. provides_hooks:
  61. - pre_tool_call
  62. - post_tool_call
  63. - pre_llm_call
  64. - subagent_start
  65. - on_session_reset
  66. - post_approval_response
  67. provides_middleware: []
  68. requires_env: []