Skip to content

Commit 6ae03a0

Browse files
committed
release-notes: add v0.21.6 and dashboard-v0.4.7 drafts
1 parent cf0c01b commit 6ae03a0

2 files changed

Lines changed: 35 additions & 0 deletions

File tree

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# Dashboard v0.4.7 — Memories tab project filter fix
2+
3+
## What's Fixed
4+
5+
- **Memories tab returned zero results when filtering by project (#87).** The frontend sends the resolved project identity (e.g. `git:<commit-hash>`) as the filter value, but the backend was querying `memories WHERE project_path = ?` against raw filesystem paths stored on each memory row. The two never matched, so filtering any project showed no memories even when memories existed for that project.
6+
7+
Fixed by resolving the incoming identity to all stored paths that belong to it (a single `git:` identity can cover multiple worktrees and clones writing into the same shared memory pool) and querying with an `IN (...)` clause across the full set. Identical to the path History already used, so both tabs now agree on what "this project" means.
8+
9+
## Upgrade
10+
11+
The Tauri auto-updater handles this release. Existing installations should pick it up on next launch or via Help → Check for Updates.

.alfonso/release-notes/v0.21.6.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# v0.21.6 — Hidden subagent isolation, TUI threshold visibility, doctor report size cap
2+
3+
## What's New
4+
5+
- **TUI sidebar and `/ctx-status` header now show the execute threshold** alongside the percentage. The header changes from `47.5% · 475K / 1.0M` to a left/right layout: `47.5% / 65%` on the left (current usage vs the execute threshold that triggers compaction), `475K / 1.0M` on the right (absolute tokens vs the model's context window). Resolved per-model, so users with `execute_threshold_percentage` or `execute_threshold_tokens` overrides see the actual value applied to their session.
6+
7+
## What's Fixed
8+
9+
- **Historian, dreamer, and sidekick can no longer spawn subagents or run unsafe tools.** Each hidden agent now ships with a `permission` ruleset that denies everything by default and explicitly allows only the tools that agent actually needs:
10+
- Historian / compressor: `read`, `aft_outline`, `aft_zoom` (state-file offload + lightweight symbol navigation for accurate summaries)
11+
- Dreamer: `read`, `grep`, `glob`, `bash`, `aft_outline`, `aft_zoom`, `ctx_memory`, `ctx_search`, `ctx_note` (memory CRUD + verification against project source + smart-note evaluation via `gh` / `git` / `curl`). `task`, `edit`, `write`, `webfetch`, `websearch` stay denied.
12+
- Sidekick: `ctx_search`, `ctx_memory`, `aft_outline`, `aft_zoom` (memory retrieval + symbol-scoped structural context for `/ctx-aug`)
13+
14+
Previously these agents inherited the full primary-agent tool surface and historian was occasionally observed dispatching `task(subagent_type=explore)` for repo-wide fanout, which contradicts its job of summarizing the input it was given. Allow-lists were derived from auditing real tool usage in the local OpenCode DB across hundreds of past historian and dreamer child sessions.
15+
16+
- **`doctor --issue` reports now respect GitHub's 64KB body limit.** When the rendered report exceeds the budget, the main log section is truncated from the top (oldest lines dropped) with a visible `[truncated for GitHub 64KB limit — older log lines dropped]` marker. A new "Recent errors (last 20, sanitized)" section is always included before the main log so error context survives even when the bulk log gets clipped.
17+
18+
## Upgrade
19+
20+
```bash
21+
npx @cortexkit/magic-context@latest doctor --force
22+
```
23+
24+
If OpenCode still loads a cached older plugin after upgrading the CLI, the `--force` flag clears the cached install so the new version takes effect on next launch.

0 commit comments

Comments
 (0)