Revcode 0.1.4

Revcode 0.1.4

Changes since 0.1.3

• Chat replies show a live elapsed timer and subtle divider. Completed durations survive reloads.
• Tool calls appear inline with status, expandable input/output, and the latest three calls visible by default. Failed calls open automatically. View tools opens the execution inspector even when collapsed.
• Start a new thread from the collapsed desktop rail or mobile top bar.
• Delete individual threads after confirmation. The archive manager supports deletion by age and shows the actual journal and run/image storage paths with copy buttons. Running work and unresolved native outcomes are protected; interrupted deletion resumes on restart.
• Local npm run build:install replaces an existing build with the same version. Verified build directories and transactional registration preserve the previous build for rollback.
• Fix npm 12 EALLOWSCRIPTS caused by inherited npm configuration during payload installation and release preparation. User configuration files remain unchanged.
• Consolidate thread protection and draft restoration, share host/UI history types, and remove stale or duplicate maintainer documentation. Compiler checks reject unused locals and parameters; release builds reuse checked-in versioned notes.

Install or upgrade after publication

Close Revit, then run in PowerShell:

npm install -g --allow-scripts=@aectooling/revcode @aectooling/revcode@0.1.4
revcode install

For pnpm:

pnpm add -g @aectooling/revcode@0.1.4
revcode install

If a local development build already uses version 0.1.4, explicitly replace it with revcode install --replace-same-version. Normal published-package installs still reject different contents under the same version unless replacement is requested. Local build:install enables replacement automatically.

Settings, saved skills, and existing history are preserved on upgrade. Thread deletion is permanent and removes that thread's saved messages, tool logs, and attached images; it does not undo Revit edits or delete saved skills or unrelated manual execution history.

Compatibility and limitations

Windows x64, built-in Windows tar.exe, and Node.js 22.19 or newer for installation and CLI management. The application bundles Node and self-contained helpers. Revit 2025 uses .NET 8; Revit 2026 requires 2026.5 or newer on .NET 10; Revit 2027 uses .NET 10. Exact supported build ranges are recorded in the release artifact. Binaries are unsigned.

History remains separate for each Revit instance. Separate thinking blocks and tool-result image galleries in the chat transcript are not included in this release; captures remain available in the desktop and execution panels.

Release preparation

The PR received a source review focused on deletion recovery, stale requests, installer identity, rollback, and UI state. Tests and smoke checks are explicitly skipped for final release preparation at the maintainer's request. Existing PR CI results and earlier development checks do not validate the final release artifact. Packaging still builds the application and records payload and archive integrity hashes.

Source: 2c3dd68

Revcode binaries: unsigned.

Revcode 0.1.3

Revcode 0.1.3

Source: d529a58

Revcode binaries: unsigned.

Changes since 0.1.2

• Fix Windows installation failing during cli.mjs postinstall with ExtractToDirectory: Illegal characters in path. Payload extraction now uses Windows' built-in tar.exe instead of PowerShell's .NET ZIP extractor.
• Pass the archive through a file handle and set the extraction working directory directly, supporting Unicode profile paths and long nested dependency paths without command-line path conversion.
• Add an explicit maintainer option to prepare releases without tests or smoke checks. The release receipt records skipped validation; publishing preserves that choice.

Install or upgrade after publication

Close Revit, then run in PowerShell:

npm install -g --allow-scripts=@aectooling/revcode @aectooling/revcode@0.1.3
revcode install

For pnpm:

pnpm add -g @aectooling/revcode@0.1.3
revcode install

The explicit install command handles blocked lifecycle scripts or pending activation. Existing settings and history are preserved. Users whose 0.1.2 installation failed can install 0.1.3 directly.

Compatibility

Windows x64 with the built-in Windows tar.exe and Node.js 22.19 or newer for installation and CLI management. The application bundles Node and self-contained helpers. Revit 2025 uses .NET 8; Revit 2026 requires 2026.5 or newer on .NET 10; Revit 2027 uses .NET 10. Exact supported build ranges are recorded in the release artifact. Binaries are unsigned.

Release validation

Tests and smoke checks were explicitly skipped for this release preparation at the maintainer's request. Earlier installer-fix validation is not a test of the final 0.1.3 artifact. Packaging still builds the application and records payload and archive integrity hashes.

Revcode 0.1.2

Revcode 0.1.2

Source: f7ff734

Revcode binaries: unsigned.

Changes since 0.1.1

• Add persistent conversation threads with separate agent context and run history, automatic titles and date grouping, archive/unarchive, and independent selection in multiple browser tabs. Switching threads preserves unsent text, image attachments, and drawing scenes while the page stays open. Existing history appears in a legacy thread.
• Add Excalidraw drawings and image annotations. Upload, paste, or drop supported images; annotate them with shapes, arrows, text, and freehand strokes. Adjust reference-image opacity, reopen drawings, and capture the active Revit view. Editor assets and fonts are bundled locally.
• Fix Capture active view incorrectly rejecting the active model when Revit returns different managed wrappers for the same document. The capture guard now uses document equality while retaining the active-view check.
• Reduce the release payload by removing dependency source maps/type declarations and non-Windows-x64 ZeroMQ binaries. Packaging validates the staged host and production dependencies before sealing the artifact.
• Make Windows build/install launcher tests tolerate slow PowerShell startup and include subprocess errors, signals, and output in failure diagnostics.

Install or upgrade after publication

Close Revit before activation, then run:

pnpm add -g @aectooling/revcode@0.1.2
revcode install
revcode doctor

The explicit install command also handles blocked lifecycle scripts or pending registration. Existing settings and history are preserved. Installing a new npm version does not update already-running Revit processes.

Compatibility and limitations

• Windows x64. Node.js 22.19 or newer is required for package management and CLI bootstrap; the application uses bundled Node and self-contained native helpers.
• Packaged targets: Revit 2025 build 25.4.41.14 or newer on .NET 8; Revit 2026 build 26.5.0.55 or newer on .NET 10; Revit 2027 build 27.0.10.13 or newer on .NET 10. Installation checks the packaged year, build range, and runtime. Revit 2025 on .NET 10 is not included.
• Binaries are unsigned and may trigger Revit's standard add-in prompt.
• Only one thread can run at a time. History survives host restarts within the same Revit instance; separate Revit instances have independent histories. Unsent drafts and drawing scenes are lost on page reload.
• Sending images requires an image-capable model. Native captures and desktop screenshots sent to a model go to the selected provider. Desktop automation remains experimental.
• C# executes with full trust inside Revit. Use disposable models for testing; an uncertain native operation requires inspection before further execution.

Validation

• The capture-fix PR passed full CI before merge. The final release build passed typechecking, 137 source tests, native tests, .NET 8/10 transport checks, and 16 deployment tests.
• All 137 staged-payload tests passed for the final build; all three Revit add-ins were built with locked dependencies.
• The first candidate passed all four npm/pnpm tarball installation modes and a local upgrade from 0.1.1 with doctor reporting no problems.
• Live Revit 2026.5 testing passed queries, compiler diagnostics, committed edits, and rollback checks. It exposed the active-view capture comparison bug; the corrected generated capture code then exported the view successfully in Revit.
• The final rebuilt candidate has not repeated the local upgrade or full live UI smoke test; further live testing was skipped at the maintainer's request. Revit 2025 and 2027 were built but not live-tested for this release. No real-provider conversation was sent.

Revcode 0.1.1

Revcode 0.1.1

Source: c9f24d6

Revcode binaries: unsigned.

Version 0.1.1 prepares the first scoped npm release as @aectooling/revcode and fixes release packaging and publication. The CLI command remains revcode.

Changes since 0.1.0

• Move the npm package from revcode to @aectooling/revcode, with updated installation and removal instructions. The existing v0.1.0 tag and draft artifacts are preserved as the abandoned unscoped candidate.
• Fix isolated tarball tests to select the configured pnpm version through Corepack and approve local tarball lifecycle scripts using pnpm's source identity. Package lookup now supports the scoped name.
• Fix GitHub draft-release lookup during publication by resolving the release ID before checking its notes and assets.
• Remove the mandatory acceptance.json file from the release workflow and uploaded assets. Manual live-test notes are optional; automated tests, source verification, signing-policy checks, and artifact-integrity checks remain required.

Install after npm publication

Close Revit before activation, then run:

pnpm add -g @aectooling/revcode@0.1.1
revcode install
revcode doctor

The explicit revcode install command also handles blocked package-manager lifecycle scripts or pending registration. Settings and history are preserved by removal; use revcode uninstall before removing the global package.

Compatibility and known limitations

• Windows x64; Node.js 22.19 or newer is required for installation and CLI management. The application uses bundled Node and self-contained helpers.
• Configured Revit targets: 2025 on .NET 8, 2026.5+ on .NET 10 (build 26.5.0.55 or newer), and 2027 on .NET 10. Installation checks the exact build and runtime against the packaged metadata. Revit 2025 on .NET 10 remains deferred.
• Revcode binaries are configured as unsigned for this release and may trigger Revit's standard add-in prompt.
• Revcode remains an early, full-trust prototype. C# runs inside Revit; test with a disposable project. Desktop automation is experimental, and live validation across all supported Revit targets remains a separate manual check.

See the deployment guide for compatibility details, rollback, removal, and the artifact publication workflow.

Packaged minimum Revit builds

• Revit 2025: 25.4.41.14, .NET 8.
• Revit 2026: 26.5.0.55, .NET 10.
• Revit 2027: 27.0.10.13, .NET 10.