docs: define ChatGPT message lifecycle and completion detection
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- documentation
Research direction
Start by locating the existing ChatGPT adapter, queue engine, and documentation structure; the issue names these components but no file paths or tests. Document the READY-to-NEXT_PROMPT lifecycle, semantic events, completion signals and fallbacks, failure paths, UI-automation/API boundaries, and a test strategy for selector or UI changes.
Written by the indexing model from the issue text.
Description
Objective
Document how QueueIt interacts with the ChatGPT web UI and how it decides that a response is complete.
Critical requirement
The next queued prompt must not be sent based on a fixed timeout.
QueueIt must observe reliable UI state and require a completion condition before advancing.
Lifecycle
READY
-> PROMPT_INSERTED
-> SUBMITTED
-> GENERATING
-> COMPLETED
-> NEXT_PROMPT
Failure paths must cover:
- submit failed
- generation stopped unexpectedly
- error response
- page changed
- conversation unavailable
- selector changed
- user manually sends a message
- user stops generation
- rate limit / service error
Design requirement
Keep selectors and DOM heuristics isolated in the ChatGPT adapter. The queue engine should receive semantic events such as submitted, generating, completed, and failed.
Important
The document must explicitly distinguish:
- DOM/UI automation
- unsupported private APIs
- official OpenAI APIs
QueueIt MVP is a browser UI automation tool and does not provide API access or extra ChatGPT usage.
Acceptance criteria
The completion detector has documented signals, fallbacks, failure behavior, and a test strategy for UI changes.
- Dominant language
- CSS
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ChinmayOnGithub/queueit
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ChinmayOnGithub/queueit#10 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in ChinmayOnGithub/queueit
Similar issues
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 3 days
-
type: documentation
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
spring-projects/spring-boot#52092 ·
Maintainers usually reply within 1 day
-
[Bug] 官网文档的图片挂了Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
DietrichGebert/ponytail#1063 ·
Maintainers usually reply within 3 days