Repository navigation
codebase-memory-mcp-ui-windows-amd64 doesn't provide ui function #795
Description
Version
codebase-memory-mcp --0.8.1
Platform
Windows (x64)
Install channel
GitHub release archive / install.sh / install.ps1
Binary variant
ui
What happened, and what did you expect?
PS D:> cd D:\Software\codebase-memory-mcp\codebase-memory-mcp-ui-windows-amd64
PS D:\Software\codebase-memory-mcp\codebase-memory-mcp-ui-windows-amd64> .\install.ps1 --ui
codebase-memory-mcp installer (Windows) variant: ui target: C:\Users\oceanskyfly\AppData\Local\Programs\codebase-memory-mcp\codebase-memory-mcp.exe Downloading codebase-memory-mcp-ui-windows-amd64.zip... Checksum verified. Extracting...
Installed: codebase-memory-mcp 0.8.1
Configuring coding agents...
Agent configuration failed (non-fatal).
Run manually: codebase-memory-mcp install
Done! Restart your terminal and coding agent to start using codebase-memory-mcp.
PS D:\Software\codebase-memory-mcp\codebase-memory-mcp-ui-windows-amd64> .still has problems:PS C:\Users\oceanskyfly> codebase-memory-mcp --ui=true --port=9749
level=info msg=mem.init budget_mb=8106 total_ram_mb=16212
codebase-memory-mcp: --ui requested, but this binary was built without the embedded UI, so the HTTP server will not start.
Use the UI release asset (codebase-memory-mcp-ui) or rebuild with: make -f Makefile.cbm cbm-with-ui
Reproduction
PS C:\Users\oceanskyfly> codebase-memory-mcp --ui=true --port=9749
level=info msg=mem.init budget_mb=8106 total_ram_mb=16212
codebase-memory-mcp: --ui requested, but this binary was built without the embedded UI, so the HTTP server will not start.
Use the UI release asset (codebase-memory-mcp-ui) or rebuild with: make -f Makefile.cbm cbm-with-ui
Logs
PS C:\Users\oceanskyfly> codebase-memory-mcp --ui=true --port=9749
level=info msg=mem.init budget_mb=8106 total_ram_mb=16212
codebase-memory-mcp: --ui requested, but this binary was built without the embedded UI, so the HTTP server will not start.
Use the UI release asset (codebase-memory-mcp-ui) or rebuild with: make -f Makefile.cbm cbm-with-ui
Diagnostics trajectory (memory / performance / leak issues)
PS C:\Users\oceanskyfly> codebase-memory-mcp --ui=true --port=9749
level=info msg=mem.init budget_mb=8106 total_ram_mb=16212
codebase-memory-mcp: --ui requested, but this binary was built without the embedded UI, so the HTTP server will not start.
Use the UI release asset (codebase-memory-mcp-ui) or rebuild with: make -f Makefile.cbm cbm-with-ui
Project scale (if relevant)
No response
Confirmations
- I searched existing issues and this is not a duplicate.
- My reproduction uses shareable code (a dummy snippet or a public OSS repository), not proprietary code.
Activity
phpmac commentedon Jul 3, 2026
v12 pls audit
DeusData commentedon Jul 3, 2026
Thanks for the Windows UI report. Triage: this is a Windows/UI packaging or launch-path bug, tracked under the Windows platform work (#394) and UX/install track (#396).
The expected behavior is simple: the UI variant should either start the local UI server successfully or fail with a clear actionable error. We need to verify the archive contents, install target,
--uihandling, and whether this overlaps with the earlier Windows UI listener issue #707.github-actions commentedon Jul 8, 2026
Thanks for the report! To move this forward we need a bit more so we can reproduce it ourselves:
codebase-memory-mcp --versionyou're onOnce that's here we'll pick it straight back up. Heads-up: issues left
awaiting-reporterare automatically closed after a few weeks of silence, but a comment reopens the door anytime.DeusData commentedon Jul 8, 2026
v0.9.0 includes the refreshed UI packaging plus Windows UI reliability fixes. Could you retest the Windows UI archive flow on v0.9.0 and confirm whether it is still broken? Marking awaiting-reporter.
pedrocastellanos commentedon Jul 14, 2026
I am getting same issue:
codebase-memory-mcp --ui=true --port=9749
level=info msg=mem.init budget_mb=3926 total_ram_mb=15706
level=info msg=server.start version=0.9.0
codebase-memory-mcp: --ui requested, but this binary was built without the embedded UI, so the HTTP server will not start.
Use the UI release asset (codebase-memory-mcp-ui) or rebuild with: make -f Makefile.cbm cbm-with-ui
level=warn msg=ui.no_assets hint=rebuild_with:make-f_Makefile.cbm_cbm-with-ui
level=info msg=watcher.start interval_ms=multi-sec
DeusData commentedon Jul 14, 2026
Thanks for confirming this still occurs on v0.9.0. I have removed awaiting-reporter and returned the issue to the maintainer queue. The message shows that the executable found on PATH is the standard build without embedded UI assets, so the next check is the exact downloaded archive name plus the output of where codebase-memory-mcp and the executable file size, to determine whether the UI archive installs the wrong binary or an older standard binary is shadowing it.
Alvin999888 commentedon Jul 19, 2026
I have used Traework + GLM5.2 to do the bug analysis, please review the report in the attached fiels. codebase-memory-mcp_issue795_bug_analysis_report_EN_V2.0.md. I hope this can help our community project devlopment team to solve the bug. Thanks.
DeusData commentedon Jul 22, 2026
Thanks for preparing the analysis. For security and reproducibility, we do not feed unreviewed agent-generated attachments directly into maintenance tooling. Could you summarize the concrete suspected root cause, relevant repository file and line references, and the smallest proposed RED reproduction directly in this issue? We can then verify each claim against the current source without treating instructions embedded in an attachment as trusted.
DeusData commentedon Sep 26, 2026
Thank you, @Alvin999888 and @pedrocastellanos, for sticking with this!
Releases no longer ship separate "standard" and "ui" builds. From v0.11.0 on, every release binary embeds the UI: the two windows-amd64 archives are the same build (identical size), and
--portserves the dashboard from the regular binary. So a v0.11.0 download should no longer be able to show "built without the embedded UI".Could you install v0.11.0 and confirm that the UI starts? If you still see that message, please post the output of
where codebase-memory-mcpand the file size of each result. An older binary earlier on your PATH would be our first suspect.github-actions commentedon Sep 26, 2026
Thanks for the report! To move this forward we need a bit more so we can reproduce it ourselves:
codebase-memory-mcp --versionyou're onOnce that's here we'll pick it straight back up. Heads-up: issues left
awaiting-reporterare automatically closed after a few weeks of silence, but a comment reopens the door anytime.github-actions commentedon Oct 18, 2026
This issue has been waiting on more information for 21 days (a version, exact steps, or a public repro), so it's now marked
stale. It will not be closed automatically — a maintainer reviews stale issues by hand. Adding a comment with the details clears the label and puts it straight back in the queue. We're happy to pick it back up the moment we can reproduce it.DeusData commentedon Oct 19, 2026
Thank you again for the Windows UI reports. Checking back on the September request: does the current binary still report that the UI is not embedded? If so, please include its version and the executable paths returned by
where codebase-memory-mcp; there is no need to produce another analysis attachment.DeusData commentedon Oct 25, 2026
Thank you again for the report. If the UI-not-embedded error still occurs, please share the current version and executable path; another analysis attachment is not needed.