Skip to content

Agent Wiki 0.9.1

Choose a tag to compare

@chrisbyboston chrisbyboston released this 06 Oct 10:12
· 31 commits to main since this release

Agent Wiki 0.9.1 simplifies two-factor setup with separate Passkey and Authenticator app cards. Add a passkey opens the device prompt immediately. New passkeys receive a default label such as Passkey 1, with optional inline renaming afterward. The success screen keeps recovery codes available while renaming and offers a direct download plus an optional code preview.

The responsive interface supports light and dark appearance. Renaming requires recent authentication, ownership and CSRF checks, and preserves the passkey credential, browser sessions and recovery codes. Existing explicitly named API registrations remain supported. All other MFA enrollment, verification, removal and recovery requirements remain in place.

Validation: 238 core tests and 75 browser tests passed on macOS and Linux. Exact-commit managed Linux CI passed both source/browser and Nix package checks. Its first attempt hit a timing failure in an unchanged MCP preview test; the complete retry passed with the same runner and limits. Independent review found no P0/P1/P2 issues. Native upgrade from 0.9.0, container replacement and backup/restore qualification passed.

The signed Linux amd64 OCI archive is qualified; native host closure distribution is not published. The current production npm audit reports six low and four moderate affected-package entries, with no high or critical entries. Installed npm dependencies and 132 runtime artifacts are unchanged from 0.9.0. The signed security record documents applicability and retained prior runtime findings; no clean-dependency claim or fresh runtime-feed scan is made.

There is no new database migration. The MFA recovery requirements continue to apply, including paired database/key backup and 0.9.0-or-newer server and lifecycle tools after enrollment.

Source: 44e32573e94c723b7dfe6a8373a9c9d8bca076b5. Verify the SSH-signed annotated tag and artifact signatures against the trusted release key. This remains initial-development software; publishing source does not automatically deploy installations.