Repository navigation
docs: generate weekly changelog 2026-07-12 - #5636
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe PR updates screenshot framing and changelog-generation guidance, and adds July 12, 2026 marketing changelog content covering terminal agents, improvements, experimental features, and bug fixes. ChangesScreenshot updates
Release changelog content
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Ready to review this PR? Stage has broken it down into 3 individual chapters for you:
Chapters generated by Stage for commit 6bec51d on Jul 12, 2026 8:53pm UTC. |
Greptile SummaryThis PR adds the weekly marketing changelog for 2026-07-12. The main changes are:
Confidence Score: 5/5This looks safe to merge after small changelog and prompt cleanups.
apps/marketing/content/changelog/2026-07-12-terminal-rich-input-v2-default-mobile.mdx and .github/prompts/generate-changelog.md
|
| Filename | Overview |
|---|---|
| .github/prompts/beautify-screenshot.ts | Computes screenshot frame width from image aspect ratio so tall crops fit inside the canvas. |
| .github/prompts/generate-changelog.md | Adds compact screenshot guidance, with one stale crop note that no longer matches the script. |
| apps/marketing/content/changelog/2026-07-12-terminal-rich-input-v2-default-mobile.mdx | Adds the weekly changelog entry and image references, with badge headings that can lose generated anchors. |
| apps/marketing/content/changelog/2026-07-12-tweet.md | Adds a tweet draft as a markdown file that is not included by the changelog MDX loader. |
Prompt To Fix All With AI
Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 2
apps/marketing/content/changelog/2026-07-12-terminal-rich-input-v2-default-mobile.mdx:7
**Badge Headings Lose Anchors**
When a `PRBadge` is embedded in the `##` heading, the heading children are no longer a plain string. The marketing MDX heading component only derives an id from string children, so these sections can render without stable anchors or table-of-contents targets.
### Issue 2 of 2
.github/prompts/generate-changelog.md:112-113
**Crop Guidance Is Stale**
This note still says tall, narrow crops over-zoom because the beautify script is cover-fit, but this PR changes the script to contain-fit those crops as bordered cards. Agents following the prompt can avoid valid focused crops and produce less useful changelog screenshots.
```suggestion
render the TUI content). The beautify script now contain-fits very tall,
narrow crops as bordered cards, so use the crop that best frames the feature.
```
Reviews (1): Last reviewed commit: "docs: recrop Mistral Vibe changelog shot..." | Re-trigger Greptile
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
| image: /changelog/2026-07-12-rich-input-hero.png | ||
| --- | ||
|
|
||
| ## Rich Input for Terminal Agents <PRBadge url="https://github.com/superset-sh/superset/pull/5453" /> |
There was a problem hiding this comment.
When a PRBadge is embedded in the ## heading, the heading children are no longer a plain string. The marketing MDX heading component only derives an id from string children, so these sections can render without stable anchors or table-of-contents targets.
Prompt To Fix With AI
This is a comment left during a code review.
Path: apps/marketing/content/changelog/2026-07-12-terminal-rich-input-v2-default-mobile.mdx
Line: 7
Comment:
**Badge Headings Lose Anchors**
When a `PRBadge` is embedded in the `##` heading, the heading children are no longer a plain string. The marketing MDX heading component only derives an id from string children, so these sections can render without stable anchors or table-of-contents targets.
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
| render the TUI content). Note the beautify script's crop is cover-fit — very tall, | ||
| narrow crops get over-zoomed, so prefer landscape-ish crops. |
There was a problem hiding this comment.
This note still says tall, narrow crops over-zoom because the beautify script is cover-fit, but this PR changes the script to contain-fit those crops as bordered cards. Agents following the prompt can avoid valid focused crops and produce less useful changelog screenshots.
| render the TUI content). Note the beautify script's crop is cover-fit — very tall, | |
| narrow crops get over-zoomed, so prefer landscape-ish crops. | |
| render the TUI content). The beautify script now contain-fits very tall, | |
| narrow crops as bordered cards, so use the crop that best frames the feature. |
Prompt To Fix With AI
This is a comment left during a code review.
Path: .github/prompts/generate-changelog.md
Line: 112-113
Comment:
**Crop Guidance Is Stale**
This note still says tall, narrow crops over-zoom because the beautify script is cover-fit, but this PR changes the script to contain-fit those crops as bordered cards. Agents following the prompt can avoid valid focused crops and produce less useful changelog screenshots.
```suggestion
render the TUI content). The beautify script now contain-fits very tall,
narrow crops as bordered cards, so use the crop that best frames the feature.
```
How can I resolve this? If you propose a fix, please make it concise.![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 4
🧹 Nitpick comments (1)
apps/marketing/content/changelog/2026-07-12-terminal-rich-input-v2-default-mobile.mdx (1)
25-25: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winResolve the TODO before publishing.
The TODO comment about the missing iOS screenshot is still in the changelog content. If this entry is published as-is, the comment will render as visible text in the MDX output (depending on the MDX configuration) or at minimum leaves an unfinished placeholder in a live changelog.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@apps/marketing/content/changelog/2026-07-12-terminal-rich-input-v2-default-mobile.mdx` at line 25, Remove the unresolved iOS screenshot TODO from the changelog content so the published MDX contains no unfinished placeholder; update the surrounding entry only as needed to remain complete without that comment.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/prompts/generate-changelog.md:
- Around line 112-113: Update the screenshot crop guidance near the TUI content
note to describe the beautify script’s contain-fit framing instead of cover-fit.
Remove the stale over-zooming warning and clarify that tall or narrow crops are
preserved rather than cut off, while retaining the preference guidance only if
still applicable.
In
`@apps/marketing/content/changelog/2026-07-12-terminal-rich-input-v2-default-mobile.mdx`:
- Around line 37-38: Move the GPT-5.6 Sol, Terra, and Luna bullet out of the
“Mistral Vibe Joins the Agent Roster” section and place it under the
Improvements section, preserving the existing PRBadge link and wording.
- Around line 55-57: Update the “Bug fixes” section heading in the changelog to
use the same level-two heading syntax as the “Improvements” heading, replacing
the bold-text formatting while preserving the section title and surrounding
content.
In `@apps/marketing/content/changelog/2026-07-12-tweet.md`:
- Line 29: Update the changelog sentence near “thanks to all our users” to use
“every day” as two words, preserving the rest of the wording unchanged.
---
Nitpick comments:
In
`@apps/marketing/content/changelog/2026-07-12-terminal-rich-input-v2-default-mobile.mdx`:
- Line 25: Remove the unresolved iOS screenshot TODO from the changelog content
so the published MDX contains no unfinished placeholder; update the surrounding
entry only as needed to remain complete without that comment.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 850042d6-cfbe-4d09-a1c5-c486162e122a
⛔ Files ignored due to path filters (3)
apps/marketing/public/changelog/2026-07-12-mistral-vibe.pngis excluded by!**/*.pngapps/marketing/public/changelog/2026-07-12-rich-input-hero.pngis excluded by!**/*.pngapps/marketing/public/changelog/2026-07-12-rich-input.pngis excluded by!**/*.png
📒 Files selected for processing (4)
.github/prompts/beautify-screenshot.ts.github/prompts/generate-changelog.mdapps/marketing/content/changelog/2026-07-12-terminal-rich-input-v2-default-mobile.mdxapps/marketing/content/changelog/2026-07-12-tweet.md
| render the TUI content). Note the beautify script's crop is cover-fit — very tall, | ||
| narrow crops get over-zoomed, so prefer landscape-ish crops. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Update "cover-fit" to reflect new "contain-fit" framing.
The beautify script now uses contain-fit frame sizing (.github/prompts/beautify-screenshot.ts lines 71-73), which specifically prevents tall/narrow crops from being cut off top/bottom. The note here still says "cover-fit" and warns about over-zooming, which is now partially stale — the cutoff problem is solved. Consider updating to reflect the contain-fit behavior so the agent doesn't avoid tall crops unnecessarily.
📝 Suggested update
-Note the beautify script's crop is cover-fit — very tall,
-narrow crops get over-zoomed, so prefer landscape-ish crops.
+Note the beautify script uses contain-fit framing — tall/narrow crops float as a
+bordered card instead of overflowing, but very tall crops still read poorly in a
+blog layout, so prefer landscape-ish crops when possible.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| render the TUI content). Note the beautify script's crop is cover-fit — very tall, | |
| narrow crops get over-zoomed, so prefer landscape-ish crops. | |
| render the TUI content). Note the beautify script uses contain-fit framing — tall/narrow crops float as a | |
| bordered card instead of overflowing, but very tall crops still read poorly in a | |
| blog layout, so prefer landscape-ish crops when possible. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/prompts/generate-changelog.md around lines 112 - 113, Update the
screenshot crop guidance near the TUI content note to describe the beautify
script’s contain-fit framing instead of cover-fit. Remove the stale over-zooming
warning and clarify that tall or narrow crops are preserved rather than cut off,
while retaining the preference guidance only if still applicable.
| - Model picker includes `mistral-medium-3.5` and `devstral-small` | ||
| - GPT-5.6 Sol, Terra, and Luna added to the Codex model picker <PRBadge url="https://github.com/superset-sh/superset/pull/5558" /> |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
The GPT-5.6 Codex models bullet may be misplaced under the Mistral Vibe section.
Line 38 describes Codex model picker additions (GPT-5.6 Sol, Terra, Luna), but the section heading on line 31 is "Mistral Vibe Joins the Agent Roster." This bullet is about a different agent's model picker and could confuse readers. Consider moving it to the Improvements section or giving it its own mini-section.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@apps/marketing/content/changelog/2026-07-12-terminal-rich-input-v2-default-mobile.mdx`
around lines 37 - 38, Move the GPT-5.6 Sol, Terra, and Luna bullet out of the
“Mistral Vibe Joins the Agent Roster” section and place it under the
Improvements section, preserving the existing PRBadge link and wording.
| --- | ||
|
|
||
| **Bug fixes** |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Inconsistent heading style for the Bug fixes section.
"Improvements" on line 40 uses a ## heading, but "Bug fixes" on line 57 uses bold text (**Bug fixes**). This inconsistency may cause the Bug fixes section to render without proper heading semantics or navigation anchors.
💚 Proposed fix for heading consistency
---
-**Bug fixes**
+## Bug Fixes📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| --- | |
| **Bug fixes** | |
| --- | |
| ## Bug Fixes |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@apps/marketing/content/changelog/2026-07-12-terminal-rich-input-v2-default-mobile.mdx`
around lines 55 - 57, Update the “Bug fixes” section heading in the changelog to
use the same level-two heading syntax as the “Improvements” heading, replacing
the bold-text formatting while preserving the section title and surrounding
content.
|
|
||
| Also this week: wake offline hosts with a configurable wake command, remote hosts on every plan (relay no longer needs a paid subscription), a Sydney relay region, Claude Code transcript scrolling at full speed, and Linear project/cycle filters for Tasks. | ||
|
|
||
| As always, tons of bug fixes and improvements, thanks to all our users in open beta for V2 helping us make the product better everyday <3 |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix "everyday" → "every day".
"Everyday" is an adjective meaning commonplace; the intended meaning here is "each day," which requires the two-word adverbial form "every day."
💚 Proposed fix
-helping us make the product better everyday <3
+helping us make the product better every day <3📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| As always, tons of bug fixes and improvements, thanks to all our users in open beta for V2 helping us make the product better everyday <3 | |
| As always, tons of bug fixes and improvements, thanks to all our users in open beta for V2 helping us make the product better every day <3 |
🧰 Tools
🪛 LanguageTool
[style] ~29-~29: The wording of this phrase can be improved.
Context: ...ur users in open beta for V2 helping us make the product better everyday <3
(MAKE_STYLE_BETTER)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@apps/marketing/content/changelog/2026-07-12-tweet.md` at line 29, Update the
changelog sentence near “thanks to all our users” to use “every day” as two
words, preserving the rest of the wording unchanged.
Source: Linters/SAST tools
🧹 Preview Cleanup CompleteThe following preview resources have been cleaned up:
Thank you for your contribution! 🎉 |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
2 issues found across 7 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="apps/marketing/content/changelog/2026-07-12-tweet.md">
<violation number="1" location="apps/marketing/content/changelog/2026-07-12-tweet.md:29">
P3: `everyday` should be `every day` here — "everyday" is an adjective (ordinary/commonplace), but the adverbial phrase "every day" (each day) is what the sentence intends.</violation>
</file>
<file name=".github/prompts/generate-changelog.md">
<violation number="1" location=".github/prompts/generate-changelog.md:113">
P2: This guidance says the beautify script uses "cover-fit" and warns about over-zooming tall/narrow crops, but the same PR changes `beautify-screenshot.ts` to use contain-fit framing (tall/narrow crops now float as bordered cards instead of overflowing). The documentation is stale on arrival—agents following this prompt will avoid valid focused crops unnecessarily.
Consider updating to reflect the contain-fit behavior.</violation>
</file>
Architecture diagram
sequenceDiagram
participant Desktop as Desktop Client (v2)
participant Editor as Rich Input Editor (⌘I)
participant Agent as Terminal Agent (Claude Code / Codex / Mistral Vibe)
participant Relay as Relay Server
participant iOS as iOS Client (Live Session)
participant Host as Remote Host (SSH / Relay)
Note over Desktop,Agent: Rich Input for Terminal Agents (NEW)
Desktop->>Desktop: User presses ⌘I
Desktop->>Editor: Open rich input overlay
Editor->>Editor: Capture multiline prompt, @file mentions
Desktop->>Editor: Send prompt on Enter
Editor->>Agent: Inject prompt as one block
Agent->>Agent: Execute command in TUI
Agent-->>Desktop: Display output in terminal
Note over Desktop,Agent: v2 Default for New Signups (CHANGED)
alt New user signup
Desktop->>Desktop: Enable v2 workspace layout
else Existing user
Desktop->>Desktop: Keep current configuration
end
Note over Desktop,Host: Low‑latency scrolling (improved)
Agent->>Desktop: Stream terminal output
Desktop->>Desktop: Render transcript at VS Code speed
Note over Desktop,iOS: Live Agent Sessions on iOS (Experimental)
Desktop->>Desktop: Enable "Enable live agent sessions" in Security settings
iOS->>Relay: Connect to relay (WebSocket)
Relay->>Desktop: Establish session channel
iOS->>Relay: Send message / review plan
Relay->>Desktop: Forward message to agent
Desktop->>Agent: Feed input to terminal agent
Agent->>Desktop: Tool call / permission prompt
Desktop->>Relay: Relay response
Relay->>iOS: Display in iOS session thread
alt User answers permission prompt
iOS->>Relay: Approve / deny
Relay->>Desktop: Apply decision
Desktop->>Agent: Continue execution
end
Note over Agent,Host: Mistral Vibe as First‑Class Agent (NEW)
Desktop->>Desktop: Open agent picker
Desktop->>Agent: Select Mistral Vibe
Agent->>Host: Launch agent via relay (model: mistral‑medium‑3.5)
Agent-->>Desktop: Working indicator + completion chime
Note over Desktop,Host: Additional features (wake, remote, Sydney relay)
Desktop->>Host: superset hosts wake <host>
Host-->>Desktop: Host powered on
Desktop->>Relay: Connect to Sydney relay region (lower latency)
Relay->>Host: Route traffic via Sydney node
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| connection; and applying/clearing the override fires a resize that dismisses open | ||
| dropdowns/popovers and reflows terminal TUIs (set the size first, then open the menu / | ||
| render the TUI content). Note the beautify script's crop is cover-fit — very tall, | ||
| narrow crops get over-zoomed, so prefer landscape-ish crops. |
There was a problem hiding this comment.
P2: This guidance says the beautify script uses "cover-fit" and warns about over-zooming tall/narrow crops, but the same PR changes beautify-screenshot.ts to use contain-fit framing (tall/narrow crops now float as bordered cards instead of overflowing). The documentation is stale on arrival—agents following this prompt will avoid valid focused crops unnecessarily.
Consider updating to reflect the contain-fit behavior.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/prompts/generate-changelog.md, line 113:
<comment>This guidance says the beautify script uses "cover-fit" and warns about over-zooming tall/narrow crops, but the same PR changes `beautify-screenshot.ts` to use contain-fit framing (tall/narrow crops now float as bordered cards instead of overflowing). The documentation is stale on arrival—agents following this prompt will avoid valid focused crops unnecessarily.
Consider updating to reflect the contain-fit behavior.</comment>
<file context>
@@ -99,6 +99,19 @@ the full `pointerdown/mousedown/pointerup/mouseup/click` sequence) and
+connection; and applying/clearing the override fires a resize that dismisses open
+dropdowns/popovers and reflows terminal TUIs (set the size first, then open the menu /
+render the TUI content). Note the beautify script's crop is cover-fit — very tall,
+narrow crops get over-zoomed, so prefer landscape-ish crops.
+
**2. Beautify** with `.github/prompts/beautify-screenshot.ts` (local headless-Chrome
</file context>
|
|
||
| Also this week: wake offline hosts with a configurable wake command, remote hosts on every plan (relay no longer needs a paid subscription), a Sydney relay region, Claude Code transcript scrolling at full speed, and Linear project/cycle filters for Tasks. | ||
|
|
||
| As always, tons of bug fixes and improvements, thanks to all our users in open beta for V2 helping us make the product better everyday <3 |
There was a problem hiding this comment.
P3: everyday should be every day here — "everyday" is an adjective (ordinary/commonplace), but the adverbial phrase "every day" (each day) is what the sentence intends.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/marketing/content/changelog/2026-07-12-tweet.md, line 29:
<comment>`everyday` should be `every day` here — "everyday" is an adjective (ordinary/commonplace), but the adverbial phrase "every day" (each day) is what the sentence intends.</comment>
<file context>
@@ -0,0 +1,29 @@
+
+Also this week: wake offline hosts with a configurable wake command, remote hosts on every plan (relay no longer needs a paid subscription), a Sydney relay region, Claude Code transcript scrolling at full speed, and Linear project/cycle filters for Tasks.
+
+As always, tons of bug fixes and improvements, thanks to all our users in open beta for V2 helping us make the product better everyday <3
</file context>
| As always, tons of bug fixes and improvements, thanks to all our users in open beta for V2 helping us make the product better everyday <3 | |
| As always, tons of bug fixes and improvements, thanks to all our users in open beta for V2 helping us make the product better every day <3 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@apps/marketing/content/changelog/2026-07-12-terminal-rich-input-mistral-vibe.mdx`:
- Line 44: Replace the bold paragraph introducing the Experimental section with
a semantic Markdown heading, preserving the existing title text and PRBadge
while keeping the section content unchanged.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 949a7e4b-e80d-432f-8c75-a1e75da780fe
📒 Files selected for processing (3)
.github/prompts/generate-changelog.mdapps/marketing/content/changelog/2026-07-12-terminal-rich-input-mistral-vibe.mdxapps/marketing/content/changelog/2026-07-12-tweet.md
🚧 Files skipped from review as they are similar to previous changes (2)
- .github/prompts/generate-changelog.md
- apps/marketing/content/changelog/2026-07-12-tweet.md
| - **CLI workspace lookup** - `superset ws get` prints a workspace's details, with `--field` for scripting <PRBadge url="https://github.com/superset-sh/superset/pull/5549" /> | ||
| - **The main workspace is "local"** - The repo checkout always displays as "local" and can no longer be renamed <PRBadge url="https://github.com/superset-sh/superset/pull/5586" /> | ||
|
|
||
| **Experimental: live agent sessions on iOS** - an early build of driving a coding agent running on your desktop from the iOS app; the agent and your code stay on your machine. Off by default under Desktop → Settings → Security. <PRBadge url="https://github.com/superset-sh/superset/pull/5580" /> |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Use a semantic heading for the Experimental section.
This distinct section is currently formatted as bold paragraph text, so it will not receive normal heading semantics or navigation treatment.
Proposed fix
-**Experimental: live agent sessions on iOS** - an early build of driving a coding agent running on your desktop from the iOS app; the agent and your code stay on your machine. Off by default under Desktop → Settings → Security. <PRBadge url="https://github.com/superset-sh/superset/pull/5580" />
+## Experimental: live agent sessions on iOS
+
+An early build of driving a coding agent running on your desktop from the iOS app; the agent and your code stay on your machine. Off by default under Desktop → Settings → Security. <PRBadge url="https://github.com/superset-sh/superset/pull/5580" />📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| **Experimental: live agent sessions on iOS** - an early build of driving a coding agent running on your desktop from the iOS app; the agent and your code stay on your machine. Off by default under Desktop → Settings → Security. <PRBadge url="https://github.com/superset-sh/superset/pull/5580" /> | |
| ## Experimental: live agent sessions on iOS | |
| An early build of driving a coding agent running on your desktop from the iOS app; the agent and your code stay on your machine. Off by default under Desktop → Settings → Security. <PRBadge url="https://github.com/superset-sh/superset/pull/5580" /> |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@apps/marketing/content/changelog/2026-07-12-terminal-rich-input-mistral-vibe.mdx`
at line 44, Replace the bold paragraph introducing the Experimental section with
a semantic Markdown heading, preserving the existing title text and PRBadge
while keeping the section content unchanged.
There was a problem hiding this comment.
2 issues found across 3 files (changes from recent commits).
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name=".github/prompts/generate-changelog.md">
<violation number="1" location=".github/prompts/generate-changelog.md:11">
P2: The revert-detection guidance added to the changelog prompt relies on scanning for `revert:` PR titles, which is unreliable. GitHub auto-generated revert PRs typically use `Revert "..."` rather than the `revert:` prefix, and the prompt provides no deterministic way to map a revert PR back to the original PR it undid. This makes it likely the generator will drop the revert PR but still include the reverted feature in the changelog, publishing code that is no longer shipped. Consider verifying the actual title format used by reverts in this repository (e.g., #5641) and adding a concrete lookup mechanism — for example, parsing the revert PR body for the original PR number or cross-referencing merge commits.</violation>
<violation number="2" location=".github/prompts/generate-changelog.md:73">
P2: The new instruction to use macOS-only shortcut glyphs (⌘I, ⌘⇧L) will make public changelog entries inaccurate for Windows and Linux users, who use Ctrl-based bindings instead. Prior changelog entries already used cross-platform notation (e.g., `⌘/Ctrl+click`, `⌘F / Ctrl+Shift+F`, `Cmd/Ctrl+Enter`) to accommodate all platforms, and the project has explicit cross-platform desktop support. Combined with the nearby instruction to "end every feature with how to get it," this risks telling Windows/Linux users to press shortcuts they do not have. Consider amending the guidance to either list both variants (`⌘/Ctrl+I`) or note that cross-platform features should use platform-neutral notation.</violation>
</file>
Tip: Review your code locally with the cubic CLI to iterate faster.
Re-trigger cubic
| - Use a horizontal rule (`---`) before the bug fixes section | ||
| - Bug fixes should use bullet points, one fix per line, same as Improvements | ||
| - **Title Case for `##` headings** ("Redesigned Workspace Activity Strip", not "Redesigned workspace activity strip") | ||
| - **Shortcuts as mac glyphs**: ⌘I, ⌘⇧L, not "Cmd+I" or "Cmd-Shift-L" |
There was a problem hiding this comment.
P2: The new instruction to use macOS-only shortcut glyphs (⌘I, ⌘⇧L) will make public changelog entries inaccurate for Windows and Linux users, who use Ctrl-based bindings instead. Prior changelog entries already used cross-platform notation (e.g., ⌘/Ctrl+click, ⌘F / Ctrl+Shift+F, Cmd/Ctrl+Enter) to accommodate all platforms, and the project has explicit cross-platform desktop support. Combined with the nearby instruction to "end every feature with how to get it," this risks telling Windows/Linux users to press shortcuts they do not have. Consider amending the guidance to either list both variants (⌘/Ctrl+I) or note that cross-platform features should use platform-neutral notation.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/prompts/generate-changelog.md, line 73:
<comment>The new instruction to use macOS-only shortcut glyphs (⌘I, ⌘⇧L) will make public changelog entries inaccurate for Windows and Linux users, who use Ctrl-based bindings instead. Prior changelog entries already used cross-platform notation (e.g., `⌘/Ctrl+click`, `⌘F / Ctrl+Shift+F`, `Cmd/Ctrl+Enter`) to accommodate all platforms, and the project has explicit cross-platform desktop support. Combined with the nearby instruction to "end every feature with how to get it," this risks telling Windows/Linux users to press shortcuts they do not have. Consider amending the guidance to either list both variants (`⌘/Ctrl+I`) or note that cross-platform features should use platform-neutral notation.</comment>
<file context>
@@ -64,14 +69,26 @@ Brief description of the feature and its benefit to users.
- Use a horizontal rule (`---`) before the bug fixes section
- Bug fixes should use bullet points, one fix per line, same as Improvements
+ - **Title Case for `##` headings** ("Redesigned Workspace Activity Strip", not "Redesigned workspace activity strip")
+ - **Shortcuts as mac glyphs**: ⌘I, ⌘⇧L, not "Cmd+I" or "Cmd-Shift-L"
+ - **UI paths in bold with arrows**: **Settings → Experimental**, **Integrations → Slack**
+ - **No emoji in the changelog entry** - emoji belong in the launch thread only
</file context>
| - **Shortcuts as mac glyphs**: ⌘I, ⌘⇧L, not "Cmd+I" or "Cmd-Shift-L" | |
| - **Shortcuts as mac glyphs, or cross-platform notation for shared features**: Use ⌘I, ⌘⇧L for mac-only features; for features available on all platforms, prefer ⌘/Ctrl+I or ⌘F / Ctrl+Shift+F so the changelog is accurate for Windows and Linux users too |
| - Use `gh pr list --state merged --search "merged:>=$(date -d 'last monday' +%Y-%m-%d)" --json number,title,body,url,mergedAt --limit 50` to get all PRs merged in the past week | ||
| - Categorize PRs into: **Major features**, **Improvements**, **Bug fixes** | ||
| - Skip PRs that are purely internal (CI/CD, dev tooling, refactors) unless they affect users | ||
| - **Drop reverted work**: scan the same window for `revert:` PRs and exclude both the revert and the PR it undoes (e.g. #5639 merged and was reverted by #5641 eleven minutes later) |
There was a problem hiding this comment.
P2: The revert-detection guidance added to the changelog prompt relies on scanning for revert: PR titles, which is unreliable. GitHub auto-generated revert PRs typically use Revert "..." rather than the revert: prefix, and the prompt provides no deterministic way to map a revert PR back to the original PR it undid. This makes it likely the generator will drop the revert PR but still include the reverted feature in the changelog, publishing code that is no longer shipped. Consider verifying the actual title format used by reverts in this repository (e.g., #5641) and adding a concrete lookup mechanism — for example, parsing the revert PR body for the original PR number or cross-referencing merge commits.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At .github/prompts/generate-changelog.md, line 11:
<comment>The revert-detection guidance added to the changelog prompt relies on scanning for `revert:` PR titles, which is unreliable. GitHub auto-generated revert PRs typically use `Revert "..."` rather than the `revert:` prefix, and the prompt provides no deterministic way to map a revert PR back to the original PR it undid. This makes it likely the generator will drop the revert PR but still include the reverted feature in the changelog, publishing code that is no longer shipped. Consider verifying the actual title format used by reverts in this repository (e.g., #5641) and adding a concrete lookup mechanism — for example, parsing the revert PR body for the original PR number or cross-referencing merge commits.</comment>
<file context>
@@ -8,6 +8,8 @@ Generate a new changelog entry for this week based on merged PRs.
- Use `gh pr list --state merged --search "merged:>=$(date -d 'last monday' +%Y-%m-%d)" --json number,title,body,url,mergedAt --limit 50` to get all PRs merged in the past week
- Categorize PRs into: **Major features**, **Improvements**, **Bug fixes**
- Skip PRs that are purely internal (CI/CD, dev tooling, refactors) unless they affect users
+ - **Drop reverted work**: scan the same window for `revert:` PRs and exclude both the revert and the PR it undoes (e.g. #5639 merged and was reverted by #5641 eleven minutes later)
+ - **Dedupe against the previous entry**: the date window overlaps the day the last changelog merged, so read the most recent existing entry and skip any PR it already announced
</file context>
| - **Drop reverted work**: scan the same window for `revert:` PRs and exclude both the revert and the PR it undoes (e.g. #5639 merged and was reverted by #5641 eleven minutes later) | |
| + - **Drop reverted work**: scan the same window for `revert:` or `Revert "` PRs. For each revert, read its body for the original PR number (GitHub reverts usually include `Reverts org/repo#N`) or run `gh pr view <revert-number> --json body` to find the reverted PR, then exclude both from the changelog. |
Summary
Weekly changelog for 2026-07-06 → 2026-07-12, generated from this week's merged PRs.
apps/marketing/content/changelog/2026-07-12-terminal-rich-input-mistral-vibe.mdx— leads with the ⌘I rich input overlay for terminal agents (feat(desktop): Warp-style rich input overlay for terminal panes (v2) #5453/feat(desktop): make terminal rich input a global toggle for all panes #5522) and Mistral Vibe as a first-class agent (feat(desktop): add first-class Mistral Vibe coding agent #5552, GPT-5.6 Codex models feat(shared): add GPT-5.6 models to Codex picker #5558); 12 improvements + 12 bug-fix one-liners with PR badges. The experimental iOS live agent sessions (feat(mobile): live ACP agent sessions end to end (host harness, mobile UI, desktop gate) #5580) appear as a low-key footnote at the bottom of Improvements.2026-07-12-tweet.md(ignored by the changelog loader).generate-changelog.md, andbeautify-screenshot.tsnow contain-fits frames so tall/narrow crops render as bordered cards instead of overflowing the canvas.Not included: #5639 (native-fidelity wheel scrolling) merged 2026-07-12 but was reverted by #5641 eleven minutes later — the shipped scrolling change remains #5563.
Test Plan
bun run lintexits 0<PRBadge>links)2026-07-12-tweet.mddoes not render as a changelog entrySummary by CodeRabbit
@filementions and draft persistence across tab switches.