[struong]

Removes the custom [data-v-ask-ai-container] overrides in src/styles/globals.ts, which pinned the floating Ask AI input into the right outline column at widths of 1376px and up and hid it below that.

Below 1376px the input was display: none, but cmd/ctrl+I still opened its menu. The menu was anchored to the hidden trigger, so it rendered at the top-left with no width.

With the overrides gone, Vocs's default applies: the input floats at the bottom center at every width, and cmd/ctrl+I opens the menu above it.

Checks: pnpm check:styles, pnpm check:types. Verified in a browser at 1600px and 1200px, with the input closed and opened through the shortcut.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
tempo-docs	Ready	Preview	Nov 12, 2026 2:28am UTC

[claude]

LGTM. This is a small CSS deletion that hands the Ask AI layout back to Vocs's default.

What was reviewed:

• All three removed [data-v-ask-ai-container] blocks in src/styles/globals.ts. Nothing else in the repo references ask-ai, so no other code depended on them.
• The --tempo-docs-shell-width and --tempo-docs-outline-width variables are still used in DocsNavigation.styles.ts and surfaces.styles.ts, so removing these rules doesn't leave them unused.
• The intended behavior change (the input is now visible below 1376px, which fixes the menu opened by cmd/ctrl+I being anchored to a hidden trigger) matches the code.
• Not done: the visual checks (pnpm check:styles and how it looks in a browser) weren't run in this review.

Extended reasoning...

The change only deletes 39 lines of global CSS overrides for the Ask AI container in one file, src/styles/globals.ts. It touches no security-sensitive surface. A search found no other references to the Ask AI container selector. The CSS variables it used are still referenced elsewhere. The intent is clear, the change is self-contained, no CODEOWNERS file covers the path, and no reviewer has raised an objection.