Pre-submit Checks
- I have searched Warp bugs and there are no duplicates
- I have searched Warp known issues page and my issue is not there
- I have an issue with AI and have included the debugging ID (Optional, but helps expedite the AI quality fix). Debugging ID instructions
- I have technical issue and have included the logs (optional, but helps expedite the bug fix). Log instructions
Describe the bug
Several user-facing strings in the Warp client contain typos, grammar mistakes, or wording that is inconsistent with the rest of the UI. All of them are still present on master (96d816ad).
I'd like to fix all of them in a single PR. Before I open it, could a maintainer confirm that this is OK, or let me know if you'd prefer to split it up or leave any of these as they are?
Typos and grammar
| Location | Current | Proposed | Where it appears |
|---|---|---|---|
app/src/auth/auth_override_warning_body.rs:31 | "any personal Warp drive objects ... from this anonymous session with be permanently deleted." | "Warp Drive" / "will be" | Auth override warning modal |
app/src/settings_view/features_page.rs:7728 | "using fraction scaling (ex: 125%)" | "fractional scaling" | Settings > Features (Wayland) |
app/src/settings_view/privacy_page.rs:68 | "for potential sensitive" | "for potentially sensitive" | Settings > Privacy |
app/src/settings_view/keybindings.rs:1029 | "in a side pane at anytime." | "at any time." | Settings > Keyboard shortcuts |
app/src/settings_view/mcp_servers/list_page.rs:99 | "Once you add a MCP server" | "an MCP server" | Settings > MCP servers (empty state) |
app/src/auth/paste_auth_token_modal.rs:274 | "from the browser to get complete login." | "to complete login." | Paste auth token modal |
app/src/terminal/view.rs:26838 | "Can not invoke environment variable subshell ..." | "Cannot invoke ..." | Error toast |
app/src/terminal/shared_session/viewer/network.rs:1124, :1136 | "Please ask sharer to reshare to continue." | "ask the sharer" | Shared session viewer error |
app/src/workspace/view.rs:22564 | "unable to launch the new installed version." | "newly installed version" | Update failure message |
app/src/ai/facts/view/rule.rs:59 | "Your rules are disabled ... You can turn it back on anytime." | "turn them back on" | Rules page disabled banner |
Inconsistent capitalization / product names
| Location | Current | Proposed | Where it appears |
|---|---|---|---|
app/src/settings_view/appearance_page.rs:3119 | "restart Warp for MacOS" | "macOS" | Settings > Appearance |
app/src/settings_view/features_page.rs:7572 | "Honor linux selection clipboard" | "Linux" | Settings > Features |
app/src/workspace/view/agent_cli_launch_modal/view.rs:81 | "better behavior for REPLS" | "REPLs" | Agent CLI launch modal |
app/src/context_chips/mod.rs:343, :349 | "Svn Branch", "Svn Uncommitted File Count" | "SVN ..." | Prompt context chip names |
app/src/context_chips/node_version_popup.rs:241 | "No node versions installed" | "No Node.js versions installed" (matches "Node.js versions" at :192 in the same popup) | Node version popup |
Changes that also need a test update
| Location | Current | Proposed | Where it appears |
|---|---|---|---|
app/src/ai/blocklist/inline_action/requested_command.rs:1573-1574 | "OK if I call MCP tool {tool} on server {server}" (no "?") | Add "?" (matches "OK if I call this MCP tool?" at :91); update requested_command_tests.rs:78, :86 | MCP tool approval prompt |
app/src/ai/orchestration/validation.rs:90 | "The pi harness is not available." | "The Pi harness ..." (matches "Pi child agents" at :87); update validation_tests.rs:41 | Orchestration config |
Apart from the two test files listed above, none of these strings are used in tests, settings keys, or telemetry event names, so the fix would be string-only.
To reproduce
- Open the files and lines listed above on
master. - Or open the corresponding UI in Warp (for example Settings > Features, Settings > Privacy, Settings > Keyboard shortcuts) and read the text.
Expected behavior
User-facing strings are free of typos and use consistent spelling for product names (macOS, Linux, Warp Drive, SVN, Node.js, Pi).
Screenshots, videos, and logs
No response
Operating system (OS)
macOS
Operating system and version
N/A - UI copy issue found by reading the source
Shell Version
No response
Current Warp version
No response
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
If this is approved, I'll open one PR with all of the changes above and include before/after screenshots for the strings that can be easily shown in the UI.
Does this block you from using Warp daily?
No
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
No response
@ttrweb
Here's what I found while triaging this issue:
Thanks for the detailed copy audit. I verified this appears to be a source-level UI copy cleanup rather than an environment-specific bug; no extra reporter info is needed for triage. A maintainer can still decide whether to split the cleanup PR, but the issue is actionable as filed.
Maintainer details
I concluded that the issue is an actionable UI copy bug covering hard-coded Warp client strings with typos, grammar issues, and inconsistent product capitalization..
Triage summary
This is an actionable UI copy bug. The report identifies hard-coded client strings with typos, grammar issues, and inconsistent product-name capitalization, and code inspection confirmed representative examples at the referenced locations.
Reproducibility
High. The issue can be reproduced by reading the cited source literals or opening the affected UI surfaces; it is not dependent on the reporter's environment.
Likely root cause
The affected copy is embedded directly in Warp client UI string literals across several modules. Most fixes are string-only; the MCP tool approval prompt and Pi harness validation message also require updating existing test expectations.
Duplicate check
I enumerated the repository's open issues and did not find two or more likely duplicates. Narrow exact-term candidates were unrelated to this cross-surface copy cleanup.
Factory auto-implement eligibility
Not queued for factory auto-implementation: this fails the localized-scope gate because it spans many unrelated UI surfaces and test files rather than one component or subsystem.
This is my automated analysis and may be incorrect. A maintainer will verify the details.
Powered by Oz