ISSUE: Node Experimental Warning on Windows PowerShell

[PVLPM]

When I try to start CodeBurn in PS, I see the next thing:

PS C:\Users\User> codeburn
(node:47364) ExperimentalWarning: SQLite is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

If I press Ctrl+C, I get an interface for a second, and then it aborts.

[iamtoruk]

Thanks for the report. Two separate things going on here:

1. ExperimentalWarning
We suppress this on latest main — if you're on v0.9.5 from npm it should already be silenced. Can you confirm with codeburn --version? If it still shows, it might be a Windows-specific edge case with our process.emit patch.

2. Dashboard hangs, flashes on Ctrl+C
This is the real issue. The interactive dashboard uses Ink which needs raw-mode stdin. PowerShell sometimes doesn't hand over the terminal correctly, so the TUI waits for input that never arrives.

Quick workaround — pipe to force static output:

codeburn today | more

Or use the non-interactive status command:

codeburn status

What's your Node version (node --version) and codeburn version (codeburn --version)?

[PVLPM]

Thanks for the fast response. I just installed Codeburn, so it's 0.9.5. I confirm that.

PS C:\Users\User> codeburn --version
0.9.5
PS C:\Users\User> node --version
v22.14.0

And this is what I get from codeburn today | more and codeburn status commands

[iamtoruk]

Good to know the workarounds work. Both issues are confirmed:

ExperimentalWarning: The suppression is in v0.9.5 but appears to not work on Windows — Node may be writing the warning at the native level before our JS-level patch can intercept it. We'll fix this with --no-warnings=ExperimentalWarning in the CLI entrypoint which catches it at the Node level instead.

Interactive dashboard hanging: This is an Ink (the TUI library) issue with raw-mode stdin on Windows PowerShell. process.stdin.isTTY reports true but raw mode doesn't behave correctly, so the dashboard waits for input that never arrives. We'll add a fallback for this.

For now, codeburn status is the best experience on Windows — it gives you the same data without needing interactive mode. Will update here when both fixes land.

[iamtoruk]

Mean while can you please check this as you are already using windows.

The Windows menubar app is ready for testing on the feat/windows-menubar-tauri branch. It's a native system tray app built with Tauri (same React frontend as the macOS version).

What's included:

System tray icon with popup dashboard (spending, trends, activity, tips)
Dark/light theme toggle via right-click menu
Runs in background, refreshes automatically
No console window flash on data refresh
To try it:

git clone https://github.com/getagentseal/codeburn.git
cd codeburn
git checkout feat/windows-menubar-tauri
cd desktop
npm install
npm run tauri dev
Requires: Node.js, Rust toolchain, and the Tauri prerequisites for Windows.

Or if you just want to build a release binary:

npm run tauri build
The .msi installer will be in desktop/src-tauri/target/release/bundle/msi/.

Would appreciate feedback on any issues - especially around tray icon behavior, theme rendering, and data accuracy. Once it's solid we'll merge to main and add codeburn menubar support for Windows.

[iamtoruk]

Both issues are fixed on main now (c511627).

ExperimentalWarning: Turned out the process.emit patch had a timing bug. Node defers the warning via process.nextTick, but we were restoring the original emitter synchronously in the finally block. By the time the warning actually fires, our patch was already gone. Fixed by delaying the restore by one tick so it stays active long enough to intercept.

Dashboard hang: Ink v7 wraps every render frame in DEC mode 2026 synchronized output markers (BSU/ESU). ConPTY on Windows does not implement this protocol, so it buffers forever waiting for a sequence it can't process. That's why nothing renders, and Ctrl+C shows a flash of output (Ink's unmount writes directly without BSU/ESU). Fixed by intercepting the two specific escape sequences on Windows before they reach stdout. Full interactivity is preserved, keyboard, live refresh, cursor, everything works the same.

Can you pull main and test?

npm install -g codeburn@latest
codeburn

Both the warning and the hang should be gone. Let me know how it goes.

[iamtoruk]

Correction on the install step - the fix is on main but not published to npm yet. To test it now:

git clone https://github.com/getagentseal/codeburn.git
cd codeburn
npm install
npm run build
node dist/cli.js

Will publish to npm once you confirm it works on your end.

[PVLPM]

Unfortunately, it still hangs up until I press Ctrl + C, and then the dashboard is shown for a moment as it was before.

[PVLPM]

So, how can we use CodeBurn on Windows/PowerShell?

PS C:\Users\User\codeburn> codeburn --version
0.9.6
PS C:\Users\User\codeburn> codeburn
PS C:\Users\User\codeburn> codeburn

Still nothing happens until I press the Ctrl+C. Just previous error is gone.