[only21mil]

Problem

In the web app on a phone or tablet, Settings > Project > Actions lists saved commands but hides their edit gear until hover or keyboard focus. A touch user sees no edit control. The button remains in the layout and can be tapped without seeing it.

Reproduced on main 5ffe045931 in Android Chrome. With a coarse pointer, no hover capability and no focus in the row, the edit wrapper has computed opacity 0.

Change

Add pointer-coarse:opacity-100 to the edit control wrapper. This follows the touch fallback already used by the keybinding rows in Settings and by other hover-revealed web controls, such as the pull request edit button. Fine-pointer hover and keyboard-focus classes stay in place.

Scope and approval

This is a small, focused fix for an obvious visibility bug in an existing control. It qualifies for the exception in CONTRIBUTING.md. No prior issue or discussion was found. The change is one class in ProjectActionsList.tsx.

Verification

Built main and the fix separately with isolated app state. Opened the production web app in Android 16 Chrome, chose the same example project, scrolled to Actions, and captured the row before touching its edit control. The gear is absent on main and visible with the fix. Tapping the visible gear opens Edit Action with the saved name and command.

Exact scoped checks:

• pnpm --filter @t3tools/web build: both production builds pass.
• node read-style.mjs: a disposable check against the real Chrome tab fails on main and passes with the fix. It requires (pointer: coarse), no hover/focus on the wrapper, and opacity 1. Main returns 0; the fix returns 1.
• pnpm exec vp lint apps/web/src/components/settings/ProjectActionsList.tsx: pass, zero errors or warnings.
• pnpm exec vp fmt --check apps/web/src/components/settings/ProjectActionsList.tsx: pass.
• pnpm exec vp run --filter @t3tools/web typecheck: pass.

The check reads getComputedStyle(document.querySelector('[aria-label="Edit Verify"]').parentElement).opacity. No class-name assertion, mock, timer, or basic DOM test was added to the suite. The repository's visual-fix guidance calls for before/after captures.

Not checked: iOS Safari, physical touch hardware, desktop mouse/keyboard interaction, action execution, or the native clients. The native clients use separate components.

Prior PRs: no earlier PR attempting this touch visibility fix was found in live open and closed PR searches.

Main production build, before touching the row. The saved action has no visible edit gear.

Fix production build, before touching the row. The edit gear is visible.

The same visibility assertion fails on main and passes with the fix.

Production fix, verification check, PR description and images written with GPT-6.1 Sol in T3 Code Nightly.

🤖 Generated with GPT-6.1 Sol in T3 Code Nightly

[macroscopeapp]

Approvability

Verdict: Approved at b1df485

Macroscope's review found this PR approvable — Adds one existing, established touch-pointer utility to reveal project-action edit buttons on coarse-pointer screens. The change is isolated to presentation, preserves desktop hover and keyboard-focus behavior, and has no schema or broader runtime impact.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Source mode: Auto
• Repository: pingdotgg/t3code
• Branch: main
• File: .coderabbit.config.ts
• Commit: f054d1b
• Layers: Repository TS config
• Review profile: CHILL
• Plan: Advanced
• Run ID: cadf57f7-9057-4cf7-ac77-2c16929dda31

📥 Commits

Reviewing files that changed from the base of the PR and between f054d1b and b1df485.

📒 Files selected for processing: 1

• apps/web/src/components/settings/ProjectActionsList.tsx

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 6 remain after this review.

📝 Walkthrough

The edit-control container is now visible on coarse-pointer devices. Its existing focus-within and hover visibility rules remain.

Changes: Edit-control visibility

Layer / File(s)	Summary
Coarse-pointer visibility apps/web/src/components/settings/ProjectActionsList.tsx	The edit-control container adds pointer-coarse:opacity-100. Existing focus-within and hover rules remain.

Priority: ➖ Normal

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to b1df4

The touch-screen visibility fix is supported and does not regress other interaction modes.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title is concise, uses the repository's conventional format, and clearly describes the touch-screen visibility fix for project action edit buttons.
Description check		The description includes all required sections. It clearly explains the problem, change, scope and approval rationale, verification steps and results, screenshots, limitations, and the agent details.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• 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.}

[maria-rcks]

Note

Written by gpt-6.1-sol on behalf of Maria

Verified in a real dev environment

verified as-is at b1df485adafa37ab625e8bb4d90d4bf7add38842 on this linux boat vm. no source changes or pushes were needed.

• installed and ran github/main (5ef56853ef1854da50bc1909c6c0a32700f2cb13) in a separate worktree, then stopped its captured server process before starting the exact pr head. both used isolated development state and background vp run dev servers.
• drove the real web client with the repo's playwright and /usr/bin/google-chrome. added the real /home/user/t3code git checkout through the app, created a thread, selected codex gpt-6.1-sol, and received project actions verification ready. through the local provider proxy. no mocks, fixtures, replay provider, or seeded data.
• created the same saved Verify action through settings on both revisions. with touch emulation at 1280x900, (pointer: coarse) true, (hover: hover) false, and no hover or focus on the edit wrapper, main's computed opacity was 0; the pr's was 1.
• tapped the visible gear, confirmed the existing name and command, edited the command, saved, reloaded, and reopened the editor. the edit persisted. the recording shows tap, edit, and save; persistence was checked separately after reload.
• clicked the thread's Run Verify control. the running server opened the terminal in /home/user/t3code, wrote the edited command, and streamed project-action-edited-ok back to the client. the terminal and real codex response are visible below.
• checked neighboring desktop behavior in a separate fine-pointer context: opacity 0 at rest, 1 on hover, 1 after tabbing from Add action to the edit button. enter opened Edit Action; cancel closed it.
• checked the touch gear at 390x844 in dark mode. it remained visible and the action row was readable.
• ran vp run check:changed 5ffe04593166870d3ada2a83eb5fe55f0d192fc7 through blacksmith-check: format, lint, knip, and both affected typechecks passed. the explicit comparison ref uses this pr's parent because the isolated runner initially lacked origin/main history. hosted ci also reports 28 successful checks, 0 failing, 0 pending.

before: main, same project and saved action, no hover/focus. main's newer settings shell differs from the older pr head.

after: exact pr head, same project and saved action, no hover/focus.

short runtime transcript:

composer: Codex / gpt-6.1-sol
assistant: project actions verification ready.
ui: Run Verify
terminal.open: cwd=/home/user/t3code, status=running
terminal.write: printf 'project-action-edited-ok\n'
terminal output: project-action-edited-ok

Not verified

physical touch hardware, safari, native ios/android clients, and the electron shell on linux/macOS/windows were not exercised. touch and phone checks used real chrome with playwright input emulation. remote relay/tunnel connections, other providers, action shortcuts, worktree setup/settle automation, and preview-opening actions were outside this one-class visibility change. no performance claim is made.