pingdotgg / pingdotgg/t3code

[Bug]: Creating a SnapShot while a question is being asked goes into the wrong textbox

Open
#12,271 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

accepted bug via-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce
  1. Start a thread in which the AI uses the built-in UI/tool call to ask you a question, where it takes over the text box with the custom question version

  2. Use a keyboard shortcut to take a snapshot

Expected behavior

The snapshot should end up attached to the question. Instead, the only way to attach a screenshot is to manually drag and drop one into the text box.

Actual behavior

The screenshot gets attached to the normal text box, and you can only see it once you submit your response to the question.

Impact

Major degradation or frequent failure

Version or commit

No response

Environment

No response

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in apps/web by reproducing the question-state flow: let the AI take over the text box, then use the keyboard shortcut to create a snapshot. Trace the snapshot attachment target and the custom question text box; done means the snapshot appears attached to the active question before submission, with the normal text box unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.