Agent Core 0.15.0 — Windows x64

Agent Core 0.15.0 — Windows x64

Stable release for the documented external-controller workflow. The current README describes the shipped product, setup and boundaries; historical roadmap text has been removed from that entry point.

Included improvements

• Deadline-aware recall, resumable task continuity and revision-bound Memory claim review through the existing owners.
• Background Open Browser Use with guarded form controls, nested-panel scrolling and paged reading of loaded ChatGPT conversations.
• Dashboard proposal cards and readable Markdown under docs/proposals, with a structured approval/revision/hold/rejection guide. Fully completed proposals move to docs/history-agent-core.
• Installed performance-oriented engineering and strengthened reverse-engineering Skills. External bootstrap/context guidance exposes current digest-bound instructions; REA reuses pinned tooling with explicit runtime selection and fail-closed validation.
• Current Workflows diagrams, Windows portability, same-owner Skill recovery, committed-source packaging and the complete official restart chain.

Native implementation remains frozen. Only the specifically approved three Native test fixtures and their three baseline hashes changed. The exact completed review is available in the source repository.

Download and integrity

Download Agent-Core-v0.15.0.zip and SHA256SUMS.txt below. Keep the extracted directory intact; the EXE depends on its bundled files.

Source: c8a0d306493ecbfaa8a5c9f9ae9df1754d813e98
ZIP bytes: 227895803
ZIP SHA-256: 13ac2f48f5fe1a48cac50ad0c8fa06867cecd39f17db54b487a0981a4c67f226
EXE SHA-256: 45fc4bcb64ec3700a65410ab8cc18522f542340baeabb7742992c21bc2221f8e

RELEASE-MANIFEST.json binds the source and archived release intents. INTEGRITY-MANIFEST.json describes packaged files. ACCEPTANCE.json records sanitized verification outcomes. RELEASE-NOTES.md retains the generated change details.

Verification

The actual ZIP passed entry-boundary checks, extraction, 20,950 immutable file hashes, EXE version checks, UI/restart-chain checks and browser-helper binding. The extracted package initialized fresh canonical Memory and ran its bundled Core: health 0.15.0, Memory/execution available, two packaged Skills, anonymous MCP rejected with HTTP 401, and graceful shutdown with zero component issues.

The installed runtime was activated using the official restart capability. Its health reports 0.15.0; four existing/installed Skills remain available. Both engineering instructions were delivered completely. Actual Agent Core process capability ran REA on this exact EXE: 29 PE entries, 12 resources, with static-analysis limitations retained. Agent Core Browser Use scrolled the settings panels and clicked Refresh tools in the background, observed loading followed by readiness, and acknowledged closing its owned tab while retaining the existing browser.

Source checks: full root run 3,006 passed / 3 failed / 37 skipped; all three fixture failures were corrected and their three files reran 37 passed / 0 failed / 1 skipped. This closes all 3,009 executed root cases across the runs; the original full command remains recorded as failed. Additional checks: UI 24 passed plus typecheck, static inspector 53, REA launcher 6, Skill recovery 12 and release-readiness 16. Structural compatibility passed against the prior baseline; it does not establish unchanged runtime refinement/authentication/task behavior.

Installation and scope

Windows x64 and Microsoft Edge WebView2 Runtime are required for the desktop launcher. For a new installation with no existing Memory, run from the extracted root while Core is stopped:

.\runtime\node\node.exe .\scripts\memory\activate-canonical.mjs --fresh

Then launch Agent Core.exe and configure authentication/providers as needed. Existing installations require explicit migration/recovery; do not overwrite a running store. No user Memory, credentials, browser profile or private tooling link is included.

REA CLI dependencies on a new machine require explicit restoration using the engineering guide. Browser use requires a connected supported extension. Conversation reads cover loaded DOM and declare incomplete history. Fresh-package qualification covers Node/Core, Memory, HTTP health/auth and shutdown; fresh-machine GUI/WebView2 and optional providers/devices/browser workflows are not qualified by that check. Explicit platform/privilege/opt-in/live skips remain. No live learning/intelligence gain or general speedup is claimed.

See the current release guide for details.

Agent Core v0.15.0-beta.0 - Windows Portable Prerelease

Windows portable prerelease and source

Updated 2026-10-10 UTC after review of the Windows integration report.

Tagged source commit: 23fdca411e152c42fe1a5b81f526b18d6d57bd3b. Product: 0.15.0-beta.0; native file/assembly: 0.15.0.0. This remains a prerelease, not a stable promotion. The 28 stable release intents remain unconsumed.

Downloads

The uploaded Agent-Core-prerelease-0.15.0-beta.0.zip is the Windows portable runtime built from the clean tagged checkout. GitHub-generated “Source code” ZIP/tar downloads are source only and are not the portable runtime.

• Portable ZIP: 192,161,595 bytes
• SHA-256: e54f590f9b260c5ffbd817054ca827117904ca222c8081a11f1a2073e92b13ee
• Accompanying assets: ARTIFACT-MANIFEST.json, ARTIFACT-NOTES.md and SHA256SUMS.txt.
• Four remote asset IDs, sizes and API digests match the supplied publication receipts. Those receipts also record fresh remote download/hash verification.

Included

• External MCP image overview, crop and zoom.
• Memory Plan 01 filtered semantic retrieval with full-corpus validation and eligible-subset ranking.
• Unified System + Memory Workflows canvas using the pinned offline Archify renderer. This shows static source dependencies, not runtime telemetry.
• Updated README/CODEBASE, historical archive, version-assessment policy and prerelease packaging.

Windows package verification

The clean exact-tag checkout built Core/Memory/UI and a fresh production launcher. The three release suites reached 23 passing cases cumulatively after correcting an ignored fixture-directory prerequisite; initial failures remain recorded. The tagged launcher built without a source patch. Packaging advanced only the staging prerelease sequence; the release tag did not move.
Fresh extraction verified 20,519 files with exact membership, sizes and hashes. Packaged Core smoke passed using bundled Node, foundation-only Memory and a ready Workflows map; normal shutdown passed. A second portable launcher GUI session was not tested because production mutex behavior was preserved. Do not describe this as full clean-install GUI acceptance.

Separate daily-installation acceptance

The reported daily installation is a directed integration preserving local changes, not an exact copy of this tag.

• Workflows production activation and functional smoke accepted.
• The earlier launcher hash discrepancy was resolved by an independent production rebuild matching the installed executable. The historical stage mismatch was corrected, not erased; its original cause remains unknown.
• Memory Plan 01 source integration, compiled artifact cutover, fresh resident process and MCP capabilities readback accepted.
• Offline semantic behavior passed through a real MCP client/transport using synthetic fixtures and a deterministic fake embedder, including synonym recall and workspace isolation.
• 522 applicable Windows nonbenchmark test cases passed cumulatively (491 initial + 31 recovered). The original full verify command remains FAIL; two Linux case-sensitive fixtures were not run on Windows, and benchmark import failed before benchmark cases executed. Recovery changed test-harness paths/timeouts, not production code or test assertions.

Limits and remaining work

Real provider quality and benchmarks remain deferred. Actual rollback execution, second-session portable GUI acceptance and full unmodified cross-platform regression are not claimed. Memory Plans 02–11 have not been started through this acceptance.

The historical @black-project-agent-core/agent-core-plugin@0.7.0 is a separate declarative plugin, not this portable runtime. The reported npmjs publication attempt was blocked by authentication requirements and is not claimed published. No credential or security-setting change is part of this release-note update.

Earlier Linux preparation passed Core/Memory/UI builds, 31 focused Workflows tests, 10 UI tests and 6 new prerelease tests. Its 21/23 release-suite result lacked Windows PowerShell; the subsequent Windows evidence above supplies the corresponding archive checks.

Tagged source notes (historical publication state) · Publication guide

This update corrects publication/acceptance status only. It changes no source, tag, assets, visibility or version.

Agent Core v0.12.0 - Stable

Recovery correction - 2026-09-20: the immutable Agent-Core-v0.12.0.zip was created before discovery that its bundled .env.example had been overwritten by filesystem corruption (6,687 NUL bytes). The runtime/package checksum remains unchanged. When recovering from this release, use the attached Agent-Core-v0.12.0-env.example instead; main also contains the corrected source-grounded template.

Agent Core v0.12.0

Changes

• [minor] Complete the Serena-derived Semantic IDE deferred wave with loopback external TCP providers, multi-root workspaces, provider hot reload, type hierarchy, diagnostics delta, version compatibility checks, hardened provider environment boundaries, and scalable workspace freshness.
• [minor] Adopt Anthropic-SDK-derived runtime hardening for bounded outbound retries and response IO, secret-environment isolation, sensitive credential-file handling, atomic persistence durability, correlation-safe diagnostics, expanded redaction, and read-only release compatibility review.
• [minor] Add A-MEM-derived non-mutating memory evolution preview with bounded neighbor review evidence while preserving explicit memory_batch mutation authority.
• [minor] Adopt Changesets-derived release policy wiring, metadata-safe intent discovery, non-consuming snapshot artifacts, and explicit prerelease channel state.
• [minor] Adopt Reflexion-derived same-failure-family stagnation advisories and compact redacted failure-evidence history for bounded diagnosis.
• [minor] Adopt final Grafel boundary hardening: workspace registry hygiene, Audit/reference-tree exclusion from the current-line graph, MCP schema/manifest contracts, provider wire-version compatibility, typed Code Intelligence query parity, and bounded graph-touch evidence.
• [minor] Add verified project-local Semantic IDE provider provisioning and repair plus an external MCP acceptance harness.
• [patch] Adopt Anthropic SDK-derived structured MCP result fallback, abort-listener cleanup, and fail-soft outbound attempt observability.
• [patch] Adopt Anthropic SDK-derived MCP result convergence, Phone SSE framing, outbound cancellation lifecycle, and race-bound file I/O hardening.
• [minor] Add source-anchored memory provenance and staleness evidence, bounded revision snapshots, and source-file-aware retrieval ranking.
• [patch] Restore stable Hermes partner discovery and v0.21.3 source recovery across split Hermes/9Router layouts after filesystem corruption.

Packaging boundary

This archive contains the current Agent Core runtime plus a source snapshot needed for audit/reconstruction. Live credentials, .env, secrets, OAuth/API-key state, user memory notes, tracker logs, browser profiles, backups, Git metadata, and protected reference repositories are intentionally excluded.

Agent Core v0.7.0 - Prerelease

Agent Core 0.7.0 updates the complete active project: runtime source, workflow and memory services, execution provenance, operational scripts, tests, plugin source, Supabase migrations, and SubProject source.

This is a prerelease. The existing v0.6.0 Stable release and package stable tag remain unchanged.

Main changes

• Source-grounded craft_source, workflow_plan, and workflow_status with current receipts, accepted plans, managed DAG execution, and evidence-backed completion.
• Canonical Markdown memory, deterministic Graphify recall, direct scoped Supabase second memory, and durable workflow synchronization/recovery.
• Required scoped preflight, durable task finalization, current-attempt artifact validation, and explicit closure retry without repeating successful work.
• Windows lifecycle, shell/startup handling, OAuth/tunnel supervision, portable source tooling, and version identity updates.
• Active source for Agent Code, Presentation Bridge, Super-Runtime, Market-Signal-Lab, and the remaining SubProject material is included in the project snapshot. This does not certify every independent subproject binary.
• No additional inference provider or model API key is required.

Downloads

Asset	Contents
agent-core-project-v0.7.0-source.zip	Complete tracked superproject source: 1,265 regular files. Two upstream submodules remain pinned in Git; their contents are not vendored.
agent-core-windows-v0.7.0-prerelease.zip	Agent Core runtime distribution with fresh compiler output, runtime source, scripts, selected docs, and migrations.
agent-core-fresh-v0.7.0-prerelease.zip	The same clean runtime payload, without operator configuration or data.
agent-core-plugin-v0.7.0-prerelease.zip	Plugin source and routing/GitHub skills.
black-project-agent-core-agent-core-plugin-0.7.0.tgz	Exact GitHub Packages npm artifact, published under next.
presentation-bridge-v0.2.0-source.zip	Standalone Presentation Bridge source snapshot; its independent version remains 0.2.0.
release-manifest.json, SHA256SUMS.txt	Source commit, channel, asset inventory, sizes, and SHA-256 checksums.

The runtime ZIP is not a bundled installer for all native subprojects. Install its documented Node dependencies and project-local tools, configure your own .env, and build native components separately when needed. Private .env files, credentials, live memory, logs, caches, reference-vault contents, and installed tools are excluded.

Verification

• Fresh isolated build succeeded; runtime archives contain 318 freshly generated compiler files.
• Functional regression results: 1,092 passed, 11 skipped across a 184-file suite. Missing isolated-tool prerequisites were provisioned, and failed cases were rerun selectively; these totals combine the full run and those targeted rechecks.
• Unchanged quality gate passed: 40 routing cases and 12 memory cases, including full graph-target and hard-guardrail recall.
• Brand, release metadata, documentation-link, tracked-source, archive-entry, CRC, and SHA-256 checks passed.
• The full-source ZIP matches the committed source bytes; GitHub Package and release assets share the same manifest identity.
• Performance gates/benchmarks and whole-project Stable certification were not run. Local verification was used; GitHub Actions remains disabled.

Source commit: 4c0cf8e070bf11dfa89e6fcef611a54bcd4c0480.

GitHub Package: @black-project-agent-core/agent-core-plugin@0.7.0 (next). The package uses the existing Agent Core MCP connection; it does not embed another model or controller.

Agent Code v0.1.0 Vault Preview 1

Agent Code v0.1.0 Vault Preview 1 is a prerelease candidate for native Windows acceptance of the secure OpenRouter credential vault and deterministic rotation milestone.

Included candidate scope:

• Windows current-user DPAPI protected credential storage
• metadata-only Credential Vault UI
• OpenRouter GET /api/v1/key validation without model inference
• deterministic bounded rotation state machine
• automated credential secret-boundary/corruption certification gate

This is NOT a stable release. Native Windows DPAPI self-test, add/restart persistence, live stored-key validation, and Windows synthetic rotation acceptance remain required before Milestone 2A certification.

Agent Code v0.1.0 Preview 2

Windows x64 preview. Fixes Preview 1 startup failure: TaskDialogIndirect entry point not found. Preview 2 restores the Tauri Common Controls v6 Windows manifest and adds a build-time artifact contract that fails if TaskDialogIndirect is imported without Microsoft.Windows.Common-Controls 6.0.0.0. Cross-compiled on Linux; native Windows launch validation is still pending user/device confirmation.

BROKEN — Agent Code v0.1.0 Preview 1

DO NOT USE. Preview 1 has a Windows startup defect: TaskDialogIndirect entry point not found because the build embedded a minimal manifest without Microsoft.Windows.Common-Controls v6. Use Preview 2 instead.

Agent Core v0.6.0 - Stable

[0.6.0] - 2026-08-31 — Stable

Added

• Wave A-F hardening is consolidated into the stable control plane: repaired trust boundaries, dual-era MCP support, deterministic execution policy/recovery, tamper-evident observability, deterministic routing/memory quality gates, adaptive local resource governance, bounded evidence-based diagnosis, and optional safe local maintenance.
• Wave G adds a repository-owned 18-area core certification contract plus npm run certify:core:prepublish and post-publication npm run certify:core gates so architecture-level stability claims require the same repeatable local evidence.
• Core certification now binds normal regression, Wave E routing/memory quality, 100k deterministic-memory performance, deterministic execution performance, stable-release parity, release metadata, and no-external-AI/model/API policy checks.

Changed

• Agent Core server/runtime identity and Native GitHub Fabric User-Agent advance from 0.5.4 to 0.6.0.
• Core certification has an explicit release lifecycle: prepublication proves the source before a tag exists; postpublication additionally requires the exact version-matched GitHub stable release assets and tag parity.
• Adaptive resource governance may only reduce new execution dispatch within the operator hard maximum; it never terminates already-running work or alters factual execution-result semantics.

Fixed

• Stable release parity verification invokes Git tag/source checks through git instead of accidentally routing them through the GitHub CLI.
• Stable release packaging no longer requires the removed self-fork diagram directory; dist is declared as the sole generated runtime input and release tests now require every other runtime package input to have tracked source.
• Routing least-privilege classification, capability ranking noise, deterministic memory chatter displacement, audit-journal test synchronization, and Wave A trust-boundary defects are covered by permanent regression/certification gates.

Security

• No OpenAI, Anthropic, Gemini, cloud embedding/reranking, external AI judge, hidden model-worker, or model API dependency is added by the A-G evolution.
• Detailed HTTP metrics remain loopback-only, MCP browser Origin is validated, OAuth tokens remain resource-bound, principal/project isolation remains fail-closed, and release artifacts remain allowlist-built without secrets/runtime evidence.
• Scheduled maintenance remains disabled by default and has no destructive retention-apply, restore, credential-revocation, or file-deletion call path.

Stability evidence

• Pre-version Wave G certification established the complete 18/18 core matrix, 137 test files / 668 tests passing with 38 intentional skips, 100k memory p95 well below the 150 ms gate, execution DAG/dispatch/wake p95 below 50/100/250 ms gates, 55 tools in both MCP protocol eras, and zero external model/API dependency/source violations.
• Final v0.6.0 publication evidence is recorded in docs/stability.md and the Wave G roadmap after tag/release publication, stable parity, production source-sync, public trust-boundary canary, and live audit verification complete.

Agent Core v0.5.4 - Stable

[0.5.4] - 2026-08-30 — Stable

Added

• Autonomous execution memory pre-search now recalls bounded relevant failures, decisions, conflicts, and hard guardrails from execution objectives and node purposes before create/start/dynamic-add/retry paths, without indexing raw command text; degraded memory search fails open while enforced hard guardrails fail closed before process launch.
• Execution memory pre-search has a dedicated local performance gate requiring real p95 latency below 500 ms.
• Bounded runtime observability with /health/metrics and read-only agent_core_health_metrics, deterministic rolling p50/p95/p99/max summaries, and TTL/single-flight optional GitHub health probes.
• Deterministic structured execution-output parser v1 with persisted source hashes and bounded test/build/deployment/performance/warning/error/security evidence.
• Execution schema v4 verified-artifact index with hash/type/run lookup, startup reconciliation, advisory-only reuse discovery, and review-only purge suggestions.
• Read-only execution_workflow_advice with optional route-valid proposedNext guidance and principal/project isolation.
• Local improvisation performance gates for health metrics, bounded parsing, 1000-row artifact lookup, 128-node advisor analysis, and 100000 bounded metric observations.
• Self-healing Codespaces bridge with a loopback Streamable HTTP MCP server, real protocol probes, remote registration verification, file-backed credential recovery, fixed tunnel identity, and watchdog repair for local MCP failure, stale runtime state, or repeated internal 502 responses.
• Presentation Bridge v0.2 with a shared one-screen Electron/hosted interface, real progress and cancellation, Google Slides workflows, local or remote Keynote worker support, encrypted desktop worker settings, recent jobs, setup dialogs, compatibility reporting, and restrictive CSP.
• Cross-platform stable release construction through Node.js, including a credential-free presentation-bridge-v0.2.0-source.zip alongside the Agent Core runtime/plugin ZIPs and npm package.

Changed

• Stable release ownership now targets Black-Project-Agent-Core/Agent-Core and @black-project-agent-core/agent-core-plugin; release packaging additionally emits a dedicated fresh-install ZIP containing the tracked Codespaces bootstrap/bridge contract.
• Stable publication now has an explicit remote parity gate: a package version cannot be declared complete while the GitHub Release ZIP assets remain on an older version.
• capability_route now injects a bounded deterministic projection of recalled non-guardrail memory into capability ranking and reports memoryInjection evidence, closing the gap between available DMF infrastructure and autonomous routing adoption.
• Execution-derived intelligence now documents and enforces the authority order PROCESS TRUTH > VERIFIED ARTIFACT TRUTH > PARSED STRUCTURED INTERPRETATION > ARTIFACT/CACHE SUGGESTION > WORKFLOW ADVICE; cache awareness never skips current command execution.
• Windows owned-process stop now terminates the spawned process tree so a stopped background command cannot leave descendants holding the routed working directory.
• The repository README now documents the canonical clone path, Windows and Codespaces operation, Presentation Bridge, release assets, and authenticated GitHub Packages installation.
• Stable release packaging now includes canonical Codespaces and Windows cutover documentation, deterministic source ZIP paths, an expanded manifest, and SHA-256 coverage for every distributable asset.

Fixed

• Fixed-tunnel Codespaces recovery now treats the tracked tunnel ID as authoritative, ignores stale account/machine tunnel environment overrides, and uses a repository-level Codespaces runtime credential so an authorized fresh Codespace can attach without per-account tunnel setup.
• Root Agent Core brand and documentation-link verification now stop at independent SubProject/ boundaries so legitimate subproject vocabulary or internal docs cannot block an Agent Core stable release.
• Codespaces readiness now accepts the actual server_url runtime target contract while continuing to require the exact loopback MCP URL.
• Lifecycle startup no longer treats local process health as sufficient: it verifies protocol availability, remote tunnel identity, registration freshness, and watchdog supervision before reporting ready.
• File-backed runtime credentials and tracked tunnel defaults survive environment loss, process replacement, Codespace restart, and full container rebuild without requiring manual key or tunnel export.
• Nested Codespaces package scripts now rely on the npm-provided local binary path instead of POSIX-only ./node_modules/.bin commands, allowing the complete root release gate to run on Windows and Linux.

Documentation

• Recorded the Windows installation cutover procedure and the defects found while moving the authoritative installation to a fresh canonical clone: empty runtime/data authentication stores on a clone, deletion of an ignored-path secret file required by the tracked tunnel template and launcher tests, a machine-level root locator left pointing at the previous installation, leaked tray-test processes, and a stale cutover marker asserting a success that had rolled back.

Security

• Release ZIP/TGZ construction remains allowlist-based and excludes secrets, runtime databases, logs, local capabilities, raw execution evidence, Presentation Bridge jobs, generated corpus files, caches, and credential-bearing configuration.
• GitHub REST/Git and Packages credentials remain separate, file-backed, lazily read, redacted, and absent from command arguments and release artifacts.
• Presentation Bridge preserves truthful target availability; live Google OAuth and native macOS Keynote output remain external acceptance gates rather than simulated success.

Stability evidence

• Codespaces fault injection proved automatic recovery after terminating the loopback MCP process and tunnel runtime; cold runtime reconstruction and a full Codespace rebuild restored the bridge and ChatGPT command path without user-entered recovery commands.
• Presentation Bridge verification passed its complete automated suite, doctor/isolation gates, Linux Electron smoke, restrictive-CSP contracts, rendered desktop/mobile interaction QA, and production dependency audit.
• npm run verify:release: 110 test files passed, 496 tests passed, 38 platform/performance tests skipped, release consistency passed, and 44 Markdown files with 17 relative links passed documentation validation. The Codespaces plugin additionally passed 14 files / 46 tests, while Presentation Bridge passed 45/45 tests, doctor/isolation, Linux Electron smoke, and a zero-vulnerability production audit.
• Stable publication remains local-direct with GitHub Actions/CI disabled; the exact source SHA, asset sizes, and SHA-256 digests are independently verified again after the merge and by remote read-back.

Presentation Bridge v0.2.0 RC1

Presentation Bridge v0.2.0 RC1

Draft release candidate for Windows x64 validation.

Verified before upload

• 45/45 automated tests passed
• Linux Electron smoke passed
• distributable runtime audit: 0 vulnerabilities
• distinct NSIS installer and portable artifact contracts
• SHA-256 and packaged ASAR boundary verification passed

Deliberately pending

• native Windows 10/11 smoke
• Authenticode signing and approved application icon
• live Google OAuth/native Slides acceptance
• live macOS Keynote .key acceptance

This remains a draft prerelease and is not a stable V1 declaration.