Repository navigation
Skill Recorder v0.9.0
Source-only release
Skill Recorder 0.9.0 is published from commit
53447f6cca45ad84468ff8898b182c37fb7ab9e5.
This release is source-only. No installers or portable binaries are attached.
GitHub's generated archives contain the tagged repository source only.
Changes
- Choose how to power AI: at the first Analyze/Create action, select
Bring your own model or GitHub authentication. Recording remains
available without either. The choice is available to everyone, including
Microsoft employees. - Bring your own model: use Microsoft Foundry/Azure OpenAI, OpenAI,
Anthropic, or a custom OpenAI-compatible provider without GitHub login or a
Copilot subscription. Provider billing applies. - Configure your API key, endpoint, and model/deployment name, with API-format
and Azure-version options where applicable. Standard OpenAI/Anthropic URLs
are prefilled. The selected model must support images and tool calling. - Test and save verifies image/tool support using a small, provider-billed
synthetic test, not a recording. - Remember keys securely: use OS-protected storage when available. If it is
unavailable, explain this on the key-entry screen and continue automatically
using memory only, without an extra step or blocking BYOM. - Forget key removes this app's stored and in-memory credential. Change
connections later through AI connection in Sessions. - Preserve the existing Microsoft employee Enterprise SSO and personal GitHub
sign-in flows under GitHub authentication. - Apply the selected provider consistently to analysis, skill generation, and
automation generation. Preserve tool restrictions and cancellation/retry
safeguards, and reset live AI conversations when a connection changes. - Show provider-aware data-destination disclosures and isolate BYOM sessions
from unrelated CLI configuration.
Compatibility, privacy, and upgrade notes
- BYOM is not automatically local/offline or free. Requests go to the configured
provider, under its availability, rate limits, policies, and billing. - A provider's model catalog does not guarantee every model can analyze
recordings. Image input and tool calling are required; custom endpoints must
implement a compatible API. - Foundry v1 uses a full base URL ending in
/openai/v1/; native versioned Azure
uses a resource host and API version. The model field is the deployment name
for Azure, which may differ from the base model name. - Keyless local-service onboarding and managed-identity authentication are not
exposed by this release. - Windows uses DPAPI, macOS uses Keychain, and Ubuntu needs an available secure
desktop keyring to remember keys. Without secure storage, the key is kept only
until the app closes and is requested again on the next launch. - Forgetting a key does not revoke it at the provider or erase recordings and
SDK conversation history. Connection state lives outside recording folders,
and credentials are excluded from debug exports. - Finish or cancel active AI work before changing its connection. Saved
recordings and generated outputs remain intact. - Existing local transcription and sensitive-data protection remain in place.
Review inferred activities and generated instructions; protection is a safety
net, not a guarantee. - Dependency versions and installer scripts are unchanged. Re-run the
commit-pinned source installer below to update. Locally assembled builds are
not redistributable release binaries.
Validation
- Local validation: 291 unit/regression/import tests, production build,
application/eval type checks, lockfile portability, and a 285-package license
inventory. - The actual bundled SDK/CLI completed a synthetic image-and-tool turn against
a local provider fixture without GitHub authentication; runtime artifacts
were checked for provider-key persistence. - An isolated UI preview covered initial selection, the memory-only disclaimer,
connection save/analysis continuation, cancellation, and forgetting. - Native Windows ARM64 protected-key persistence, restart recovery, and removal
were exercised. - PR CI passed on Windows x64/ARM64, macOS, and Ubuntu. The initial ARM64
compliance test process failed after all assertions passed; a targeted rerun
passed without code changes. - Exact release-commit CI passed on Windows x64/ARM64
and macOS/Ubuntu,
covering commit-pinned source installation, license/compliance checks,
tests, builds, BYOM runtime transport, and applicable packaging/architecture
checks. - Native secure-storage smoke checks on macOS, Ubuntu, and Windows x64, and paid
live-provider checks, have not been performed in this session. Automated
transport tests do not establish native storage or live-provider behavior.
Installer script SHA-256
These hashes were calculated from the exact release commit's Git blobs.
7678f7f8d38d600f2fb732f95afeadc8aa4f9b9802989d26e2f932970795770c install.ps1
bd8b5200a2c140c5a5ed9299d565ac72cee5420181774008977eaf75f210db1d install.sh
Commit-pinned installation
Windows 11 x64 or ARM64
$commit="53447f6cca45ad84468ff8898b182c37fb7ab9e5"; $env:SKILL_RECORDER_COMMIT=$commit; irm "https://raw.githubusercontent.com/microsoft/skill-recorder/$commit/install.ps1" | iexmacOS or Ubuntu
commit="53447f6cca45ad84468ff8898b182c37fb7ab9e5"; curl -fsSL "https://raw.githubusercontent.com/microsoft/skill-recorder/$commit/install.sh" | SKILL_RECORDER_COMMIT="$commit" bashFor script inspection and hash verification before execution, use the
inspect-first instructions.
Full changelog: v0.8.0...v0.9.0