Describe
Start with the symptom
Tell the agent what changed and when: “The laptop charges on one USB-C port but not the other.”
“My laptop stopped charging. Check whether it sees the battery and whether the charge level changes on AC power.” Think-Act can inspect the system and use what it finds to suggest the next test. No need to know which diagnostic command to run.
Open the activity log to see what the agent checked or changed.
Windows 10 and 11 now. Mac release planned.
Context
Task + source
Capability
Available tools
Activity
Visible progress
Review
Check result
Start with a goal. Add a file, website, or app name if the job needs one. The conversation and activity log stay with the same run.
Request
What to do
Context
What it can use
Run
Activity + tools
Review
Result + checks
What should be done, which boundaries matter, and what kind of result should come back.
Documents, files, screenshots, notes, recordings, transcripts, or checked extracted information the task genuinely depends on.
Supported tools, reusable Skills, and configured external capabilities available to that workflow where needed.
Supported task activity and the returned result stay available at the level needed to understand and review the run.
For a charging problem, the first question is whether the system detects the battery. That reading determines whether to inspect its reported health or look elsewhere. A reading alone cannot prove a charger is faulty.
Did the check answer your question?
For a power issue, compare the reported status before and after plugging in. If it stays unchanged, that narrows the next test.
Describe
Tell the agent what changed and when: “The laptop charges on one USB-C port but not the other.”
Define
Ask it to distinguish what the computer can measure from what would need a different cable, charger, or physical inspection.
Run
The agent can inspect the battery and power information the system exposes. If a reading is unavailable, it should say so.
Review
Ask which reading supports the suggested next test. An absent reading is not the same as a broken component.
Retest
If you switch ports or try a known-good charger, ask Think-Act to read the power status again. Compare the two readings before drawing a conclusion.
Try “Open the manufacturer’s parts site, find the adapter listed for this exact laptop model, and leave the page open. Don’t order it.”
Name the action, deliverable, analysis, or result you want from the run.
Attach the relevant documents, screenshots, files, notes, recordings, transcripts, or checked extracted information.
Mention required format, boundaries, destinations, available applications, or other conditions that genuinely affect how the task should be handled.
Task scope
Too open-ended
“Handle this project and take care of anything that needs doing.”
More reviewable
“Open the manufacturer’s catalog, find the adapter for this model, and stop at the product page.”
Success criteria
Simple task
A direct request may already be enough
“Open the support page for this model.”
Defined finish line
State what the result must contain
“Match the model and connector type. If several adapters match, show me the differences rather than choosing one.”
Success criteria are optional. They are useful when the reviewer needs a concrete way to tell whether the requested outcome was reached.
The agent can read local material, navigate web pages, and work with desktop apps. Skills give it instructions; optional connectors add tools.
Tools
Tools are supported capabilities the Desktop Agent can use while working on a task, such as inspecting supplied material or performing an available workflow action.
What matters
Skills
Skills keep useful instructions, conventions, and review checks for recurring work. They help a future task follow a method you have already understood and reviewed.
Best used after
Connectors
Connectors provide configured access to another supported capability when a task needs to interact beyond Think-Act's core desktop tools.
Before a task uses one
Simple relationship
Follow the tool calls in the activity log. Then check the open web page, the folder that changed, or the system reading behind the answer.
Review the observations, tool use, confirmations, reported changes, or other supported activity that matters to the task.
External changes may require confirmation or another configured approval policy depending on the capability and workflow involved.
Compare important output with the supplied source, intended destination, success criterion, or other evidence appropriate to the task.
Task
Requested outcome
Capability
What participated
Approval
What needed review
Result
What you verify
Pause a long investigation and choose Continue when you’re ready. Stopping a task does not reverse changes it already made.
01 · Inspect
Review the returned result and supported state or activity available around the run before deciding what happens next.
02 · Recover
Supported checkpoints or recovery controls may help with applicable state and operations. Do not assume every external action can be reversed.
03 · Improve
Clarify prerequisites, capability requirements, expected output, edge cases, and review checks while lessons from the run are still visible.
04 · Reuse
Reuse the instructions only after the workflow is understood and the prerequisites, checks, boundaries, and expected result have proved dependable.
A safer reuse rule
Understand the inputs, required capabilities, expected result, and review checks before converting a successful one-off run into reusable guidance. A future run still needs fresh context and review.
Find a compatible part, set up a project folder, or investigate a failing app. Each job has a different finish line; none requires a report.
Choose an outcome you can check in the app, browser, or folder itself.
Provide the working set and naming or grouping rules. File changes still depend on the relevant supported capability and permission.
Ask the agent to create project folders, copy in the approved assets, and leave ambiguous filenames where they are.
Supply the model number. Ask the agent to check the manufacturer’s site, open the matching part, and stop before checkout.
Use evidence that can be checked before anything is posted or reused.
Turn supplied evidence into a structured draft. Posting it elsewhere requires the relevant supported connector, permission, and any required confirmation.
Use the recording and transcript as process context, then verify the written steps before treating the documentation as a reusable procedure.
Open a desktop app and ask the agent to point out the right control. You can make the change yourself.
Writing, OCR, and recording can also be used on their own. Bring the Desktop Agent in when the result genuinely needs several coordinated steps rather than forcing a simple task into a larger workflow.
Compare Think-Act CapabilitiesWhat it can access, when it asks, and how to pick up a task later.
No. It acts on tasks you start or schedule, not on everything you do on your desktop.
It can use available file, browser, desktop, and document tools, plus trusted connectors you enable. Some actions require approval. See Security & Controls.
It cannot complete that step with the missing tool. Ask for a different deliverable or enable the required capability. See Skills & Integrations guide.
Use the activity log to see what the agent did, then check the result where it matters: the open website, the system reading, or the files it changed. Pausing or stopping the run does not undo a completed action.
No. A supported file edit may have a backup, but stopping or pausing a run won't undo a sent message or a browser action.
Yes. Save the instructions and checks as a Skill, then supply the new files on the next run.
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.
Try “Which drive is running low on space? Check how much is free and show me where to look next. Don’t change any files.”