Repository navigation
feat(marketing): hero shows four agents running at once - #26875
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ApprovabilityVerdict: Approved at Macroscope's review found this PR approvable — Updates the marketing hero's alternative text to describe the four-agent screenshot. The change is presentation-only and does not alter product defaults or agent behavior. You can add or adjust custom eligibility rules. Learn more. |
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Update screenshot description apps/marketing/src/pages/index.astro |
The alternative text now describes Claude, Codex, Muse, and Gemini subagents running in one thread. |
Priority:
Estimated code review effort: 1 (Trivial) | ~2 minutes
Change: Other
Suggested reviewers: maria-rcks
Merge Risk: 
Minimal · up to 936f7
-
The marketing screenshot and matching alternative text can merge with no identified product risk.
Pre-merge checks: 
3 · 
1
-
Failed checks: 1 warning Passed checks: 3 passed-
Full details: Title check
-
Explanation
The title "feat(marketing): hero shows four agents running at once" follows conventional commit format and names the main change: the marketing hero screenshot now shows four agents running in one thread. It matches the raw summary, which describes Claude, Codex, Muse, and Gemini subagents running in one thread, and the PR objectives, which describe replacing the hero screenshot.
-
Full details: Description check
-
Explanation
The description states the problem (the old hero did not show that one thread can run agents from different harnesses), describes the change (a new screenshot and matching alt text), and includes a before/after screenshot table as the template requires for UI changes. It also gives image size and file-size details and notes the model and harness used. The Scope and approval section is missing: it has no linked triaged issue or maintainer-approved discussion, and no explanation of why the change qualifies without one. The Verification section does not describe focused checks beyond the screenshots (for example, how the captured runs were confirmed as real). The Problem section is brief and has no reproduction steps, which the template treats as optional.
Resolution
Add a Scope and approval section. Link the triaged issue or the maintainer-approved discussion, or explain why this focused marketing-asset change qualifies without one. Expand the Verification section with the checks performed on the new screenshot, such as confirming the four runs were real and that the alt text matches the image. State anything not checked. The before/after screenshots and the model/harness attribution are already present and can stay.
-
Finishing Touches
-
🧪 Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Comment @coderabbitai help to get the list of available commands.
**v0.1.5** · 25 changes from 5 contributors ## Highlights Turn a No project thread into a project. Use Claude and GPT models and thinking controls with Antigravity. Customize thread details, including usage limits. Switch all your installations between Stable and Nightly in one step. ## Fixes - New threads avoid providers that just hit usage limits (#26234) - Guest links no longer expose file diffs (#26538) - Claude edits open as diffs, not raw JSON (#26529) - Fixed a desktop security vulnerability in Brotli decompression (#26348) - Undo notices no longer cover threads (#26874) - Antigravity file reads no longer show unrelated errors (#26910) - T3 starts on fresh Ubuntu servers without libatomic (#26912) - Update everything no longer unnecessarily waits for npm (#26917) - Antigravity file reads no longer keep spinning (#26928) - Copilot follow-ups no longer kill background agents (#26715) <details> <summary>Full changelog</summary> ## What's Changed * fix(server,cursor,opencode): refresh provider usage when a turn hits its usage limit by @maria-rcks in pingdotgg/t3code#26234 * fix(web): keep tool groups collapsed after a usage-limit pause by @shivamhwp in pingdotgg/t3code#24937 * fix(mobile): photo-library PNGs no longer fail after resizing by @shivamhwp in pingdotgg/t3code#26522 * fix(server): guest links no longer return file diffs by @nexxeln in pingdotgg/t3code#26538 * fix(claude): Open diff shows Claude edits as a diff instead of raw JSON by @nexxeln in pingdotgg/t3code#26529 * chore: vouch nexxeln by @t3dotgg in pingdotgg/t3code#26812 * feat(web): Labs toggle keeps 5h, weekly, and context limits in view by @t3dotgg in pingdotgg/t3code#26859 * fix(desktop): bump Electron to 44.10.0 for the Node.js Brotli fix (CVE-2026-111497) by @nabettu in pingdotgg/t3code#26348 * chore: make agent mistakes fail early by @t3dotgg in pingdotgg/t3code#26167 * feat(marketing): hero shows four agents running at once by @t3dotgg in pingdotgg/t3code#26875 * fix(web): undo notice moves to the sidebar footer so it never covers a thread by @t3dotgg in pingdotgg/t3code#26874 * feat: turn a No project thread into a project by @t3dotgg in pingdotgg/t3code#26767 * feat(antigravity): Claude and GPT models, thinking levels, and diff edits by @t3dotgg in pingdotgg/t3code#26876 * feat(web): choose what the thread details card shows by @t3dotgg in pingdotgg/t3code#26904 * feat(updates): switch your whole fleet between Stable and Nightly in one step by @t3dotgg in pingdotgg/t3code#26288 * fix(antigravity): file reads no longer show unrelated errors by @t3dotgg in pingdotgg/t3code#26910 * feat(release): release notes and the update popover open with a short note by @t3dotgg in pingdotgg/t3code#26893 * fix(cli): t3 starts on a fresh Ubuntu server without libatomic by @t3dotgg in pingdotgg/t3code#26912 * fix(web): update everything no longer waits on npm for service hosts by @t3dotgg in pingdotgg/t3code#26917 * test(web): pin the npm wait floor for update everything by @t3dotgg in pingdotgg/t3code#26921 * fix(antigravity): served reads stop spinning and duplicate model names are labeled by @t3dotgg in pingdotgg/t3code#26928 * fix(server): queue Copilot follow-ups without killing background agents by @shivamhwp in pingdotgg/t3code#26715 * fix(web): Antigravity effort no longer shows a speedometer in the composer by @t3dotgg in pingdotgg/t3code#26929 * fix(release): Linux CLI archives build on runners without package docs by @t3dotgg in pingdotgg/t3code#26932 **Full Changelog**: pingdotgg/t3code@v0.1.4...v0.1.5 </details> Upstream release: https://github.com/pingdotgg/t3code/releases/tag/v0.1.5
The marketing hero was a T3 Code thread next to a code diff. It did not show what makes T3 Code different: one thread can run agents from different harnesses at the same time.
The new screenshot is one short exchange in a non-T3 project (postplan). The user asks for 4 subagents, the agent replies "Okay, opening Claude, Codex, Muse and Gemini.", and you can see all 4 running in the thread and in the details pane. The sidebar shows threads from several projects, and the dev banner is turned off. These were real runs captured at 2x. Only released model names are visible.
The image is the same size (2880×1800) and smaller on disk (268 KB to 97 KB). The alt text now matches the image.
Created with Claude Opus 5.5 in T3 Code (Claude Code harness).
🤖 Generated with Claude Code