Skip to content

chore(catalog): re-pin mood-music to v0.2.6 - #94

Merged
iamwhatever merged 1 commit into
mainfrom
chore/mood-music-0.2.6
Nov 19, 2026
Merged

iamwhatever merged 1 commit into
mainfrom
chore/mood-music-0.2.6

Conversation

@iamwhatever

Copy link
Copy Markdown
Collaborator

What

Re-pins mood-music from 25f879978b373377657b38f9901c3efc0b2ed9f0 (v0.2.5, catalog PR #93) to
3b01f06f37c37e0cfd14687ce315bb9bf0d8ca3f (v0.2.6), the merge commit of
app PR #10 and the current main of
iamwhatever/kirocrew-app-mood-music.
Clicking Sync installs the pinned ref, so until this lands users keep getting v0.2.5.

The entry's note now says the page shows the buddy's browser, that the buddy chat is hidden and
now kept in Crew memory, lists the new grants (chatSlots, browser:view), and names
KiroCrew#39018. It is 300 characters (the schema maximum). No other entry is touched. The registry
has no separate version field; the version comes from the app's app.json at the pinned ref.

Needs Kiro Crew with kirodotdev/KiroCrew#39018

v0.2.6 uses three Kiro Crew changes, all merged to main:

  • kirodotdev/KiroCrew#39246: ctx.chat_slots.open(state, key, hidden=True), the hidden chat the backend opens itself.
  • kirodotdev/KiroCrew#39020: the app SDK's BrowserView.
  • kirodotdev/KiroCrew#39018 (merged 2026-11-19 16:54 UTC, 906ee87027): permissions.browser, the "view" grant and the live view for an app's own slot. It is the newest of the three, so a Kiro Crew build that has it has all three.

The view also needs App browser access on in Settings > Developer > Feature previews, then
"view" approved on the app's page. On an older Kiro Crew the page says to update Kiro Crew: the
buddy's chat answers old_host, and the browser box says it cannot show the browser here yet.

What changed in the app (v0.2.5 -> v0.2.6, app PR #10)

  • The page shows the buddy's browser. A "Kiro Crew's browser" box in the player column holds the host's BrowserView for the buddy's chat, so the person can watch the buddy search and open a song, and take the tab over. The page never reads frames; the picture is Kiro Crew's.
  • The backend opens the buddy's chat through ctx.chat_slots (backend/buddy.py, POST /buddy, POST /buddy/send), hidden from the session lists. Before, the page opened it with POST /api/chat/slots.
  • The buddy's chat now uses Kiro Crew memory. v0.2.5 opened it with memory_mode: 'temporary'; ctx.chat_slots.open takes no memory mode, so the chat is a normal one and what is said there can go into lasting memory. The app's own taste store (Memory tab) is unchanged.

Permission and tool differences vs v0.2.5 (app.json, agents/dj.json)

Read from both refs with git diff 25f8799 3b01f06 -- app.json agents/dj.json.

Field v0.2.5 (25f8799) v0.2.6 (3b01f06)
version 0.2.5 0.2.6
permissions.chatSlots absent true (new)
permissions.browser absent ["view"] (new: the page may show the buddy's browser)
permissions.hiddenSessions true unchanged (kept)
permissions sessionApproval, storage, network true unchanged
permissions.api app, chat, /api/browser/media unchanged
permissions.mcpTools ["browser"] unchanged
permissions.browserSites 4 bilibili / YouTube search and play patterns unchanged
configuration one line adds a line on #39246 / #39018 / #39020 and approving "view"
agents/dj.json no change
crons, setup hooks, mcpServers none none

So v0.2.6 adds two grants (chatSlots, browser: ["view"]) and removes none. "view" lets the
page show the browser picture of the app's own chat only; it gives no new browser verbs to the
agent, and the four browserSites patterns are still the hard limit.

Screenshots

Taken with the app's own capture/capture.py from an isolated gateway (loopback only, throwaway
home, stub model) on Kiro Crew main at 906ee87027 (includes #39018), with app 3b01f06
installed from a clone. App browser access is on, and browserSites plus browser: ["view"]
were approved through the enable call. The queue is seeded through the app's own POST /queue.

light dark

The "Kiro Crew's browser" box (top right) is the real host BrowserView with access granted. It
shows "No page is open in this chat yet." because no model turn ran: the stub model does not
drive the browser, so there is no live page to show. A shot of a live page needs a signed-in model
turn driving a set-up browser, which this capture did not run. These are not mock-ups.

The images are on the pr-assets/catalog-0.2.6 branch of the app repo. It is not for merge and
can be deleted after review.

Verified

  • gh pr view 10 -R iamwhatever/kirocrew-app-mood-music: MERGED at 2026-11-18T22:06:31Z, merge
    commit 3b01f06f37c37e0cfd14687ce315bb9bf0d8ca3f. git rev-parse origin/main in the app repo is
    the same commit; app.json there says "version": "0.2.6".
  • App CI on 3b01f06: success.
  • gh pr view 39018 -R kirodotdev/KiroCrew: MERGED 2026-11-19T16:54:53Z, 906ee870275f. #39246 and #39020 MERGED.
  • python tools/validate.py: OK (3 pre-existing warnings on other apps).
  • python tools/format.py --check: all 3 files normalized.
  • pytest tests/ -q: 522 passed.

@github-actions

Copy link
Copy Markdown

Opus 5 Review — ✅ no blocking findings

Opus 5 completed its review of 4fb52e17dcde6790dd79d408f385787c373a209c and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] 4fb52e1

@github-actions

Copy link
Copy Markdown

GPT 5.6 Review — ✅ no blocking findings

GPT 5.6 completed its review of 4fb52e17dcde6790dd79d408f385787c373a209c and found no blocking issues.

This comment is updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] 4fb52e1

@github-actions

Copy link
Copy Markdown

App Readiness Review — ✅ no blocking findings

Every app repository this PR adds or re-pins passed the blocking readiness rules at 4fb52e17dcde6790dd79d408f385787c373a209c.

Rules: review/app-readiness-rules.md (base-branch snapshot). This comment is updated in place on each push.

Review details

No findings.

mood-music @ 3b01f06f37c37e0cfd14687ce315bb9bf0d8ca3f

No findings.

[APP-READINESS-REVIEWED] 4fb52e1

@iamwhatever
iamwhatever merged commit 8853366 into main Nov 19, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant