emisar
v0.50.0 open-sourceThe section your link pointed to isn't on emisar's page any more, so we've brought you to the top.
An MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. that lets AI tools securely connect to your infrastructure, write IaaS code, debug issues, and assist during incidents - without risking production stability. Built for security teams to approve and infrastructure teams to experience like magic.
emisar pack verify emisar pack diff emisar update emisar pack update --json EMISAR_GROUP=prod-eu EMISAR_RUNNER_ID=runner-42 ./emisar-runner gh attestation verify oci://ghcr.io/andrewdryga/emisar-runner:0.18.0 --owner andrewdryga install.sh --uninstall install.sh --reset-identity emisar doctor emisar state check-dispatch-log && echo "dispatch log OK" || exit 1 QUARANTINE_DISPATCH_LOG=1 ./install.sh
Summary
emisar is an open-source infrastructure-access gateway that gives MCP-capable AI agents a catalog of declared actions instead of a shell, with policy deciding what runs, what waits for human approval, and what is denied. It runs as a hosted control plane paired with a small outbound-only runner installed on your own Linux hosts via systemd, so nothing listens on the host and the agent never gets raw access; a free tier covers three runners and one user. It's aimed at platform and infrastructure teams building or operating AI agents for incident response and operational tasks, who need audited, reversible actions rather than open shell access. The catalog spans 91 packs and 1,386 actions across cloud, network, and container diagnostics. Records show a single maintainer but heavy, continuous activity — over 2,700 commits and 35 releases in the past year, most recently two weeks ago.
An MCP that lets AI tools securely connect to your infrastructure, write IaaS code, debug issues, and assist during incidents - without risking production stability. Built for security teams to approve and infrastructure teams to experience like magic.
How emisar helps
Which action did an agent actually run on a host, and who approved it?
every dispatch is journaled with the policy verdict, the approver, and the streamed output, so the audit trail shows the full chain from request to execution rather than just a shell history line
Which of my hosts are missing packs or running a degraded catalog?
the fleet view lists runners with named load failures and amber notices with the reason and remedy, instead of the action silently failing when dispatched
Did an agent's command get blocked, rate-limited, or refused, and why?
pre-run rejections are logged with bounded, allowlisted fields, so refused calls show up in operations instead of vanishing silently
Can I stage a multi-step operational task and freeze the plan before anything runs?
runbooks define typed inputs and sequential or parallel stages against selected runner groups behind a single pre-execution approval gate, with attempt and output history kept per step
Is a runner I'm talking to actually running the pack version I expect?
pack-trust conflicts name the specific runners that disagree about an action, and retention keeps versions a connected runner still advertises, so version mismatches surface instead of failing as a generic error
Languages
Features
66 capabilities across 4 capability groups · 1 backed by code, an API document or a real run
Built from emisar's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.
- emisar covers 1 of the 6 ai evaluation and governance capabilities we track.
What emisar offers you
- Web management console5
- Command-line interface4
- CI/CD pipeline integration3
- Multi-factor authentication3
- Role-based access control3
- MCP server2
- Single sign-on2
- Administrative audit log1
- Natural-language query1
- REST API1
No capabilities match.
+ OIDC SSO 1 feature Identity and access since 2026 ▸
+ OIDC and JWKS integration shipped OIDC discovery and JWKS refresh operate under a shared bounded address policy that validates responses and clears credentials when the issuer changes. 5 releases · first seen Jul 2026 ▸
Shared capability: OIDC SSO
release
- SSO groups now show role, runner, and pack access together, with in-place role editing and member filtering on the provider page. v0.47.0 · Sep 2026 · source · release history
- MFA, SSO, email, invitation, device-grant, session-revocation, and SCIM decisions are now rechecked within the transaction that commits the resulting authority. v0.42.0 · Aug 2026 · source · release history
- SSO group mappings now paginate in both directions. v0.41.0 · Aug 2026 · source · release history
- Adds OIDC discovery and JWKS refresh under a shared bounded address policy that rechecks the actual response received; changing an issuer clears credentials tied to the old one. v0.36.0 · Jul 2026 · source · release history
- Adds a unified bounded address policy covering OIDC discovery, JWKS refresh, and redirects that rechecks the response actually received; changing an issuer now clears credentials tied to the old one. v0.36.0 · Jul 2026 · source · release history
+ Multi-factor authentication 1 feature Identity and access since 2026 ▸
+ Session and authentication hardening shipped Production sessions require Secure cookies, SSO/MFA on every controller route, and a fresh step-up challenge before disabling two-factor authentication. 15 releases · 1 other source · first seen Jul 2026 ▸
Shared capability: Multi-factor authentication
Also counts toward: Multi-factor authentication, Single sign-on
release 15 total
- Reworks MFA setup and Profile security settings, including sign-out, enabled/disabled states, authenticator verification, and recovery-code flows. v0.52.0 · Oct 2026 · source · release history
- The read-only staff console now requires MFA proof tied to the current enrollment. v0.41.0 · Aug 2026 · source · release history
-
Action children now start with
no_new_privs, preventingexecveinside a pack from gaining setuid or file-capability privileges the runner does not already hold. v0.37.0 · Aug 2026 · source · release history - MCP bridge signing key now comes from a pinned credential directory instead of the environment. v0.37.0 · Aug 2026 · source · release history
- MCP bridge signing key is now sourced from a pinned credential directory instead of the environment. v0.37.0 · Aug 2026 · source · release history
- Runner tokens now carry a 90-day bounded lifetime and self-refresh two-thirds of the way through over the existing connection, with expired tokens refused at connect. v0.37.0 · Aug 2026 · source · release history
docs
- Authentication Single sign-on (SSO) Integrations Okta Microsoft Entra JumpCloud Keycloak Google Workspace docs update · Aug 2026 · source
+ AI input data redaction 1 feature AI evaluation and governance since 2026 ▸
+ Sensitive data redaction shipped Sensitive action arguments are redacted from local audit records and the portal, and Redis ACL password hashes are redacted from command output. 13 releases · first seen Jul 2026 ▸
Shared capability: AI input data redaction
release 13 total
- BunnyCDN pack 0.1.11 now rebuilds each Pull Zone edge rule from known fields and redacts header, cookie, query-string, and credential values; earlier versions are retired. v0.54.0 · Oct 2026 · source · release history
-
Consul 0.2.38omits SecretID values from token metadata; Runner masking recognizes the observed spellings. v0.53.0 · Oct 2026 · source · release history - Runner redaction now masks long private-key blocks and sensitive argument values cut by output limits, while default rules preserve public AWS access-key IDs and mask recognized secret-key and session-token fields. v0.46.0 · Sep 2026 · source · release history
- Control and bidirectional characters are rejected at ingest before they can reach an approval or audit surface. v0.44.0 · Sep 2026 · source · release history
- Adds redaction of secret-bearing reads at the source, covering Redis ACLs, pm2 environments, and secret-named variants. v0.44.0 · Sep 2026 · source · release history
- pfSense certificate reads no longer emit the certificate's private key. v0.39.0 · Aug 2026 · source · release history
+ MCP server 1 feature Interfaces and integrations since 2026 ▸
+ Hosted MCP server shipped A hosted MCP server published to the official MCP registry lets LLM agents invoke actions through a standard interface without additional setup. 21 releases · 1 other source · first seen Jul 2026 ▸
Shared capability: MCP server
Also counts toward: MCP server
release 21 total
-
Adds
cancel_runMCP tool so an agent can withdraw a run it started while waiting for approval.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ v0.50.0 · Sep 2026 · source · release history - MCP uninstall capability probes now run as the invoking user, without elevated privileges. v0.46.0 · Sep 2026 · source · release history
-
Adds
find_actionspagination by rank in the MCP bridge, so promoting a concept no longer loops or skips results. v0.44.0 · Sep 2026 · source · release history - Every MCP tool is now available as a bridge command, enabling scripts and clients without MCP support to invoke them directly. v0.42.0 · Aug 2026 · source · release history
- The MCP Bridge now owns client connect and disconnect lifecycle, drains runbook output automatically, and returns actionable validation errors. v0.42.0 · Aug 2026 · source · release history
- Backlogged run output now ships as one frame instead of one per line, and the connection lease renews at half its life instead of on every heartbeat. v0.37.0 · Aug 2026 · source · release history
docs
- MCP-based platform that gives AI agents a catalog of declared infrastructure actions with policy-controlled execution on Linux hosts.
+ Other / not yet classified 62 features Features we have not matched to a capability yet. A suggested match is marked. ▸
+ Runbooks verified A canonical JSON runbook definition is shared across the console, MCP, and execution pages, with a single approval gate that freezes the complete plan before any work begins. 27 releases · 3 other sources · first seen Jul 2026 ▸
release 27 total
- When an MCP action or runbook waits for approval, server instructions and every approval result now tell the agent to notify the user immediately with the exact approval link, fire once per request, continue independent work, and never treat a chat reply as approval.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ v0.54.0 · Oct 2026 · source · release history
- Console runbook starts retain the release and plan reviewed; changed plans require another review. v0.47.0 · Sep 2026 · source · release history
- Runbook cancellation now survives control-plane restarts, preserving cancellation state across service interruptions. v0.46.0 · Sep 2026 · source · release history
- Allows a requester to withdraw a run that is still waiting for approval. v0.44.0 · Sep 2026 · source · release history
- Owners and administrators gain an audited break-glass override for unreachable approval quorums. v0.42.0 · Aug 2026 · source · release history
- Runbook versioning now tracks published releases (e.g. Run v3) rather than counting every save, with a single in-flight draft per runbook instead of unbounded version rows. v0.39.0 · Aug 2026 · source · release history
command line
-
--gallery-only — enterprise-app: stop after the Create-your-own-application screenv0.49.0 · Sep 2026 -
--provisioning-only — provisioning: stop after the Provisioning bladev0.49.0 · Sep 2026 -
--mappings — provisioning: capture the attribute mapping and the opened externalId rowv0.49.0 · Sep 2026
+ Pack catalog expansion shipped Broadens available tool integrations, adding support for services like Artifactory, Databricks, and Sentry to the pack registry. 26 releases · first seen Aug 2026 ▸
release 26 total
-
PostgreSQL 0.2.21adds native VACUUM dead-item counters across versions, labeled checkpoint statistics, and a strict sequential-scan filter including indexless tables. v0.53.0 · Oct 2026 · source · release history -
ClickHouse 0.2.18adds a normalized structural read that omits literals and is not recreatable SQL, plus a full server-provided DDL read that requires approval under the default policy and warns about sensitive defaults, comments, and engine arguments. v0.53.0 · Oct 2026 · source · release history -
Cassandra 0.6.10adds client metadata and confines storage reads to configured roots with keyspace-escape rejection and bounded compaction history. v0.53.0 · Oct 2026 · source · release history -
GCP Storage 0.1.3distinguishes live and explicitly requested noncurrent object versions. v0.53.0 · Oct 2026 · source · release history -
Linux Core 0.5.3 / Debugging 0.3.4add peer counts and group protocol states with inline port-set membership resolution. v0.53.0 · Oct 2026 · source · release history -
Traefik 0.1.25adds a separate metrics entrypoint and complete bounded HTTP router/service inventories including summary and readiness joins. v0.53.0 · Oct 2026 · source · release history
+ Pack version lifecycle management shipped Retired pack versions are blocked from dispatching actions, requiring operators to upgrade to a supported version before runs can proceed. 13 releases · 1 other source · first seen Jul 2026 ▸
release 13 total
- BunnyCDN pack versions earlier than 0.1.11 are retired and no longer supported. v0.54.0 · Oct 2026 · source · release history
- Network/TLS versions below 0.3.1 are retired. v0.53.0 · Oct 2026 · source · release history
- Consul versions below 0.2.38, Cloudflare below 0.2.10, Cassandra below 0.6.10, and Grafana below 0.1.20 are retired and blocked by default unless explicitly overridden by an administrator. v0.53.0 · Oct 2026 · source · release history
- Symbolicator pack versions earlier than 0.2.6 are retired and cannot dispatch actions — upgrade to Symbolicator pack 0.2.6. v0.52.0 · Oct 2026 · source · release history
- Updates Symbolicator pack to 0.2.6; earlier versions are retired and can no longer dispatch actions. v0.52.0 · Oct 2026 · source · release history
- Retired versions that allowed actions to skip approval for the docker, mysql, nginx, nomad, pfsense, postgres, and victorialogs packs. v0.50.0 · Sep 2026 · source · release history
example
-
View pending changes in a pack without applying them.
$ emisar pack diffv0.42.0 · Aug 2026 · source
+ Role-aware console interface shipped Adapts navigation, actions, and filters to the member's role, immediately applying scope changes and surfacing permission states. 13 releases · first seen Jul 2026 ▸
Also counts toward: Role-based access control, Web management console
release 13 total
- Operational roles can inspect workspace-wide activity while actions remain limited by current runner and pack access. v0.47.0 · Sep 2026 · source · release history
- Scoped admins are blocked from delegating more reach than they hold or triggering account-wide pack cleanup. v0.41.0 · Aug 2026 · source · release history
- Scoped admins are blocked from delegating more reach than they hold or arming account-wide pack cleanup. v0.41.0 · Aug 2026 · source · release history
- Console navigation, actions, filters, and empty states now adapt to the member's role and access — billing managers no longer see a dead Dashboard link, and missing runner access is surfaced as a permission state. v0.41.0 · Aug 2026 · source · release history
- Restricted pack and action views now explain why results are limited. v0.41.0 · Aug 2026 · source · release history
- Billing managers now receive a finance-only console; operators can manage agents, approvals, and runbooks without gaining team or policy administration rights. v0.41.0 · Aug 2026 · source · release history
+ Signed and reproducible releases shipped Binary and container releases are immutable and reproducible, with signed tags, digest-pinned images, SLSA-3 provenance, SHA256SUMS, and SBOM attestations; unfixed HIGH/CRITICAL vulnerabilities block publication. 11 releases · 1 other source · first seen Jul 2026 ▸
release 11 total
- When GitHub CLI is unavailable for provenance verification, interactive installers prompt whether to continue and noninteractive installs emit a warning. v0.46.0 · Sep 2026 · source · release history
- Every runner and bridge binary now ships with signed checksum attestations and SLSA provenance for pre-install verification. v0.44.0 · Sep 2026 · source · release history
- Every Docker image CI builds or ships is pinned. v0.44.0 · Sep 2026 · source · release history
-
Publishes an official multi-architecture container image at
ghcr.io/andrewdryga/emisar-runnerwith build provenance and an SBOM. v0.37.0 · Aug 2026 · source · release history -
Official multi-architecture container image published at
ghcr.io/andrewdryga/emisar-runnerwith build provenance and an SBOM. v0.37.0 · Aug 2026 · source · release history -
Runner binary
runner-v0.11.0ships with SLSA-3 build provenance andSHA256SUMSpublished by its release workflow. v0.26.0 · Jul 2026 · source · release history
example
-
Verify the integrity and provenance of the official multi-arch runner container image before deploying it.
$ gh attestation verify oci://ghcr.io/andrewdryga/emisar-runner:0.18.0 --owner andrewdrygav0.37.0 · Aug 2026 · source
+ MCP run output and status reporting shipped MCP run summaries surface only meaningful fields, include bounded failure messages and policy denial reasons, and support incremental output streaming via a cursor-based call. 11 releases · first seen Jul 2026 ▸
Also counts toward: Natural-language query
release 11 total
-
Bounds the
reviewreceipt to 64 KiB in JSON-encoded bytes after masking, so a justification quoting a secret cannot push await_for_runpage past its size budget. v0.49.0 · Sep 2026 · source · release history -
Adds a
reviewobject to run summaries in the MCP bridge for gated approvals v0.49.0 · Sep 2026 · source · release history -
New
wait_for_runMCP call accepts an output cursor and returns the next cursor, enabling agents to stream run output incrementally as it arrives rather than polling. v0.34.0 · Jul 2026 · source · release history - Enables actions to opt into typed JSON results, dispatched against the pinned trusted descriptor. v0.32.0 · Jul 2026 · source · release history
- Actions can opt into typed JSON results dispatched against a pinned trusted descriptor. v0.32.0 · Jul 2026 · source · release history
-
Adds paginated MCP reads that return a copy-ready
nextcall (echoing one object) instead of a bare cursor, so agents can continue pagination without parsing a raw cursor value. v0.32.0 · Jul 2026 · source · release history
+ Infrastructure diagnostics shipped An expanding catalog of infrastructure diagnostic checks is available to operators for investigating platform health. 9 releases · first seen Jul 2026 ▸
release 9 total
-
Run DNS and HTTPS checks from inside a selected Nomad task using the new
nomad.alloc_exec_node_dnsandnomad.alloc_exec_node_httpsprobes in Nomad pack 0.4.17 — probes use fixed Node.js checks with bounded output and normal TLS verification.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ v0.56.0 · Nov 2026 · source · release history -
Network/TLS 0.3.2adds IPv6 inspection, boundedhostname:port:IPoverrides for HTTP probes and headers that preserve Host, SNI, and certificate verification, legacy TLS probes, bounded WHOIS-to-RDAP fallback, and now has certificate inspection emit only the presented certificate chain. v0.53.0 · Oct 2026 · source · release history - Adds a separate native Linux amd64 diagnostics artifact that carries its complete runtime closure and can be extracted by the host without starting a container.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ v0.53.0 · Oct 2026 · source · release history
- Metrics, logs, and process diagnostics now carry explicit cost and disclosure bounds; the Redis Sentinel down-state probe is structurally read-only. v0.42.0 · Aug 2026 · source · release history
- pfSense gains resolver, NTP, and WireGuard peer reads (secrets excluded), plus a DHCP reservation action staged for operator approval. v0.39.0 · Aug 2026 · source · release history
- Expands the infrastructure diagnostics catalog with additional checks. runner-v0.16.0 · Jul 2026 · source · release history
+ Installer integrity verification shipped The install script checks dispatch state against the staged binary before touching a running service and can quarantine an unreadable dispatch log automatically. 7 releases · 2 other sources · first seen Jul 2026 ▸
Also counts toward: Command-line interface
release 7 total
- Pre-validates config against the staged binary before installing the runner v0.49.0 · Sep 2026 · source · release history
- Installers now handle IPv6 loopback origins, per-copy MCP upgrades, and retained configuration reporting. v0.46.0 · Sep 2026 · source · release history
- Both installers now fail closed on a tampered download checksum. v0.44.0 · Sep 2026 · source · release history
-
Adds
--purgeflag toinstall.shto remove all retained files including those preserved by--uninstall. v0.33.0 · Jul 2026 · source · release history -
Adds
--purgeflag toinstall.shthat extends--uninstallby also removing the retained configuration, evidence, and log files. v0.33.0 · Jul 2026 · source · release history -
install.shnow verifies dispatch state with the staged binary before touching a running service, aborting with remediation options on failure. v0.28.0 · Jul 2026 · source · release history
example
-
Verify the integrity of a pack installation locally before deploying.
$ emisar pack verifyv0.42.0 · Aug 2026 · source -
Verify the integrity and provenance of a downloaded runner binary and the official container image before deploying.
$ gh attestation verify emisar-0.18.0-linux-amd64.tar.gz --owner andrewdryga sha256sum -c SHA256SUMS gh attestation verify oci://ghcr.io/andrewdryga/emisar-runner:0.18.0 --owner andrewdrygav0.37.0 · Aug 2026 · source
+ Workspace-scoped authentication shipped Authenticates members through workspace-specific email, MFA, and SSO settings, replacing personal login flows, and records refused SSO sign-ins in the workspace audit trail. 8 releases · first seen Aug 2026 ▸
Also counts toward: Multi-factor authentication, Single sign-on
release 8 total
- Adds refused SSO sign-ins to the workspace audit trail. v0.51.0 · Oct 2026 · source · release history
- Adds workspace-level sign-in, replacing personal logins, with per-workspace email, MFA, and SSO enforcement. v0.51.0 · Oct 2026 · source · release history
- Workspace sign-in replaces personal logins — members now authenticate through workspace-specific email, MFA, and SSO settings; any setup relying on personal login flows will break. v0.51.0 · Oct 2026 · source · release history
- Workspace members now own their identities, allowing SSO, SCIM, or invitations to create members scoped only to that workspace rather than a global personal login v0.50.0 · Sep 2026 · source · release history
- Shared reads no longer authorize execution, cancellation, approval, or access changes. v0.47.0 · Sep 2026 · source · release history
- Owner access normalization is audited and does not restore narrower grants on rollback. v0.47.0 · Sep 2026 · source · release history
+ Audit log attribution shipped Per-action account membership resolution ensures run and approval attribution is correctly scoped, preventing cross-workspace profile leakage in the audit log. 8 releases · first seen Jul 2026 ▸
release 8 total
-
SIEM/audit consumers: the
actor_kindfield on people-generated events changes from"user"to"membership", and the actor id is now the workspace member's id — queries or alerts that matchactor_kind: "user"or join on the old user id will need updating. v0.50.0 · Sep 2026 · source · release history -
Events generated by people now carry
actor_kind: "membership"and the member's id in SIEM-bound audit output; older rows retainactor_kind: "user". v0.50.0 · Sep 2026 · source · release history - Audit CSV exports now stream instead of materializing the entire export, enabling large audit log downloads without memory pressure. v0.46.0 · Sep 2026 · source · release history
- Adds a one-time audit CSV export bounded by size, replacing an unbounded export that could mis-signal a drained queue. v0.44.0 · Sep 2026 · source · release history
- Each execution snapshots the definition and release number it dispatched, making audit history immutable to later edits, publishes, or deletes. v0.39.0 · Aug 2026 · source · release history
- Each execution snapshots the definition it dispatched, making the audit record immutable to later edits, publishes, or deletes. v0.39.0 · Aug 2026 · source · release history
+ Risk-level classification for pack actions shipped Cloud-init, cloud-config, pm2 env, nginx, and caddy config dumps are classified as medium risk, removing them from the ungated low-read path. 8 releases · first seen Jul 2026 ▸
release 8 total
-
Adds
member_invitein the admin pack to thehighrisk tier, matching every other membership-change action. v0.49.0 · Sep 2026 · source · release history - Reads that can return credentials are now approval-gated; sensitive run values are masked in a single pass so one match cannot rewrite another's marker. v0.37.0 · Aug 2026 · source · release history
-
Every pack's
curlis confined to an explicit protocol with globbing off, preventing URLs arriving in API responses from expanding into extra transfers or exfiltrating credentials. v0.37.0 · Aug 2026 · source · release history -
Adds a real-time advisory warning when a policy override glob cannot match any action ID (e.g. regex-style patterns like
cassandra\.drop_*), flagging deny rules that appear protective but cover nothing — warning is non-blocking to allow rules targeting not-yet-installed packs. v0.38.0 · Aug 2026 · source · release history - Each pack's structured output is bounded to fit the runner's cap at its advertised worst case; jq filters are restricted to core builtins for compatibility with minimal hosts. v0.37.0 · Aug 2026 · source · release history
-
Every pack's
curlis confined to an explicit protocol with globbing disabled, blocking URL expansion or credential exfiltration from API-supplied URLs. v0.37.0 · Aug 2026 · source · release history
+ Run recovery after runner reconnect shipped The control plane recovers runs that were in flight when a runner disconnects and reconnects, rather than leaving them stranded. 8 releases · first seen Jul 2026 ▸
release 8 total
- Approval recovery distinguishes catalog failures, unavailable actions, and changed contracts, preserving entered notes, inputs, and unsaved runbook edits during runner/pack access changes. v0.47.0 · Sep 2026 · source · release history
-
Older MCP draft operations without a saved result now return
operation_incomplete; inspect the current draft before making another change. v0.46.0 · Sep 2026 · source · release history - Rejects dispatches that fail to decode or carry the wrong wire-protocol version at the wire, journaling the event; protocol mismatches are now permanent rather than retried. v0.44.0 · Sep 2026 · source · release history
- Protocol mismatches on the runner wire are now permanent failures rather than retried — dispatches with the wrong wire-protocol version will not be reattempted. v0.44.0 · Sep 2026 · source · release history
-
Running an older release now returns
not_liveinstead of silently dispatching current content; running an unpublished draft requires explicit consent plus the hash of exactly what was read. v0.39.0 · Aug 2026 · source · release history -
Running an older (non-live) release now returns
not_liveinstead of silently dispatching current content; running an unpublished draft requires explicit consent plus the hash of the draft as read. v0.39.0 · Aug 2026 · source · release history
+ GDPR erasure shipped Account and user erasure for GDPR compliance is available as an operator-run release task. 6 releases · 2 other sources · first seen Jul 2026 ▸
release
-
Adds
EMISAR_GROUPandEMISAR_RUNNER_IDenvironment variables to relabel a fleet runner without editing per-host configs. v0.37.0 · Aug 2026 · source · release history -
New
EMISAR_GROUPandEMISAR_RUNNER_IDenvironment variables let operators relabel a fleet without editing configs on each host. v0.37.0 · Aug 2026 · source · release history - Interactive reinstall with a different enrollment key prompts whether to preserve the existing external identity or reset it. v0.33.0 · Jul 2026 · source · release history
-
docs/COMPATIBILITY.mdnow documents on-host runner state (dispatch log, installed pack trees) as a compatibility surface with migration rules. v0.28.0 · Jul 2026 · source · release history - Account and user erasure (GDPR delete) is available as an operator-run release task. v0.28.0 · Jul 2026 · source · release history
- Account and user erasure (GDPR delete) available as an operator-run release task. v0.28.0 · Jul 2026 · source · release history
example
-
Cleanly remove a decommissioned runner's identity and token without wiping its logs or config, so the runner can be re-enrolled fresh.
$ install.sh --uninstallv0.33.0 · Jul 2026 · source -
Cleanly decommission a runner — wiping its cached token and generated identity — without losing its config, logs, or local evidence.
$ install.sh --uninstallv0.33.0 · Jul 2026 · source
+ LLM agent connection management shipped The console LLM agents list groups connections by operator, shows the bridge version per connection, and flags outdated bridges with a one-step upgrade path. 7 releases · first seen Jul 2026 ▸
Also counts toward: Web management console
release 7 total
- An MCP agent running as a subagent now forwards approval notices to its parent agent so the notification reaches the user rather than stopping in the subagent's reply. v0.54.0 · Oct 2026 · source · release history
- Connect an agent flow now generates account-specific setup for supported sandboxes including a connection test and Audit check. v0.48.0 · Sep 2026 · source · release history
- Runner tokens now carry a 90-day bounded lifetime and self-refresh two-thirds of the way through over the existing connection, with no host access required; expired tokens are refused at connect. v0.37.0 · Aug 2026 · source · release history
- MFA enrollment and recovery-code regeneration now require proof of the current inbox; credential step-up codes are rate-limited across the cluster rather than per node. v0.37.0 · Aug 2026 · source · release history
- ChatGPT tool annotations now distinguish read-only calls from mutations, and domain verification accepts OpenAI's text challenge. v0.33.0 · Jul 2026 · source · release history
-
Console LLM agents list now groups connections by the operator behind each key, displays the
emisar-mcpbridge version inline per connection, and flags out-of-date bridges with a one-step path to the upgrade command. v0.26.0 · Jul 2026 · source · release history
+ Pack action error handling shipped Pack actions fail loudly on missing source commands and HTTP error responses rather than silently returning empty success. 7 releases · first seen Jul 2026 ▸
release 7 total
-
Every Stripe and Braintree action ships a worked example, and JSON packs now return the provider error body via
--fail-with-bodyinstead of discarding it. v0.49.0 · Sep 2026 · source · release history -
Makes
statussingle-shot and kills the whole process group of an interrupted action. v0.44.0 · Sep 2026 · source · release history - Pack actions now fail on missing source commands and HTTP error responses rather than returning an empty success — any automation that depended on silent empty-success behavior will begin receiving failures. v0.36.0 · Jul 2026 · source · release history
- Makes pack actions fail explicitly on missing source commands or HTTP error responses instead of reporting empty success through a downstream pipe. v0.36.0 · Jul 2026 · source · release history
- Missing source commands and HTTP error responses now fail pack actions instead of silently reporting empty success through a downstream pipe or successful transport. v0.36.0 · Jul 2026 · source · release history
- Curl-backed API actions now fail on 4xx/5xx HTTP responses instead of reporting transport success, making pack error handling reliable. v0.34.0 · Jul 2026 · source · release history
+ Role and access normalization shipped Binds roles to immutable directory group IDs and normalizes owner access grants with audit trails. 7 releases · first seen Aug 2026 ▸
Also counts toward: Administrative audit log, Role-based access control
release 7 total
- Owner access normalization is audited and does not restore narrower grants on rollback. v0.47.0 · Sep 2026 · source · release history
- Owners always have workspace-wide action access; existing Owner scopes are normalized with an audit record. v0.47.0 · Sep 2026 · source · release history
- Role and runner-access mappings now bind to emisar's immutable directory-group ID, so same-name groups stay distinct, renames preserve grants, and delete/recreate never inherits old access. v0.43.0 · Aug 2026 · source · release history
- Role, runner, and pack scope changes now take effect in open web sessions immediately, reconnecting the session before stale authority can be acted on. v0.41.0 · Aug 2026 · source · release history
- Reads that expose every pack version or an exact run command now require a checked subject rather than relying on already-filtered callers. v0.41.0 · Aug 2026 · source · release history
- Runner, pack, action, approval, and audit discovery now enforces the member's current runner and pack scope across both the console and MCP. v0.40.0 · Aug 2026 · source · release history
+ Runner self-update shipped Allows installer-managed runners to verify and apply updates in place using checksums and attestations without host access. 5 releases · 2 other sources · first seen Jul 2026 ▸
Also counts toward: Command-line interface
release
- Runner and MCP version indicators now distinguish optional updates from required ones with direct update commands. v0.48.0 · Sep 2026 · source · release history
-
Adds
emisar updatesubcommand so installer-managed runners can update themselves, with automatic release-checksum and GitHub build-attestation verification before executing stop, swap, restart, and rollback. v0.40.0 · Aug 2026 · source · release history -
Adds
emisar updatesubcommand for installer-managed runners to self-update, with release checksum and GitHub build attestation verification before executing stop, swap, restart, and rollback. v0.40.0 · Aug 2026 · source · release history -
Adds
emisar updatesubcommand for installer-managed runners to self-update, verifying release checksum and GitHub build attestation before executing stop, swap, restart, and rollback. v0.40.0 · Aug 2026 · source · release history - Runner CLI now reloads the daemon automatically after a pack install, update, or uninstall. v0.31.0 · Jul 2026 · source · release history
example
-
Keep a runner up to date in a verified, attestation-checked way from the host where it is installed.
$ emisar updatev0.40.0 · Aug 2026 · source -
Update an installer-managed runner in place — the runner verifies checksum and attestation before swapping binaries.
$ emisar updatev0.40.0 · Aug 2026 · source
+ Runner identity and auto-enrollment shipped Runners use their hostname as identity so reboots and host replacements reconnect or enrol automatically without manual configuration. 3 releases · 4 other sources · first seen Jul 2026 ▸
Also counts toward: Command-line interface
release
-
Runners without an explicit
runner.idnow use their hostname as identity, so reboots reconnect the same runner and replaced ephemeral hosts auto-enroll without a persisted identity file. v0.35.0 · Jul 2026 · source · release history -
Adds
--reset-identityflag toinstall.shfor unattended runner identity resets when supplying a different enrollment key. v0.33.0 · Jul 2026 · source · release history -
Adds
--reset-identityflag toinstall.shfor unattended runner identity resets when supplying a different enrollment key during reinstall. v0.33.0 · Jul 2026 · source · release history
example
-
Relabel all runners in a fleet to a named group and assign unique IDs without touching per-host config files.
$ EMISAR_GROUP=prod-eu EMISAR_RUNNER_ID=runner-42 ./emisar-runnerv0.37.0 · Aug 2026 · source -
Relabel an entire runner fleet to a new group and assign stable IDs without touching per-host config files.
$ EMISAR_GROUP=prod-eu EMISAR_RUNNER_ID=runner-42 ./emisar-runnerv0.37.0 · Aug 2026 · source -
Reset a runner's external identity in an automated pipeline when rotating enrollment keys, skipping the interactive prompt.
$ install.sh --reset-identityv0.33.0 · Jul 2026 · source -
Force an unattended identity reset when re-enrolling a runner with a different enrollment key, for use in automation or CI pipelines.
$ install.sh --reset-identityv0.33.0 · Jul 2026 · source
+ Runner health diagnostics shipped Built-in diagnostic commands let operators verify dispatch log integrity, pack health, and last cloud rejection, producing a scriptable pass/fail verdict suitable for CI/CD gates. 3 releases · 4 other sources · first seen Jul 2026 ▸
Also counts toward: CI/CD pipeline integration, Command-line interface
release
-
emisar doctornow checks the dispatch log, reports degraded packs, and surfaces the last cloud rejection. v0.28.0 · Jul 2026 · source · release history -
Adds
emisar state check-dispatch-logsubcommand for scripted dispatch-log verdict checks. v0.28.0 · Jul 2026 · source · release history -
Adds
emisar doctorchecks for the dispatch log, degraded packs, and last cloud rejection; addsemisar state check-dispatch-logfor scriptable verdict on dispatch-log health. v0.28.0 · Jul 2026 · source · release history
example
-
Inspect runner health — dispatch log state, degraded packs, and last cloud rejection — from a single operator command.
$ emisar doctorv0.28.0 · Jul 2026 · source -
Script a CI/CD gate that fails a pipeline if the dispatch log is unreadable or in a bad state.
$ emisar state check-dispatch-log && echo "dispatch log OK" || exit 1v0.28.0 · Jul 2026 · source -
Check runner health — dispatch log integrity, degraded packs, and last cloud rejection — before or after an upgrade.
$ emisar doctorv0.28.0 · Jul 2026 · source -
Check dispatch-log health in a post-upgrade CI or runbook script to catch bad state before the service goes live.
$ emisar state check-dispatch-logv0.28.0 · Jul 2026 · source
+ Pack behavior test harness shipped Pack action tests run against real service managers, per-case Docker daemons, namespaced iptables, and a real dpkg database, with uncovered cases recorded explicitly. 3 releases · 3 other sources · first seen Jul 2026 ▸
Also counts toward: CI/CD pipeline integration
release
-
emisar pack update --jsonnow emits its partial report before returning a post-update validation error, preserving machine-readable output for automation pipelines. v0.40.0 · Aug 2026 · source · release history - Behavior harness now runs tests against a real service manager (PID 1), a per-case Docker daemon, iptables in its own namespace, and a real dpkg database for install, remove, and autoremove; uncovered cases are recorded with explicit reasons. v0.39.0 · Aug 2026 · source · release history
- The snmp pack's OSPF adjacency fixture now builds its network namespace on AppArmor-confined hosts. v0.35.0 · Jul 2026 · source · release history
example
-
Capture machine-readable pack update output even when post-update validation fails, so CI pipelines can parse the partial report before acting on the error.
$ emisar pack update --jsonv0.40.0 · Aug 2026 · source -
Capture machine-readable pack-update output even when post-update validation fails, so CI pipelines can parse the partial report.
$ emisar pack update --jsonv0.40.0 · Aug 2026 · source -
Capture machine-readable pack update output in CI even when post-update validation fails, so downstream automation can inspect the partial report.
$ emisar pack update --json > pack-update-report.json || truev0.40.0 · Aug 2026 · source
+ Runner dispatch log management shipped The runner detects corrupt dispatch state before connecting to the control plane and can quarantine bad logs during unattended upgrades to prevent crash-loops. 4 releases · 2 other sources · first seen Jul 2026 ▸
release
- Corrupt durable dispatch state now halts the runner before it connects to the control plane, preventing split-brain dispatch records. v0.27.0 · Jul 2026 · source · release history
- Upgrading to runner-v0.12.0 starts a new durable dispatch journal and does not import older unacknowledged entries; downgrading to an earlier runner after v0.12.0 has written new dispatch records is unsupported. v0.27.0 · Jul 2026 · source · release history
- Corrupt durable dispatch state now halts the runner before it connects to the control plane, preventing a misconfigured runner from silently operating. v0.27.0 · Jul 2026 · source · release history
-
Adds
docs/COMPATIBILITY.mdnaming on-host runner state (dispatch log, installed pack trees) as a compatibility surface with documented migration rules. v0.28.0 · Jul 2026 · source · release history
example
-
Automatically quarantine a corrupt dispatch log during an unattended host upgrade instead of crash-looping.
$ QUARANTINE_DISPATCH_LOG=1 ./install.shv0.28.0 · Jul 2026 · source -
Automatically quarantine a corrupt dispatch log during an unattended upgrade so the host does not crash-loop.
$ QUARANTINE_DISPATCH_LOG=1 bash install.shv0.28.0 · Jul 2026 · source
+ Signed dispatch trust shipped Accepts certificates from the user's own PKI for runner authorization, verifying chains against configured trust anchors. 5 releases · first seen Jul 2026 ▸
release
- Runner credential rotation uses the authenticated connection, and the dispatch journal appends durable transitions with periodic compaction. v0.47.0 · Sep 2026 · source · release history
- Issues X.509 certificates for signed dispatch where each certificate names the runners it may target v0.42.0 · Aug 2026 · source · release history
- Signed dispatch now accepts certificates issued from your own PKI, with each certificate naming the runners it may target and runners verifying the chain against configured trust anchors. v0.42.0 · Aug 2026 · source · release history
- MCP signed dispatch now signs and verifies the narrative a human approver actually reads (attestation v5) rather than a reconstruction of it. v0.37.0 · Aug 2026 · source · release history
- Signed-pack enforcement is now visible over MCP: a runner that requires signed packs announces that requirement to MCP clients. v0.30.0 · Jul 2026 · source · release history
+ TLS enforcement for outbound connections shipped All outbound connections enforce a minimum of TLS 1.2. 5 releases · first seen Jul 2026 ▸
release
- Pins a TLS 1.2 floor on the MCP bridge's HTTP client, enforcing a minimum transport security baseline for all outbound calls. v0.44.0 · Sep 2026 · source · release history
-
Policy overrides that cannot match any action ID — such as regex-style globs like
cassandra\.drop_*— are now flagged with a warning while you write them, surfacing deny rules that silently protect nothing. v0.38.0 · Aug 2026 · source · release history -
Adds a live validation warning when a policy override glob pattern cannot match any action ID — for example, regex-style patterns like
cassandra\.drop_*— so deny rules that silently protect nothing are caught while writing, not after deployment. v0.38.0 · Aug 2026 · source · release history - Outbound connections now assert a TLS 1.2 minimum floor. v0.28.0 · Jul 2026 · source · release history
- Outbound connections now enforce a TLS 1.2 floor. v0.28.0 · Jul 2026 · source · release history
+ Production plan management shipped A newer non-destructive production plan supersedes an older pending one, with Terraform confirmation as the single human apply gate. 5 releases · first seen Jul 2026 ▸
release
- Approval override flow now collects the audited reason once and clearly states which approval count is being bypassed and which policy and runner checks still apply. v0.43.0 · Aug 2026 · source · release history
- Trigram index added to speed run search on large accounts, replacing three now-covered indexes. v0.30.0 · Jul 2026 · source · release history
- A newer non-destructive production plan supersedes an older pending plan, with Terraform confirmation remaining the single human apply gate. v0.27.0 · Jul 2026 · source · release history
- A newer non-destructive production plan supersedes an older pending plan, with Terraform confirmation as the single human apply gate. v0.27.0 · Jul 2026 · source · release history
- Production infrastructure plans queue in order and never replace a review an operator already has open. v0.24.0 · Jul 2026 · source · release history
+ Pack registry shipped A dedicated pack registry with its own hostname and access controls scoped to exact object reads hosts pack distributions. 5 releases · first seen Jul 2026 ▸
Also counts toward: REST API
release
-
Extends
pack suggestto accept a registry catalog URL as a source. v0.42.0 · Aug 2026 · source · release history -
Pack retention no longer sweeps versions still advertised by a connected runner, preventing
pack_untrusteddispatch failures after idle-window cleanups. v0.35.0 · Jul 2026 · source · release history - Database-enforced tenant isolation: every runner-owned child row carries a composite foreign key to its account, so cross-tenant writes are refused at the database row level rather than only in application code. v0.30.0 · Jul 2026 · source · release history
-
Pack registry now serves from
registry.emisar.dev/v1/catalog.jsonwith anonymous access scoped to exact object reads and end-to-end tarball verification on publication. v0.24.0 · Jul 2026 · source · release history -
Pack registry now serves from its own hostname at
registry.emisar.dev/v1/catalog.json, with anonymous access narrowed to exact object reads. v0.24.0 · Jul 2026 · source · release history
+ Workspace billing management shipped Manages per-workspace subscription, payment methods, cancellation, and invoice states while ensuring transactional durability for checkout retries. 4 releases · first seen Sep 2026 ▸
release
- Billing is now per-workspace: the billing page manages payment method, cancellation, and subscription revival for the current workspace only. v0.50.0 · Sep 2026 · source · release history
- Billing management UI updated with clearer invoice states and explicit empty state for paid workspaces without invoices. v0.48.0 · Sep 2026 · source · release history
- Checkout retries now share a durable reservation, preventing duplicate charges and unresolved payment-link conflicts. v0.46.0 · Sep 2026 · source · release history
- Entitlements for paid plans now follow the subscription lifecycle, and Paddle runner quantities are kept in sync. v0.44.0 · Sep 2026 · source · release history
+ Argument boundary enforcement for pack actions shipped Arguments passed to exec-style commands in docker, systemctl, podman, and related packs must start with an alphanumeric character, blocking leading-dash flag injection. 4 releases · first seen Jul 2026 ▸
Also counts toward: CI/CD pipeline integration
release
- Runs each pack contained to its own directory tree; the runner refuses a credential file it does not own or that is reached through a symlink. v0.44.0 · Sep 2026 · source · release history
- Ships privileged packs with an exact host-access recipe and disables the user curlrc for every pack's curl invocations. v0.44.0 · Sep 2026 · source · release history
- CI now enforces that every high/critical action changed by the argument-boundary sweep has a successful behavior case or a declared machine-readable risk exception. v0.35.0 · Jul 2026 · source · release history
- Exec-style arguments across docker, systemctl, podman, minio, and related packs now anchor their first character to an alphanumeric, blocking hostile values from being parsed as leading-dash flags. v0.29.0 · Jul 2026 · source · release history
+ SCIM integration hardening shipped Ensures data integrity for group patches and immediately terminates active sessions when a connection is disabled. 4 releases · first seen Jul 2026 ▸
release
- Okta groups without an external ID can now be mapped directly. v0.43.0 · Aug 2026 · source · release history
- SCIM DELETE now retires the directory resource and its independent OIDC authority; an exact later POST revives only the directory resource. v0.42.0 · Aug 2026 · source · release history
- Adds atomic wire-order application of SCIM group patches with body bounding before authentication; disabling a SCIM connection now retires the sessions and pending identity links it vouched for. v0.36.0 · Jul 2026 · source · release history
- Disabling a SCIM connection retires all sessions and pending identity links it vouched for, which will terminate active sessions for affected users on upgrade. v0.36.0 · Jul 2026 · source · release history
+ OAuth connector account selection shipped OAuth connector setup lets a user choose which account to connect during the consent flow. 4 releases · first seen Jul 2026 ▸
release
- Signed dispatch now accepts certificates issued from your own PKI, with each certificate naming the runners it may target and runners verifying the chain against configured trust anchors. v0.42.0 · Aug 2026 · source · release history
- OAuth return targets now preserve their original local query string through SSO and registration flows. v0.33.0 · Jul 2026 · source · release history
- OAuth consent now lets a user choose which account to connect during connector setup. v0.27.0 · Jul 2026 · source · release history
- OAuth consent now lets a person choose which account to connect during connector setup. v0.27.0 · Jul 2026 · source · release history
+ Pre-dispatch rejection logging shipped Pre-run dispatch rejections such as contract changes, refusals, and rate limits are logged with allowlisted fields so refused MCP calls are visible in operations. 4 releases · first seen Jul 2026 ▸
release
-
Action children now run with
no_new_privs, so any setuid or setgid helper in a runner's process tree no longer elevates. For example,postqueue(setgidpostdrop) can no longer grant access to the Postfix queue — the runner user must own the queue directly or be apostdropmember. v0.37.0 · Aug 2026 · source · release history -
Action children now start with
no_new_privs, so a setuid or setgid helper in a runner's process tree no longer elevates. For example,postqueue(setgidpostdrop) can no longer grant access to the Postfix queue — the runner user must own the queue directly or be apostdropmember. v0.37.0 · Aug 2026 · source · release history - Pre-run dispatch rejections (contract changes, refusals, rate limits) now log bounded, allowlisted fields so rejected calls are visible in operations. v0.34.0 · Jul 2026 · source · release history
- Pre-run dispatch rejections (contract changes, refusals, rate limits) are now logged with bounded, allowlisted fields, making refused MCP calls visible in operations. v0.34.0 · Jul 2026 · source · release history
+ Service availability monitoring shipped A public status page backed by external monitors and on-call escalation surfaces availability problems including database outages and backend saturation. 4 releases · first seen Jul 2026 ▸
release
- Severe database and load-balancer conditions now page directly; point-in-time recovery drill measures actual RTO. v0.30.0 · Jul 2026 · source · release history
- Adds direct alerts for database-down, zero-healthy-backend, and portal VM saturation conditions. v0.28.0 · Jul 2026 · source · release history
-
Public status page available at
status.emisar.dev, with external availability monitoring and on-call escalation. v0.24.0 · Jul 2026 · source · release history -
Public status page at
status.emisar.devprovides external availability monitoring with on-call escalation. v0.24.0 · Jul 2026 · source · release history
+ Pack compatibility coverage shipped Extends pack support to additional software families and versions without dropping previously supported ones. 3 releases · first seen Aug 2026 ▸
release
- Adds pack compatibility for MongoDB 8.3, Kubernetes 1.37, ClickHouse 26.9, and Symbolicator 26.9 without dropping previously supported families.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ v0.52.0 · Oct 2026 · source · release history
- The Airflow pack now supports Airflow 2 (API v1) and Airflow 3 (API v2), with jobs, assets, and backfills requiring Airflow 3. v0.47.0 · Sep 2026 · source · release history
- Nomad namespaces are now supported in packs, with setup requirements surfaced in both the console and CLI. v0.42.0 · Aug 2026 · source · release history
+ Degraded pack visibility shipped Degraded packs are reported by name in API responses and flagged with remediation guidance on the runner detail page so operators know what to fix. 3 releases · first seen Jul 2026 ▸
Also counts toward: Web management console
release
- Reports local admission separately from the complete trusted pack descriptor in the Runner. v0.51.0 · Oct 2026 · source · release history
- Adds pack availability visibility in the Console: which actions are available and which runners reported an exact pack version and hash, with partial evidence labeled as partial. v0.51.0 · Oct 2026 · source · release history
-
Degraded packs now surface as named load failures in MCP
list_runnersresponses and as an amber notice with reasons and reinstall remedy on the runner detail page. v0.28.0 · Jul 2026 · source · release history
+ Session hardening shipped Enforces immediate disconnection upon session termination and requires inbox proof for MFA enrollment to prevent residual access during incidents. 3 releases · first seen Aug 2026 ▸
Also counts toward: Multi-factor authentication
release
- Replaying a still-valid spent OAuth refresh token now revokes the backing connection and its active successors, requiring reconnection. v0.42.0 · Aug 2026 · source · release history
- Ending a member's sessions now disconnects the live console session immediately, not only the cookie, closing the window where an active console remained usable after an administrator ended sessions mid-incident. v0.38.0 · Aug 2026 · source · release history
- MFA enrollment and recovery-code regeneration now require proof of the current inbox; credential step-up codes are rate-limited across the cluster rather than per node. v0.37.0 · Aug 2026 · source · release history
+ Large result streaming shipped Pages large terminal outputs via `wait_for_run` using opaque continuation tokens, allowing agents to process results larger than a single response. 3 releases · first seen Aug 2026 ▸
release
-
wait_for_runnow returns paginated 64 KiB continuation pages when a terminal runbook result exceeds one MCP response, keeping the summary in the first response. v0.40.0 · Aug 2026 · source · release history -
When a terminal runbook result exceeds one MCP response,
wait_for_runnow returns the summary in the first response and an opaque continuation token for ordered 64 KiB pages, removing the previous arbitrary total-step ceiling. v0.40.0 · Aug 2026 · source · release history -
wait_for_runnow pages large terminal runbook results as ordered 64 KiB chunks via an opaque continuation token when a result exceeds one MCP response, with small executions still completing in a single call. v0.40.0 · Aug 2026 · source · release history
+ Runbook draft management shipped Enforces a single-draft model per runbook with slug-keyed access for agents, ensuring atomic updates while keeping publication human-only. 3 releases · first seen Aug 2026 ▸
Also counts toward: MCP server
release
-
Adds
get_runbookandupdate_runbook_draftMCP surface keyed by slug, so an agent replaces the single unpublished draft under the hash it read; publication remains human-only. v0.39.0 · Aug 2026 · source · release history -
Adds
get_runbookandupdate_runbook_draftMCP endpoints keyed by slug, letting agents replace the single unpublished draft under the exact hash they read while keeping publication human-only. v0.39.0 · Aug 2026 · source · release history - Introduces a single-draft model per runbook: only one unpublished change can exist at a time; the history list labels the live release on the Run button itself (e.g. Run v3) and marks a waiting draft with a dot. v0.39.0 · Aug 2026 · source · release history
+ Hosted control plane shipped The control plane runs on hardened infrastructure with a private-network TLS-pinned database, zero-downtime rolling deploys, and no public compute surface. 3 releases · first seen Jul 2026 ▸
release
- Allows production MIG rollout placement in available zones. runner-v0.17.2 · Aug 2026 · source · release history
- Hosted admin runner bootstraps from a version-pinned release download with retries, eliminating GitHub API anonymous rate-limit failures on control-plane VM start. v0.35.0 · Jul 2026 · source · release history
- Hosted control plane moves to hardened infrastructure with zero-downtime rolling deploys, a private-network database with TLS pinned to a private CA, and no public compute surface. v0.24.0 · Jul 2026 · source · release history
+ Operator input persistence during co-approver broadcasts shipped Approval notes, grant scopes, and policy overrides entered by an operator survive console re-renders triggered by co-approver activity or refused submits. 3 releases · first seen Jul 2026 ▸
Also counts toward: Web management console
release
- Operator input (approval notes, grant scopes, policy overrides) now survives a console re-render triggered by a co-approver broadcast or a refused submit. v0.34.0 · Jul 2026 · source · release history
- Console operator input (approval notes, grant scope selections, policy overrides) now survives re-renders caused by co-approver broadcasts or refused submits. v0.34.0 · Jul 2026 · source · release history
- Operator input (approval notes, grant scopes, policy overrides) now survives console re-renders triggered by co-approver broadcasts or refused submits. v0.34.0 · Jul 2026 · source · release history
+ Pack trust conflict reporting shipped Pack-trust conflict errors identify the specific runners that disagree about an action instead of returning a generic failure. 3 releases · first seen Jul 2026 ▸
release
- Pack-trust conflict messages now name the specific runners that disagree about an action instead of failing generically. v0.34.0 · Jul 2026 · source · release history
- Pack-trust conflict UI now names the specific runners that disagree about an action instead of failing generically. v0.34.0 · Jul 2026 · source · release history
- Pack-trust conflict errors now name the specific runners that disagree about an action instead of failing generically. v0.34.0 · Jul 2026 · source · release history
+ Rate limiting for sensitive endpoints shipped SCIM, audit-export, and runner-register endpoints are rate-limited to prevent abuse. 2 releases · first seen Jul 2026 ▸
release
- Adds per-client-address request caps for MCP and audit-export endpoints. v0.51.0 · Oct 2026 · source · release history
- SCIM, audit-export, and runner-register endpoints are now rate-limited. v0.28.0 · Jul 2026 · source · release history
+ Service accounts and API keys shipped Provides a Console Settings page for creating service accounts and scoped API keys for non-human programmatic access to a workspace. 1 release · 1 other source · first seen Oct 2026 ▸
Also counts toward: Web management console
release
- Adds a dedicated Settings page in the Console for creating service accounts and API keys with scoped access.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ v0.51.0 · Oct 2026 · source · release history
example
-
Create a service account for an app such as Ryker that needs scoped, non-human API access to a workspace.
$ In the Console, go to Settings > Service Accounts and select 'Create service account', then generate an API key with the required scoped access.v0.51.0 · Oct 2026 · source
+ Pack script error handling shipped Enforces strict exit codes on packaged scripts to ensure actions fail visibly on step errors rather than silently succeeding. 2 releases · first seen Sep 2026 ▸
release
-
Enforces
set -euo pipefailon all packaged scripts via new pack lints v0.49.0 · Sep 2026 · source · release history -
Enforces
set -e(set -euo pipefailunder bash) on every packaged script, with the packs gate linting for it, so a failed step ends the action instead of silently exiting 0. v0.49.0 · Sep 2026 · source · release history
+ Pack behavior testing shipped Exercises pack actions against real service managers, Docker daemons, and system states to verify correctness before deployment. 2 releases · first seen Aug 2026 ▸
release
- Behavior harness in Packs now exercises a real service manager booted as PID 1, a per-case Docker daemon, iptables inside its own namespace, and a real dpkg database for install, remove, and autoremove scenarios. v0.39.0 · Aug 2026 · source · release history
- Behavior harness for packs now runs against a real service manager booted as PID 1, a per-case Docker daemon, iptables inside its namespace, and a real dpkg database for install, remove, and autoremove scenarios; uncovered cases are recorded with an explicit reason. v0.39.0 · Aug 2026 · source · release history
+ Runbook publishing diff shipped Renders a line-level diff against the live release hash during publish confirmation to clarify exactly what will change. 2 releases · first seen Aug 2026 ▸
release
- Runbook publishing now renders a line-level diff of what changed from the live release before confirming, using the canonical content hash as the definition's identity. v0.39.0 · Aug 2026 · source · release history
- Publish confirmation now renders a diff of changed lines against the canonical text whose hash defines the release, so reviewers see exactly what will move the hash before approving. v0.39.0 · Aug 2026 · source · release history
+ Policy override validation shipped Provides live warnings for policy globs that cannot match any action ID, preventing silent failures in deny rules. 2 releases · first seen Aug 2026 ▸
release
-
Policy overrides that cannot match any action ID — such as regex-style globs like
cassandra\.drop_*— are now flagged with a warning while you write them, surfacing deny rules that silently protect nothing. v0.38.0 · Aug 2026 · source · release history -
Adds a live validation warning when a policy override glob pattern cannot match any action ID — for example, regex-style patterns like
cassandra\.drop_*— so deny rules that silently protect nothing are caught while writing, not after deployment. v0.38.0 · Aug 2026 · source · release history
+ Runbook size and encoding correctness shipped Correctly reports size limits for runbooks and prevents multibyte-encoded descriptions from silently vanishing due to character vs. byte count mismatches. 2 releases · first seen Jul 2026 ▸
release
-
Runbook projection failures now report the actual size rather than returning a not-found response, so oversized runbooks are no longer silently dropped from
list_runbooksor denied inget_runbook. v0.38.0 · Aug 2026 · source · release history - Pre-run dispatch rejections (contract changes, refusals, rate limits) now log bounded, allowlisted fields, making rejected calls visible in operations without writing model input to the log. v0.34.0 · Jul 2026 · source · release history
+ Pack catalog optimization and compression shipped Reduces bandwidth usage via CDN compression and enforces stricter visibility filters to exclude retired or invalid versions from model-visible results. 2 releases · first seen Jul 2026 ▸
release
- MCP catalog, search, exact lookup, runner inspection, and runbook recovery now exclude pending, rejected, revoked, retired, hash-mismatched, and incomplete pack versions from model-visible results. v0.33.0 · Jul 2026 · source · release history
- Registry now serves the catalog compact and gzip-encoded behind a CDN, reducing transfer to roughly one-tenth of the previous size; pack tarballs remain unencoded to preserve content-hash pinning. v0.32.0 · Jul 2026 · source · release history
+ Production incident response skill shipped Provides a bounded observe-diagnose-act-verify workflow for customer agents to safely handle production incidents. 2 releases · first seen Jul 2026 ▸
release
-
Adds a new public
respond-to-production-incidentsskill providing customer agents a bounded observe-diagnose-act-verify workflow. v0.33.0 · Jul 2026 · source · release history -
Adds a new public
respond-to-production-incidentsskill giving customer agents a bounded observe, diagnose, act, and verify workflow. v0.33.0 · Jul 2026 · source · release history
+ MCP argument validation and coercion shipped MCP argument errors name the specific field and type mismatch, and scalar arguments sent as strings are coerced to their expected types rather than failing the call. 2 releases · first seen Jul 2026 ▸
release
-
MCP argument faults now name the specific field and type mismatch — e.g.
limit must be a JSON integer from 1 to 100; it was sent as a string.— replacing generic contract errors; enum faults list allowed values and unknown arguments are spelled out against the allowed set. v0.29.0 · Jul 2026 · source · release history -
Scalar MCP arguments sent as canonical strings (e.g.
"limit": "50","dry_run": "true") now coerce to their expected types instead of failing the call. v0.29.0 · Jul 2026 · source · release history
+ Console navigation layout shipped Groups the console sidebar into Connect, Operate, and Control sections, placing related items such as service accounts, runbooks, and policy settings together. 1 release · first seen Oct 2026 ▸
release
- The console sidebar is now grouped into Connect, Operate, and Control sections: service accounts sit with runners and AI agents, runbooks with runs, and policy, packs, team, and billing together. v0.54.0 · Oct 2026 · source · release history
+ Policy editor usability shipped Keeps targeted rulesets open during editing, hides inapplicable approval settings, consolidates ruleset target search into one dropdown, and shows each ruleset's preview beside its editor. 1 release · first seen Oct 2026 ▸
release
- The policy editor now keeps targeted rulesets open, hides approval settings that cannot apply, searches ruleset targets in one dropdown, and starts each ruleset's preview beside its editor. v0.54.0 · Oct 2026 · source · release history
+ Pack reporting and runner attribution shipped suggested Pack reporting shows which runners reported exact pack content, removing repeated counts and empty-state tooltips. 1 release · first seen Oct 2026 ▸
Suggested capability: LLM application tracing. This is our guess, not confirmed.
release
- Pack reporting now shows which runners reported the exact pack content, removing repeated counts and empty-state tooltips. v0.52.0 · Oct 2026 · source · release history
+ Member email management shipped Allows members to update their email address from Profile after mailbox verification, and supports directory sync pushing email updates while surfacing refused changes. 1 release · first seen Oct 2026 ▸
release
- Supports updating member email addresses from Profile after mailbox verification; directory sync can push email updates and surfaces refused changes. v0.51.0 · Oct 2026 · source · release history
+ SuperTokens pack shipped Adds a pack covering SuperTokens auth-core health, users, sessions, and roles, with gated mutations. 1 release · first seen Oct 2026 ▸
Also counts toward: Role-based access control
release
- Adds a new SuperTokens pack covering auth-core health, users, sessions, and roles, with gated mutations. v0.51.0 · Oct 2026 · source · release history
+ Config reload risk unification shipped Aligns the risk tier for config reloading across all packs and retires incompatible pack versions. 1 release · first seen Sep 2026 ▸
release
-
Unifies the risk tier for reloading a config to
highin every pack, and aligns the cancel-query tier across Postgres and CockroachDB;fail2banandcockroachpack versions below 0.2.0 that previously auto-ran those actions are retired. v0.49.0 · Sep 2026 · source · release history
+ Diagnostic pack enrichment shipped Adds symptom keywords to host diagnostics and suggests relevant packs based on the runner's environment. 1 release · first seen Sep 2026 ▸
release
-
The six on-host diagnostic packs (
linux-core,debugging,systemd-deep,process-forensics,fs-search,network-tls) are enriched with operator-typed symptom keywords so searches reach them first;podman,zfs,wireguard, andnodejs-pm2are suggested on hosts that run them. v0.49.0 · Sep 2026 · source · release history
+ Runbook voting transparency shipped Exposes dispatch rationale, trusted command lines, votes, and override receipts to agents via the MCP `wait_for_run` response. 1 release · first seen Sep 2026 ▸
release
-
Adds a
reviewobject towait_for_runandrecent_runsMCP responses for policy-gated runs, exposing dispatch rationale, the trusted command line, votes, and the override receipt under theview_runspermission.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ v0.49.0 · Sep 2026 · source · release history
+ Agent sandbox environments shipped Provides supported sandbox environments for agents with scoped controls over files, secrets, and tools. 1 release · first seen Sep 2026 ▸
release
-
Adds
co:opas a supported agent sandbox environment with controls for files, secrets, and tools access. v0.48.0 · Sep 2026 · source · release history
+ Runner configuration hot-reload shipped Allows reloading the full runner configuration via SIGHUP without requiring a process restart. 1 release · first seen Sep 2026 ▸
release
- Adds SIGHUP support to reload the full runner config without a process restart. v0.44.0 · Sep 2026 · source · release history
+ Windows MCP bridge support shipped Extends the MCP bridge to Windows with native ARM64 binaries, VS Code integration, and direct authentication. 1 release · first seen Aug 2026 ▸
release
- Windows support added to the MCP Bridge, including VS Code integration, native ARM64 binaries, direct authentication, and safer client-config replacement with symlink-safe backups. v0.42.0 · Aug 2026 · source · release history
+ Shell history protection for credentials shipped Key-bearing connector commands are excluded from shell history to prevent credential exposure. 1 release · first seen Jul 2026 ▸
release
- Key-bearing connector commands are kept out of shell history. v0.27.0 · Jul 2026 · source · release history
+ Unsigned installation isolation shipped Unsigned installations do not open or lock signing nonce state during startup, keeping them isolated from signed release flows. 1 release · first seen Jul 2026 ▸
release
- Unsigned installations no longer open or lock signing nonce state during startup. v0.27.0 · Jul 2026 · source · release history
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
11 commands for emisar, each with where it came from. This tool has no source analysis yet, so there is no option reference and no captured run beside them.
No command matches.
Release-note detail over time
See how much detail emisar puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
26 entries
No entries match these filters.
- September 20263
- August 20269
- July 202614
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.