Assemble the evidence
Put the screenshot beside the log excerpt. Ask which error appeared first and what the user was doing at the time.
The export failed at 10:15. Ask Think-Act to find the first error in the app log, check available disk space, and separate what the machine shows from what still needs testing.
Windows 10 and 11 now. Mac release planned.
Developer workflow
A crash can involve an app, the operating system, and a changed configuration. Give the agent the symptom and time window so it can check the right evidence.
Complement the stack you already use
Keep coding, compiling, testing, source control, deployment, and specialist tooling in the systems built for them. Bring the surrounding context and preparation to Think-Act when that is the useful part.
Where the friction moves
Put the screenshot beside the log excerpt. Ask which error appeared first and what the user was doing at the time.
Record the failing sequence once. Ask for a ticket with steps, expected behavior, and actual behavior.
Ask which runtime version or system reading bears on the failure. Have the agent show the observation before proposing a fix.
Save the fields your team checks on every bug, then use the same instructions with the next report.
For broader examples of document, writing, OCR, recording, and multi-step workflows, see the Think-Act feature directory.
Debug context review
If the log says the output file could not be written, check the destination and available space before assuming the encoder is broken.
OCR can help extract text from error screenshots, build-output captures, or other visual messages. Compare important extracted text with the image when accuracy matters. Review OCR & Document Intelligence.
Keep what the logs or screenshots actually show distinct from possible causes, missing context, and checks that still need to be run.
A plausible explanation can still be wrong. Validate it against the application, code, environment, tests, documentation, or other evidence before applying a change.
Request four sections: environment, reproduction steps, observed behavior, and missing evidence. Leave unknowns blank.
Bug handoff
Source
Recording + notes
Prepare
Repro steps
Check
Missing context
Review
Ready to share
A recording is source material, not automatically perfect reproduction steps. Remove irrelevant actions, correct the sequence, and verify the expected and observed behavior before the handoff leaves your review. See Screen Recorder workflows.
Technical writing
Use supplied notes and context to prepare an issue draft, pull request summary, setup note, onboarding explanation, release update, or stakeholder-facing description.
Keep claims checkable
Check terminology, reproduction steps, versions, links, scope, behavior claims, and anything another developer or stakeholder may rely on.
Capture the smallest sequence that reproduces it. Add the clip to the ticket alongside the written steps.
Context
Logs, screenshots, config excerpts, recordings, notes, documents, or other technical material the task actually depends on.
Prepare
Organize evidence, separate observations from possibilities, draft checks, prepare issue text, or turn rough notes into documentation.
Review
Check extracted text, assumptions, terminology, reproduction steps, versions, proposed checks, and the next action yourself.
Next step
Apply manually, continue in your developer tools, or use an appropriate configured capability where a supported external action is genuinely required.
Many developer tasks can stop at Review. An external write or change is not automatically the next step.
Explore Desktop AgentExternal access is separate from prepared work
Do not assume repository, terminal, filesystem, database, issue-tracker, CI/CD, cloud, SSH, container, or production access is built in. What a task can use depends on the capabilities that are actually supported and configured. See Skills & Integrations for how external capabilities fit into Think-Act workflows.
Reusable developer method
Save a Skill with the fields your team needs, then give it fresh evidence for each issue.
Skill
Keep the sequence, prerequisites, warnings, and expected result clear for the next similar task.
Connector or tool
Bring in another system only when supplied context is not enough. Access still depends on configured trust and permissions.
Reviewed result
A successful tool call is not verified work. Review important results and external effects before relying on them.
Do not assume built-in GitHub, GitLab, repository, terminal, filesystem, database, Jira, CI/CD, cloud, SSH, Docker, Kubernetes, or other developer-service access. The integrations page explains how Skills and configured capabilities remain separate.
Share a redacted log excerpt rather than an entire environment file. Review the draft before posting it.
Avoid exposing API keys, tokens, passwords, or unrelated secrets in manually supplied prompts, screenshots, logs, or configuration unless they are intentionally required and permitted.
Review the model endpoint, connector runtime, account, service, storage, and sharing path involved before processing material covered by organizational policy.
Review the source, maintainer, runtime, setup, credentials, and resources a package may reach. Local execution changes where it runs, not whether the package deserves scrutiny.
Deployment, deletion, migration, production data changes, publishing, or other consequential actions deserve the safeguards and review practices appropriate to your environment.
For the broader trust model, including permissions, connector review, sensitive information, and consequential actions, see Security & Controls.
Compare the agent's timeline with a bug you already understand before using the same instructions on an open issue.
Good first developer tasks
Easy to verifyStart from supplied context before adding external capabilities. If you want to understand the broader workflow first, review Desktop Agent workflows. For current Free, Personal, or Business differences, use the plan comparison.
Choose the context
Pick one log, screenshot, recording, technical note, config excerpt, or small set of related material whose important details you know how to check.
Ask for one result
Ask for organized evidence, a list of plausible causes, checks to run, reproduction steps, an issue draft, release note, or another concrete artifact.
Diagnostic output
Organized evidence, plausible causes, assumptions, or checks to run.
Team-ready artifact
Reproduction steps, an issue draft, release note, or technical summary.
Review the output
Check extracted text, technical claims, versions, assumptions, proposed checks, reproduction steps, and anything another person may rely on.
Use the result
Paste the issue draft, run the checks, update your documentation, or continue manually in the developer system where the work actually belongs.
Reuse if useful
Save the reviewed instructions, checks, and output structure as reusable guidance. Add external capability later only when a specific access need appears.
How to use logs, recordings, and connectors without giving an agent unrestricted access.
Use it for work around the IDE: organize evidence, compare logs, produce a reproduction report, or document a workflow across apps. See Desktop Agent workflows.
Yes. Give it the relevant excerpt or screenshot and ask for the first error and the events just before it. See OCR & Document Intelligence.
It can use available file and shell tools. External trackers or databases need suitable access and permissions; a draft ticket needs neither. See Skills & Integrations.
Strip credentials, tokens, and unrelated customer data. Check the configured provider and your team's policy first. See Security & Controls.
No. Treat a suspected cause as a hypothesis. Check it against evidence or a reproducible test. See Desktop Agent page.
Yes. Ask for release notes, a reproduction checklist, or a technical handoff in your team's format. See Writing Assistant.
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 and compare plans.
Ask “Find the first error from this run. Check one system condition that could explain it. Don’t change the configuration.”