Choose
Pick one process or issue worth showing
Define a useful starting point and an understandable end. Keep unrelated applications, tasks, and information outside the capture where possible.
When a teammate asks which button to click, show them. Choose the screen and audio source, record the steps, and play the clip back before sharing it.
A recording shows what happened, not always why. Review generated instructions before a demonstrated sequence becomes documentation another person is expected to follow.
Windows 10 and 11 now. Mac release planned.
Recording workflow
Choose your source, check the audio level, and start recording. Pause while you wait for a page to load.
Observation becomes guidance only after review
A recorded action may be accidental, environment-specific, optional, or missing an explanation. Review adds the context that the screen alone cannot provide.
Choose
Define a useful starting point and an understandable end. Keep unrelated applications, tasks, and information outside the capture where possible.
Capture
Capture the visual process instead of reconstructing the order later. Use narration only when reasoning, expectations, or failure context would otherwise be invisible.
Prepare
Prepare a draft SOP, bug reproduction guide, checklist, workflow summary, transcript where narration exists, or another supported working format.
Review
Correct missing steps, accidental actions, unclear wording, prerequisites, warnings, and expected outcomes before the documentation is shared or relied on.
Reuse
Share the reviewed document, keep it as working knowledge, refine it with another Think-Act feature, or preserve a stable method as reusable guidance.
A walkthrough shows how to finish a task. A bug recording shows the exact click and what happened instead.
Repeatable procedure
Prepare ordered steps, prerequisites, useful checks, warnings, and expected outcomes from a process that has actually been demonstrated.
Review steps and prerequisites before the draft becomes operational guidance.
QA & troubleshooting
Prepare a clear sequence showing how an issue was reached, what was expected, what happened instead, and which visible state may help another reviewer investigate.
Quick reuse
Reduce a demonstrated sequence to the steps and checks someone needs when a full SOP would be unnecessarily heavy.
A concise checklist can still need prerequisites or warnings when skipping them would change the result.
When narration exists
Use spoken context where available to preserve reasoning the screen could not show. A silent recording can still support useful visual documentation without inventing narration that was never provided.
Internal knowledge
Prepare a shorter explanation of what the process does, when it is useful, and the main steps someone should understand before following the full procedure.
Capture scope
Record one process at a time. Close unrelated tabs and notifications so viewers can follow the cursor.
A tighter recording is easier to review, easier to document, and less likely to contain unrelated information.
Explain why a step is required, what outcome you expect, why an option was chosen, what went wrong, or what another person should check. A clear silent workflow can still be useful.
Close unrelated applications and avoid exposing credentials, customer information, private messages, confidential documents, or other content the process does not require.
Check that the recording contains the intended process and does not expose information that should be removed or handled differently.
Look at the selected display and audio input. Make a short test clip if narration is important.
Recording
Captured process
Transcript
Narration when present
Draft
SOP · report · checklist
Review
Checked result
The visual process remains the reference for order, interface state, outcomes, and any captured narration.
Spoken explanation can provide additional text context without making narration a requirement for every recording.
SOPs, reproduction steps, summaries, checklists, and other supported outputs remain editable working drafts.
Compare the draft with the recording, resolve unclear steps, and remove information that should not travel with the final documentation.
Menus, timing, and unexpected dialogs are easier to understand when you can see them.
Recording alone
Video preserves the visual sequence, interface state, timing, and any narration. It remains valuable when someone needs to see the task exactly as it appeared.
Still requires
Think-Act workflow
Keep the original recording as evidence while preparing written steps, summaries, checklists, or other useful documentation that can be edited as the process becomes clearer.
What gets added
Give the agent your step notes and ask for a numbered procedure. Check the draft against the clip before handing it to someone new.
A Skill preserves the reviewed method
It can keep instructions, prerequisites, conventions, warnings, checks, and expected outcomes. It does not create access to files, applications, accounts, connectors, or permissions.
Observe
Use the recording as evidence of the demonstrated sequence rather than relying on memory or a reconstructed description.
Document
Add the instructions, prerequisites, expected outcomes, warnings, and context the recording alone did not make explicit.
Review
Remove accidental steps, identify exceptions, note conditions that change the process, and keep actions requiring judgment or approval visible.
Reuse
Save a reviewed method as reusable guidance where appropriate. Future external actions still depend on the capabilities, permissions, and approvals available to that workflow.
Reusable instruction is not permission. Recording a workflow or saving a Skill does not authorize consequential external actions.
Show a new hire an export setting, demonstrate an issue to support, or keep a reference for a task you do once a quarter.
Capture a routine process from a useful starting point to a visible result, then prepare an SOP draft with the steps and checks another operator needs.
Preserve the path to an issue together with the visible state, expected result, actual result, and the context another person needs to reproduce it.
Demonstrate how a real task is performed, then prepare a concise checklist or training draft so a teammate does not have to infer every step from the recording.
Preserve what the user saw and what was already tried, then turn that context into a shorter handoff a developer, specialist, or next support tier can review.
Demonstrate a feature or internal tool, then prepare tutorial notes, a concise summary, or a knowledge-base draft that can be edited for its audience.
Record a task you rarely perform, then keep a short reviewed guide for the next time instead of reconstructing the process from memory.
Use sample records when possible. Watch for names, messages, or other people’s audio before sharing the file.
Storage, processing location, model endpoints, connectors, and data flow depend on the configuration you use. Review data-handling guidance and data-flow guidance before recording sensitive workflows.
Close unrelated applications and tabs, silence unnecessary notifications, and record only the task you need.
Do not intentionally capture passwords, tokens, private messages, or other information that should not be present in the recording.
Follow organizational, contractual, or legal requirements that apply to recording people, customer information, accounts, or internal systems.
Inspect the recording and generated material, then use storage and sharing practices approved for the information involved.
Replay the clip to find the step that failed. Give the Desktop Agent the error text and time so it can check the app log. The recording shows what you saw; the log can help explain why.
It preserves sequence, visible state, and explanation that may be difficult to reconstruct from notes alone.
A recording does not bypass permissions, connector trust, confirmations, or review requirements for whatever happens next.
Use the captured sequence and visible state to identify what happened, what remains unclear, and what should be checked before trying again.
Turn the useful parts of the recording into a shorter brief covering the goal, observed behavior, important steps, and unresolved questions.
Once the process is understood, use the supplied notes or transcript to refine an SOP, tutorial, support note, or knowledge-base draft.
When reviewed instructions remain dependable, preserve the prerequisites, warnings, expected outcomes, and checks needed to reuse the method as a Skill.
Control boundary
If the next workflow changes files or external systems, apply the permissions, connector trust, approvals, and review appropriate to that action. Recording the process does not authorize the next step.
Review Controlled AutomationAudio, walkthroughs, and turning a recording into useful documentation.
No. Record a bug, a handoff, or a process that's hard to explain in writing.
No. A silent clip can be enough. Add microphone or system audio only if it helps the viewer.
Use the clip as the reference and give the agent your notes to draft a checklist. Check the steps against what the recording shows.
A summary can miss a dialog, a wait, or a final confirmation. Replay those steps before another person relies on the instructions.
Yes. Save the checked instructions, expected output, and prerequisites as a Skill.
Close unrelated windows, choose the capture area carefully, and check what is audible as well as what is visible.
You can try Think-Act on 64-bit Windows 10 or 11. The Mac release is planned for Q1 2027; see Downloads for availability. See downloads page.
Show one setting that a teammate often misses, then check that the label is readable on playback.