magic context tui or sidebar disappeared when i updated to the latest version

[vicXvac]

Short description

the magic context side bar is not showing

What happened?

previously before i updated to the latest version (it automatically updated), the magic context and the aft were showing just fine
magic context up and then the aft stats underneath it, then the thing automatically updated and then i could not see magic context
things in the sidebar, the command like ctx-* are still visible and are functioning and the plugins installed show both the aft and the
magic context when i run /status but when i run ctrl + p to see plugins, i only see aft among the external plugins and dont see the
magic context one, its as though it has just disappeared, the plugin is registered both in my opencode.json and also in the tui.json as
well

Diagnostics

:~$ npx @cortexkit/magic-context@latest doctor --issue
│
●  Detected OpenCode — using it for diagnose.
│
◇  Running doctor for OpenCode…
┌  Magic Context Issue Report
│
◇  Issue title
│  magic context tui or sidebar disappeared when i updated to the latest version
│
◇  Issue description
│  previously before i updated to the latest version (it automatically updated), the magic context and the aft were showing just fine 
magic context up and then the aft stats underneath it, then the thing automatically updated and then i could not see magic context 
things in the sidebar, the command like ctx-* are still visible and are functioning and the plugins installed show both the aft and the
 magic context when i run /status but when i run ctrl + p to see plugins, i only see aft among the external plugins and dont see the 
magic context one, its as though it has just disappeared, the plugin is registered both in my opencode.json and also in the tui.json as
 well
│
◇  Diagnostics collected
│
◇  Report written to /home/vicafricode/magic-context-issue-20260721-224419.md
│
◇  Submit this issue on GitHub now?
│  Yes
│
▲  gh CLI not found — falling back to browser
│
●  Open this URL and paste the contents of /home/vicafricode/magic-context-issue-20260721-224419.md into the Diagnostics field:
│
●  https://github.com/cortexkit/magic-context/issues/new?title=magic%20context%20tui%20or%20sidebar%20disappeared%20when%20i%20updated%20to%20the%20latest%20version&template=bug_report.yml
│
└  Issue report ready

Plugin version

0.32.4

OpenCode version

1.18.4

Platform

ubuntu

Client

OpenCode TUI (CLI)

Log output (optional)

[ualtinok]

Thanks for the report. We audited OpenCode 1.18.x with the OpenCode team and found no host-side change that would explain this — but we do have a strong suspect on our side: the plugin's auto-updater briefly removes the active package directory while installing a new version, and if the TUI process loads during that window it can miss the sidebar entry while the server half (already loaded in memory) keeps working. That matches your symptom exactly: /status shows the plugin, ctx-* commands work, but ctrl+p has no Magic Context TUI entry.

Two things that would help confirm, and likely fix it immediately:

1. Fully quit OpenCode (all windows/instances), start it once with opencode --print-logs, and check for a line starting with [tui.plugin] — if one appears, please paste it here.
2. If the sidebar is back after that clean restart, the update race is confirmed — we're preparing a fix that makes the update atomic so this can't recur.

Either way the log line (or its absence) settles it.

[marcelauer]

Hi, I can confirm this bug, also occured after the update (as already stated ctx-* commands still work). I started it with --print-logs and got no line starting with [tui.plugin]. The Magic Context sidebar entry is still missing. Since then I also rebooted my laptop, without any effect, the sidebar entry is not showing up anymore.

[vicXvac]

i followed the steps

1. Clean restart:
   pkill -f opencode
   ps aux | grep opencode # confirmed nothing running
   opencode --print-logs

2. Checked for the [tui.plugin] line:
   grep -i 'tui.plugin' ~/.local/share/opencode/log/opencode.log

This returns zero results — not even a failure/error variant of that line, just nothing at all.

3. Sidebar after the clean restart: still only shows the AFT panel. No Magic Context entry, same as before.
   A couple of things that might be relevant to narrowing this down:

I'm on plugin version 0.32.4 (confirmed via magic-context doctor, which passes 13/13 with no warnings — DB, embedding endpoint, and ctx-* commands all working fine).
Since the log never shows a [tui.plugin] line at all, even after a fully clean start, the update-race theory may not fully explain what's happening on my end — a race would still leave some trace (success or failure) at TUI boot, but there's nothing there.
doctor reports "TUI sidebar plugin configured" as a pass, and my tui.jsonc does list the plugin correctly, so it looks like the plugin is registered as expected — it just never seems to produce the actual sidebar widget or the log line tied to it.

[ualtinok]

Thank you both — this is exactly the evidence we needed, and it rules out our first theory. A clean restart with zero [tui.plugin] output (not even a failure line) means the TUI loader is skipping the Magic Context entry before it ever attempts to load it — this is not the update race we suspected, since AFT's sidebar loading in the same session proves the TUI plugin path itself is working.

We're tracing the exact enumeration path in OpenCode 1.18.4 with the OpenCode team now. One thing would help pin it precisely: could either of you paste the exact plugin entry lines (just those lines, nothing sensitive) from BOTH files:

1. ~/.config/opencode/tui.json (or .jsonc) — the entry under plugin
2. ~/.config/opencode/opencode.json (or .jsonc) — the entry under plugin

We suspect the interaction between the two entries (the TUI process reads both files and deduplicates by package name), so the exact spec strings in each file matter. A workaround may be possible via a config edit once we confirm the mechanism — we'll post it here as soon as we have it.

[ualtinok]

Update from tracing this with the OpenCode team — narrowing steadily:

• The published 0.32.4 package has been verified clean through OpenCode's real resolver, TUI entry selection, import, and shape validation in an isolated environment. The package loads correctly; this is a configuration/origin-merging issue, not a broken plugin build.
• Correction to our earlier ask: a SUCCESSFUL TUI plugin load prints no [tui.plugin] line at all, so the empty grep result doesn't tell us anything by itself. The meaningful signal is the plugin manager list (Ctrl+P).

Three asks that will pin this down (either reporter):

1. Ctrl+P → plugin list: is Magic Context completely ABSENT, or listed as disabled/inactive? (These are different bugs.)
2. The exact raw plugin lines from: ~/.config/opencode/tui.json(.jsonc), ~/.config/opencode/opencode.json(.jsonc), plus any project-level .opencode/tui.json or tui.json in the project you launch from — and whether any of OPENCODE_TUI_CONFIG, OPENCODE_CONFIG_DIR, or OPENCODE_DISABLE_PROJECT_CONFIG are set in your shell.
3. One isolation run: from a NEW empty directory, run OPENCODE_DISABLE_PROJECT_CONFIG=1 OPENCODE_TUI_CONFIG=/tmp/mc-tui.json opencode where /tmp/mc-tui.json contains only {"plugin": ["@cortexkit/opencode-magic-context@0.32.4"]}. If the sidebar appears there, the fault is in config merging and your normal config files will show us where; if it's still absent, please paste any loading/applying/skipping/failed ... tui config lines from --print-logs.

[ualtinok]

Progress: we've reproduced a closely related failure locally and traced it with the OpenCode team to the TUI slot rendering layer. One more diagnostic that would confirm your instances match: after a restart, check the log for lines containing [tui.slot] (note: slot, not plugin):

grep -i 'tui.slot' ~/.local/share/opencode/log/opencode.log

If a [tui.slot] plugin error line appears naming magic-context, your sidebar is failing at render time and being silently replaced with a fallback — which matches what we reproduced (and explains why AFT can render while Magic Context doesn't). We're working the root cause with the OpenCode team; the fix will ship in the next plugin release either way.

[vicXvac]

1. The magic context plugin is completely absent in the plugin list
2. tui.jsonc and opencode.jsonc

3

Ran the isolation test. Magic Context does appear in Ctrl+P when it's the only plugin declared:

ran these commands

mkdir -p /tmp/mc-test
echo '{"plugin": ["@cortexkit/opencode-magic-context@0.32.4"]}' > /tmp/mc-tui.json
OPENCODE_DISABLE_PROJECT_CONFIG=1 OPENCODE_TUI_CONFIG=/tmp/mc-tui.json opencode

[vicXvac]

Progress: we've reproduced a closely related failure locally and traced it with the OpenCode team to the TUI slot rendering layer. One more diagnostic that would confirm your instances match: after a restart, check the log for lines containing [tui.slot] (note: slot, not plugin):

grep -i 'tui.slot' ~/.local/share/opencode/log/opencode.log

If a [tui.slot] plugin error line appears naming magic-context, your sidebar is failing at render time and being silently replaced with a fallback — which matches what we reproduced (and explains why AFT can render while Magic Context doesn't). We're working the root cause with the OpenCode team; the fix will ship in the next plugin release either way.

i ran the opencode command normally and after killing the opencode process

pkill -f opencode
ps aux | grep opencode # confirm nothing running
opencode

This returns zero results — no [tui.slot] line at all, not even a plugin error naming magic-context. Same as the earlier [tui.plugin] check — nothing gets logged for either.