Grok Bot · Forms and login within chat
Have the agent pause when user input is needed, then continue the task after receiving it. Waiting and success are distinct states with clear boundaries.
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>You can now fill out forms and logins for your Bot without ever leaving the chat, with support for any password manager. · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fff6ee}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Motion and composition
Local motion · Composition rules
Orange means waiting; green means complete
Place a white phone in a warm orange glow, using high-contrast sans serif for form text. Stack the task request, action-required card, and Continue button vertically; switch the success confirmation to green.
Hand the entire authentication step to the user
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>You can now fill out forms and logins for your Bot without ever leaving the chat, with support for any password manager. · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#fff6ee}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="4" data-end="13"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>Expand the action-required card into a login form, then invoke password manager options. After selection, populate a placeholder account and masked password; show success only after submission finishes.
Have the confirmation answer the original task
Summarize the completed task and key results on the success card. Keep task names, dates, or objects consistent between request and confirmation, then cut to the brand last.
Adapt to other workflows requiring authorization
Use payment confirmation, resource access, or publishing approval. Replace form fields and confirmation content while preserving pause, user input, and resumed execution.
Sections and rhythm
Click a section to seek to it in the choreography example above.






Visual references · Discrete still frames
Creating other themes
- Suitable for workflows requiring authorization; preserve pause→user confirmation→resume→confirmation.
- Replace authentication form content; success must not precede submission.
Production constraints
Request / action-required card / continue button / login form / password manager / submission confirmation
- The agent hands control to the user only when authentication is encountered; the workflow resumes after user input.
- Transition from orange waiting to green completion while keeping information tied to the same task.
- Never display real passwords; use placeholder input when adapting.