Before submitting
Area
apps/web
Problem or use case
When writing prompts in the input textarea, the current font makes it harder to work with structured text such as code, markdown, JSON, shell commands, and multiline prompts.
A proportional font can make indentation, alignment, and whitespace less obvious, which increases the chance of formatting mistakes and makes prompts harder to review before sending.
Proposed solution
Use a monospace font for the prompt input textarea, or provide a setting to enable monospace input for users who write code-heavy prompts.
The main goal is for the prompt editor to preserve visual alignment and make whitespace, indentation, and line structure easier to read while typing.
Why this matters
This would benefit users who use t3code for programming-related prompts, debugging, editing code snippets, or writing structured instructions.
A monospace input would improve readability, reduce formatting errors, and make the prompt box feel more suited to developer workflows.
Smallest useful scope
Apply a monospace font only to the main prompt input textarea in the web app.
A first version does not need extra editor features—just changing the textarea font would already solve the core usability issue.
Alternatives considered
The current workaround is to draft prompts in an external editor such as Zed and then paste them into the app.
That works, but it adds friction and makes quick prompt editing inside the app less comfortable.
Risks or tradeoffs
A monospace font may look less friendly for casual users who mostly write plain-language prompts.
If that is a concern, a user preference or automatic behavior only for multiline/code-style input could be considered later. But even a simple default change for the textarea may be acceptable for a developer-focused tool.
Examples or references
Many developer tools and AI coding products use monospace fonts in prompt or editor inputs when users are expected to write code, commands, markdown, or structured text.
Contribution
Before submitting
Area
apps/web
Problem or use case
When writing prompts in the input textarea, the current font makes it harder to work with structured text such as code, markdown, JSON, shell commands, and multiline prompts.
A proportional font can make indentation, alignment, and whitespace less obvious, which increases the chance of formatting mistakes and makes prompts harder to review before sending.
Proposed solution
Use a monospace font for the prompt input textarea, or provide a setting to enable monospace input for users who write code-heavy prompts.
The main goal is for the prompt editor to preserve visual alignment and make whitespace, indentation, and line structure easier to read while typing.
Why this matters
This would benefit users who use t3code for programming-related prompts, debugging, editing code snippets, or writing structured instructions.
A monospace input would improve readability, reduce formatting errors, and make the prompt box feel more suited to developer workflows.
Smallest useful scope
Apply a monospace font only to the main prompt input textarea in the web app.
A first version does not need extra editor features—just changing the textarea font would already solve the core usability issue.
Alternatives considered
The current workaround is to draft prompts in an external editor such as Zed and then paste them into the app.
That works, but it adds friction and makes quick prompt editing inside the app less comfortable.
Risks or tradeoffs
A monospace font may look less friendly for casual users who mostly write plain-language prompts.
If that is a concern, a user preference or automatic behavior only for multiline/code-style input could be considered later. But even a simple default change for the textarea may be acceptable for a developer-focused tool.
Examples or references
Many developer tools and AI coding products use monospace fonts in prompt or editor inputs when users are expected to write code, commands, markdown, or structured text.
Contribution