Repository navigation
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:installreplaces an existing build with the same version. Verified build directories and transactional registration preserve the previous build for rollback. - Fix npm 12
EALLOWSCRIPTScaused 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 installFor pnpm:
pnpm add -g @aectooling/revcode@0.1.4
revcode installIf 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.