CodeAI Hub is a Visual Studio Code extension + standalone Project Manager (CEF) that unifies multiple AI providers behind a single, type-safe orchestration layer.
Current Release — v1.2.249 (Quality Gates user-return finalization repair)
This release repairs the remaining Quality Gates terminal child-plan mismatch
seen during the v1.2.248 retest. When Quality Gates integration needs more
than one managed integration commit, Core now opens
Phase 4 — Persistent Quality Gates User Return after the validated final
integration commit instead of creating another generic Phase 3 continuation.
The Quality Gates managed-plan shim now treats every validated
quality-gates.phase3.integration.taskN commit as eligible for the persistent
user-return anchor. Regression coverage locks the split-integration path:
the first incomplete integration commit may create task2, but the validated
follow-up commit must create quality-gates.phase4.user-return.task1 and must
not create quality-gates.phase3.integration.task3.
Previous release: v1.2.248 (Managed feedback dead-end repair)
This release repairs the managed feedback dead-end seen during the
v1.2.247 Application Skeleton retest. Core may still reject an invalid
managed-stage result, but provider-visible feedback no longer combines a
repairable failure with a wait-only instruction that leaves the agent with no
allowed action.
Application Skeleton Phase 3 now treats root scaffold files declared by the
accepted skeleton map, including package.json and tsconfig.base.json, as
Application Skeleton-owned materialization work. Remaining repairable
Application Skeleton boundary failures now tell the agent how to repair the
materialization boundary instead of saying “do not update / wait for Core”.
Previous release: v1.2.247 (Dynamic Quality Gates ownership rebuild)
This release repairs the remaining Quality Gates Phase 3 dead-end from
v1.2.246. Core now classifies Quality Gates materialization paths both from
the accepted quality-gates.json contract and from known QG toolchain patterns,
including scripts/qg/**, .ox*.json, and tsconfig.qg*.json.
Accepted-but-invalid Quality Gates integration feedback now remains
provider-actionable: missing .husky/pre-commit / .husky/pre-push wiring is
reported as Phase 3 repair work, not as a “do nothing and wait for Core”
lifecycle blocker. The Quality Gates prompt also makes required hook wiring
agent-owned during Phase 3, so the agent must update the hook section instead of
declaring it Core-owned pending regeneration.
Previous release: v1.2.246 (Quality Gates integration repair rebuild)
This release repairs the Quality Gates Phase 3 integration boundary seen in
v1.2.245. Core now treats the real Quality Gates materialization files,
including scripts/quality-gates/** and biome.jsonc, as stage-owned work,
keeps volatile node_modules install noise out of the managed stage blocker,
and routes accepted-but-invalid integration work back into a Phase 3 repair
task instead of a stale Phase 2 acceptance loop.
Quality Gates feedback is now provider-actionable after failed integration: the agent is told to continue materialization and wire the required Husky hook commands explicitly. The prompt and bundled contract also state that materialization is not complete until scripts, package commands, hook wiring, and accepted artifact state are all updated and ready for Core validation.
Previous release: v1.2.245 (Managed review anchor cleanup rebuild)
This release fixes the Quality Gates stall still visible in v1.2.244 and the
stale review-task leak observed during Application Skeleton retesting. Quality
Gates now derives acceptanceCommitted from the committed
workspace.plan.md ledger, matching Application Skeleton, so Core's
docs: accept quality gates contract commit can open the integration
continuation even when the JSON artifact still contains
acceptanceCommitted: false.
Managed review and user-return revisions are now injected before the managed
commit transaction, and the shim/mutator guardrails prevent generic
Continue managed ... tasks or leftover phase2.review.task2 pairs after a
single correction followed by user acceptance. Regression coverage locks the
Application Skeleton, Quality Gates, and Diagram Modules paths.
Previous release: v1.2.244 (Managed acceptance continuation rebuild)
This release fixes the remaining Quality Gates acceptance-to-integration stall
found while retesting v1.2.243. When Core accepts the Quality Gates contract
while an earlier post-turn arbitration pass is still in flight, the follow-up
continuation is now queued and replayed after that pass completes instead of
being dropped as a concurrent invocation. The result is the intended same-session
handoff from typed Подтверждаю to the Quality Gates integration prompt.
Previous release: v1.2.243 (Managed typed acceptance rebuild)
This release fixes the remaining Quality Gates acceptance stall found while
retesting v1.2.242. Production typed acceptance now dispatches by live
managed stage, so Подтверждаю in quality_gates reaches the Quality Gates
Core runner instead of disappearing in the Application Skeleton path. The
managed review prompts for Application Skeleton and Quality Gates now also end
with one exact closing sentence that asks the user either to confirm the
contract or list required revisions, without offering extra optional next
steps after the review boundary.
Previous release: v1.2.242 (Managed contract review boundary rebuild)
This release fixes the final Quality Gates review-boundary defects found while
retesting v1.2.241. The Quality Gates panel now shows a step-local Accept Contract button under quality-gates.md, draft-turn prompts ask the user to
confirm the contract or list revisions instead of asking Core for approval,
and typed contract acceptance now routes through the same Core command path
for both Application Skeleton and Quality Gates. Short acknowledgements such
as Окей or Давай дальше remain ordinary chat replies and do not silently
advance the managed plan.
Previous release: v1.2.241 (Managed handoff barrier rebuild)
This release fixes the cross-stage managed handoff defects found while retesting
v1.2.240. Core now unlocks downstream stages only after the upstream terminal
artifacts are reread and validated, while keeping the completed upstream stage
active through its own Phase 4 idle anchor and user-return loop. Diagram
Modules no longer opens Application Skeleton early, Application Skeleton no
longer opens Quality Gates from an unresolved materialization repair, and
Quality Gates opens only its idle post-completion anchor after validated
integration instead of auto-opening revision1.
Previous release: v1.2.240 (Quality Gates release retest fixes)
This release fixes the Quality Gates defects found while retesting v1.2.239.
Core now treats the Quality Gates child plan and workspace ledger as owned
artifacts during the managed acceptance flow, keeps draft and review feedback
contract-only until the Core-owned acceptance commit is complete, and blocks
the integration prompt from opening out of a failed acceptance state. The
Quality Gates child-plan mutator also renumbers review-revision task pairs
correctly, so the Phase 2 plan no longer duplicates numbered items.
Previous release: v1.2.239 (Quality Gates managed orchestration lifecycle)
This release landed the Quality Gates Baseline managed orchestration scope.
Core now drives Quality Gates through the same dynamic child-plan lifecycle as
Application Skeleton: a draft contract commit, a user-led review phase with
per-revision commits, a Core-owned acceptance commit, a separate integration
commit, and a persistent post-completion user-return revision loop. Repair
attempts inject concrete repair task-pairs and commit either valid owned diffs
or tracked attempt evidence. Stage-light truth is derived from the
workspace.plan.md acceptedCommits ledger, so completed Application Skeleton
or Quality Gates LEDs stay green even while downstream artifacts are dirty.
Previous release: v1.2.237 (Application Skeleton misplaced product-parts repair)
This release fixes the Application Skeleton repair blocker found during
v1.2.236 retesting. If the provider writes materialized product-parts/**
under .codeai-hub/<workspace>/product-parts/**, Core now sends an
actionable repair instruction to move the projection to root
product-parts/** and clean up the misplaced copy, instead of telling
the agent to wait.
Application Skeleton also stays visually pending until materialization is
really complete. A successful materialization repair commit with root
product-parts/** now opens the persistent user-return phase, creates the
Quality Gates child plan, and advances the workspace ledger to
activeStage: "quality_gates".
Previous release: v1.2.236 (Application Skeleton Quality Gates handoff recovery)
This release fixes the Application Skeleton handoff blocker found during
v1.2.235 retesting. After feat: materialize application skeleton, Core
now creates doc/TODO/stages/quality-gates/todo-plan.md before moving
the workspace ledger to activeStage: "quality_gates" and committing
the ledger update.
Diagram Modules should no longer report virtual-simulation.md not found
when the artifact exists in the provider-created alias directory.
Previous release: v1.2.234 (Managed stage isolation fix)
This release fixes the managed stage orchestration regression found
during v1.2.233 retesting. Starting Diagram Modules now creates only the
active Diagram Modules child plan, post-turn arbitration is scoped to the
active provider stage, and Core keeps product-parts.index.md on its own
commit boundary before continuing to Product Part materialization.
Previous release: v1.2.233 (Application Skeleton clean retest rebuild)
This release was a clean rebuild of the managed lifecycle upgrade fix after the retest environment was cleared of old local tails. It carried the same Application Skeleton lifecycle-boundary fix as v1.2.232 under a fresh package version so Project Manager and the extension runtime could be retested from a clean local install state.
Previous release: v1.2.232 (Application Skeleton managed lifecycle upgrade boundary)
This release fixes the managed-workspace lifecycle upgrade blocker found
during v1.2.231 retesting. When an existing managed workspace receives a
new Core-managed scripts/plan-orchestrator/plan-cli.mjs shim after
extension reinstall, Core now commits that lifecycle upgrade before
starting Application Skeleton provider work. The upgraded shim no longer
remains as out-of-stage dirty state that blocks the draft artifact commit.
Application Skeleton out-of-owner dirty feedback is also non-actionable for the provider: Core tells the agent to wait while Core repairs the managed lifecycle boundary instead of mixing lifecycle errors with artifact-edit instructions.
Previous release: v1.2.231 (Application Skeleton restart gate recovery)
This release fixes the Core restart/reinstall blocker found during
v1.2.230 retesting. Application Skeleton start-gate recovery now ignores
volatile Core metadata, including .codeai-hub/state/task-timers.json
and timestamp-only .codeai-hub/<workspace>/description/description-step.json
refreshes, when classifying managed dirty state. If the Diagram Modules
artifacts are valid on disk, Application Skeleton unlocks after Core
restart instead of showing the misleading product-parts.index.md not found readiness text.
The regression suite now reproduces a restarted Core with valid
product-parts.index.md, accepted Product Part artifacts, and only
volatile metadata dirty state, then asserts that
gating.blocked.application_skeleton remains false. The real retest
workspace was also diagnosed clean with all four Product Parts valid.
Previous release: v1.2.230 (Application Skeleton managed orchestration)
Application Skeleton now uses the managed dynamic plan lifecycle. The generated child plan starts with the draft contract task and grows at runtime for Core rejection repairs, review revisions, explicit acceptance, materialization, and post-completion user-return revisions. Acceptance and materialization are committed at separate boundaries, and invalid retry attempts write tracked evidence under the workspace revision tree instead of disappearing into runtime state.
Previous release: v1.2.229 (Diagram Modules user-return revisions)
This release fixes the post-completion Diagram Modules return loop from
v1.2.228. After all Product Parts are accepted, Phase 2 now opens an
always-current diagram-modules.user-return.revisionN.task1 with a
paired Git Commit instead of an idle no-commit anchor. User-requested
revisions, such as updating the Project Manager Product Part from an
external document, are now committed through the managed boundary and
the next revision task is opened immediately afterward.
The managed commit transaction and installed plan shim both have
regression coverage for the release-blocker path: final Product Part
commit creates revision1, committing that revision creates
revision2, and a dirty product-parts/project-manager.md change is
committed instead of being left as pending Core-owned dirty state.
Previous release: v1.2.228 (Diagram Modules managed repair orchestration)
This release makes Diagram Modules managed-step orchestration durable
when Core rejects an agent turn. Core now injects a dedicated
repairN microtask pair before provider-visible correction feedback,
commits each repair attempt even if the artifact is still invalid, and
writes tracked attempt evidence under the workspace revision tree so
failed tries do not disappear into runtime state. Product Part commits
no longer count dirty repair artifacts as accepted Product Parts.
The post-completion Diagram Modules phase is now a persistent
user-return surface rather than a one-shot review commit. After all
Product Parts are accepted, the child plan remains open for future
user-requested revisions, while the workspace ledger separately unlocks
Application Skeleton. A deterministic forced-rejection integration test
covers the full path: invalid Product Part, repair task injection,
repair feedback, tracked evidence, managed commit, and clean temp
workspace.
Previous release: v1.2.227 (handoff anchor regex fix for v1.2.226)
This release fixes the last missing pin of the Application Skeleton
phase orchestration: the Phase 4 handoff seed line in
managed-todo-tree.ts did not contain the literal expected commit:
substring (it only said "no commit required" inside the scope clause),
so the post-Stream-A TASK_LINE_RE could not match it. After Phase 3
materialize commit, advancement could not find the next task line and
fell into the fallback-insert branch, synthesizing a spurious
phase3.materialize.task2 continuation pair with the same commit
message — visible as a duplicate Pin 7 in the user plan and a stuck
IN_PROGRESS continuation. The fix adds expected commit: none — reserved handoff anchor inside the parenthetical scope clause of the
handoff seed line. After the fix, advancement after Phase 3 materialize
lands cleanly on application-skeleton.handoff.task1 with
expectedCommitMessage: null; the workspace stage transition
(recordWorkspaceCommit) then switches activeStage to
quality_gates through the normal path. End-to-end Application
Skeleton orchestration (Phase 1 → 2 → 3 → 4 handoff → Quality Gates)
now completes cleanly.
Previous release: v1.2.226 (acceptance callback wiring fix for v1.2.225)
This release closes the production wiring gap that left v1.2.225's
acceptance write-path unreachable at runtime. The Phase 24 writer +
runner were correctly implemented and unit-tested, but the typed-fallback
router's optional handleManagedAcceptContractCommand callback was
never assigned anywhere in production code — only the read site in
session-request-handler-message-dispatch.ts existed, leaving the
optional chain a silent no-op. As a result, typing "Контракт принимаю,
можешь продолжать" or "accepted" got intercepted by the recognizer,
logged as Skipping managed contract acceptance phrase, and dropped on
the floor. No runner, no map.json patch, no Phase 2 commit, no Phase 3
continuation. The fix adds the late-bound callback at the
remote-bridge-bootstrap.ts composition site (mirroring the existing
onTurnCompleted pattern), threads it through
SessionRequestHandlerOptions and the runtime deps interfaces, and
hands it to the SessionRequestHandlerMessageDispatch factory. The
end-to-end flow now executes as designed.
Previous release: v1.2.225 (acceptance write-path fix for v1.2.224)
This release closes the last missing piece of the Phase 16 Option C
acceptance flow: the accepted: true write on
application-skeleton-map.json. Before v1.2.225, every acceptance entry
point (PM Accept Contract button via HTTP endpoint, typed-fallback
recognizer with broadened verbs, Core accept-contract handler decision)
only set the in-memory recentlyAcceptedSessions Set. Nobody patched
the map file. The Phase 3 continuation dispatcher (Stream 16D Option C)
gates on progress.accepted === true reading the file, so it never
fired. User-typed "accepted" was silently intercepted by the typed-
fallback router with no follow-up turn, no Phase 2 accept commit, and
no Phase 3 materialization prompt.
The fix introduces a single-owner writer module
(application-skeleton-acceptance-writer.ts) that patches the map file
to accepted: true (and reviewState: "accepted" for draft maps;
materialized maps preserve their reviewState). The Core accept-contract
runner calls it on kind: "accepted", so both the PM button (via HTTP
endpoint) and the typed-fallback router funnel through the same writer.
The patched file becomes a dirty Application Skeleton-owned artifact;
the managed commit gate auto-commits docs: accept application skeleton contract (Phase 2 commit); the next read-model snapshot reports
progress.accepted === true; the Phase 3 dispatcher fires the
materialization continuation prompt to the agent.
- SolidWorks-WorkFlow docs index:
doc/SolidWorks-WorkFlow/Docs_Index.md - System SSOT:
doc/SolidWorks-WorkFlow/System/SystemArchitecture.md - Session input lock SSOT:
doc/SolidWorks-WorkFlow/Contracts/SessionInputLock_SSOT_StateMachine.md - Bug registry:
doc/BugRegistry.md
CodeAI Hub is already usable, but the current recommended installation path is still source-based. If you want to try the product today, clone the repository, build the release artifacts locally, and install the generated VSIX into Visual Studio Code.
- Git
nvm- Node.js per the project
.nvmrc(currently22.17.0) +npm - Visual Studio Code
cmake(required for the standalone CEF launcher / Project Manager build)- the provider CLIs or SDK access you plan to use (
Claude,Codex,Gemini) installed and authenticated separately
git clone https://github.com/OleynikAleksandr/CodeAI-Hub.git
cd CodeAI-Hub
nvm install # reads .nvmrc and installs the pinned Node version
nvm use
npm install
npm run setup:hooks
./scripts/build-all.sh
./scripts/build-release.sh --use-current-version- VSIX package in the repository root:
codeai-hub-<version>.vsix - fresh runtime tarballs in:
doc/tmp/releases/~/.codeai-hub/releases/
Open Visual Studio Code and run Extensions: Install from VSIX..., then select the generated codeai-hub-<version>.vsix.
- This is the current early-access path, not a polished one-click installer.
- The first full build can take a while because it prepares provider bundles, UI bundles, core runtime, and the standalone launcher.
- Provider CLIs / SDKs are not bundled inside this repository and must be available separately.
Before starting, read doc/SolidWorks-WorkFlow/Docs_Index.md and follow the SSOT contracts in doc/SolidWorks-WorkFlow/Contracts/ (especially doc/SolidWorks-WorkFlow/Contracts/Workflow_CLI.md) to configure provider CLIs and SDKs.
- Install dependencies
npm install npm run setup:hooks # installs Husky git hooks - Implement changes in
src/andpackages/**(micro-classes + facades; keep files under 500 lines). - Run quality checks before committing:
npm run quality # architecture gate + Ultracite lint npm run check:knip # detect unused files/exports npm run compile # ensure TypeScript builds cleanly
- GitHub Actions now runs a minimal public CI baseline on every push to
mainand on every pull request. - The workflow enforces the same root quality gates used as the local baseline:
npm run check:architecture,npm run lint,npm run check:knip, andnpm run compile. - The root
compilegate now builds@codeai-hub/translation,@codeai-hub/localization, and@codeai-hub/core-supervisorbefore browser/root type-check, so clean GitHub runners do not depend on pre-existing workspacedist/folders. - Local Husky hooks remain the fastest feedback path; CI is the public verification surface, not a replacement for the local release ritual.
./scripts/build-all.sh
./scripts/build-release.sh --use-current-versionmedia/ Bundled webview assets (CSS + JS) shipped with the extension.
media/react-chat.js React bundle generated by the webview build script.
src/extension.ts VS Code extension entry point.
src/extension-module/ Extension host micro-classes (settings, bootstrap glue).
src/core/webview-module/ HTML scaffold that injects the webview assets.
src/client/project-manager/ Project Manager CEF UI surface (sidebar, sessions, settings).
src/client/ui/ Shared session UI bundle (used by both webview and PM shells).
src/types/ Shared TypeScript types (provider, session, model registries).
packages/ Workspace packages — provider modules and runtime services.
packages/Claude_Module/ Claude provider runtime (Agent SDK integration, session lifecycle).
packages/Codex_AppServer_Module/ Codex provider runtime (App Server JSON-RPC, app-server process).
packages/Gemini_Module/ Gemini provider runtime (CLI core integration).
packages/core/ Core orchestrator (turn lifecycle, continuity, remote bridge).
packages/core-supervisor/ Runtime supervisor (Core process management).
packages/cef-launcher/ Standalone CEF Launcher (native macOS/Windows/Linux client for PM).
packages/ui/ Project Manager UI styles + bundled assets.
packages/translation/ Shared runtime translation engine.
packages/localization/ Bundled English source dictionaries + glossary + lookup primitives.
packages/unified-session/ Shared session contract used across packages.
scripts/ Quality, build, and release automation (build-all.sh, build-release.sh, etc.).
doc/ Architecture SSOT, planning docs, sessions log, knowledge base.
doc/SolidWorks-WorkFlow/ Canonical SSOT tree (System / Clusters / Modules / Contracts / DesignSystem / Plans).
doc/tmp/releases/ Locally staged release tarballs after build-all.sh.
This repository is currently distributed as UNLICENSED. Source is visible for audit and development collaboration, but redistribution requires explicit permission from the repository owner.