Goal and Tasks banners cast an excessive shadow above the composer
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- react, typescript
Research direction
Start with apps/web/src/components/chat/ComposerBanner.tsx, especially ComposerBanner.Peek and how ComposerBannerStack places the collapsed panel above the Tasks banner. Reproduce the reported setup in the desktop app with an active goal and task list, then inspect the light appearance. Done when the panels have a clean separation without the heavy shadow shown in the screenshot.
Written by the indexing model from the issue text.
Description
What happened
When a thread has both tasks and an active goal, the stacked panels above the composer show an unattractive dark shadow across the top of the Tasks bar. The supplied screenshot shows this in a light appearance.
Diagnosis
Likely source: ComposerBanner.Peek uses shadow-md, and ComposerBannerStack places the collapsed panel above the Tasks banner. This matches the screenshot, but the cause has not been independently verified in a running client.
Steps to reproduce
Based on the user's report:
- Open a thread in the desktop app.
- Have both an active goal and a task list.
- Inspect the collapsed panels above the composer.
Expected: a clean separation between panels without the heavy dark band.
Version
0.1.2-nightly.20261021.3457, confirmed by the local server.
Environment
Windows x64, build 10.0.26200; desktop app connected to its local server. Triage CLI: 0.1.1.
Evidence
User-provided screenshot showing the shadow above the Tasks row. The user will need to attach the screenshot after issue creation.
Related issues
#19455 concerns warnings obscured by goal banners; this report concerns visual shading.
Fix applied or workaround
None.
Filed by
Codex AI agent via T3 triage; GPT-6.1-Sol.
- Dominant language
- TypeScript
- Stars
- 24.8k
- Forks
- 6.4k
- Avg merge
- 3h 39m
- Merged PRs (30d)
- 301
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pingdotgg/t3code
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
All issues in pingdotgg/t3code
Similar issues
-
[BUG] rag: sentence content can cross the reported sentence boundariesPossibly taken @LJK-ikun claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
README: the Resource URI Schemas example's file://documents/* pattern only matches that literal URIOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
platformatic/mcp#361 ·
Maintainers usually reply within 1 day
-
frontend
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Push: sem service worker ou sem VAPID, o interruptor de Notificações fica ligado sem avisar nadaOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
melgarafael/DeskcommCRM#3164 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ant-design/pro-components#9769 ·
Maintainers usually reply within 1 day