Computer use with Denker
Summary
Computer use helps carry a request into the app where you need the result. Show Denker a form, name the fields to fill, and tell it which information to use. Relevant saved company details can reduce repeated typing, while a clear request keeps the work focused on those fields. You review the filled form before submitting. Using saved Memory requires Pro, including its trial; the available actions depend on your app and configured access.
Key points
- Start where the result belongs. Point at the form or mark the relevant fields. The visible reference and your words tell Denker what to work on, without making you describe its location from scratch.
- Put useful information to work. Supply the details once for the task, or use relevant facts already available in Memory. Computer use can apply those values to supported fields in the destination app.
- Keep the final decision with you. Ask Denker to stop at the filled draft, then check its values. You can correct the result and decide whether it is ready to submit.
Example: fill a form with saved company details
A supplier registration form asks for company details you have already shared with Denker. Reusing the relevant saved facts can spare you from entering the same information field by field. Show the form, identify the company and ask Denker to fill the contact fields for your review. Check the saved details first and provide any missing or changed information for the task.
- Open a supplier form and identify the company whose details belong in it.
- Review the relevant saved details in Memory before asking Denker to use them.
- Show the form and specify the fields you want filled, using a request such as the one below.
- Inspect the resulting fields and correct missing or outdated information before submitting yourself.
Fill these supplier contact fields with my saved company details. Leave information you cannot establish blank and stop before submitting.
This is an example instruction. It defines the scope you want; it does not guarantee every form exposes the same fields or accepts the same interaction. Check the company name, contact details and any required fields in the actual destination.
Read about Memory and the feature announcement.
Start with a task you can inspect
Open the app and the specific item you want help with. Use the controls taught in Denker's welcome guide to point, mark the relevant area, or add a voice or text instruction. Name the intended result: a draft, selected fields filled, or an explanation returned in a workspace frame.
Include enough context to distinguish the right account, document or form. A screenshot shows a captured view; hidden rows, other tabs and related records may require additional context or access. Keep the requested change small while learning how the workflow behaves in your setup.
Follow Getting Started for AI setup and platform-specific controls.
Check the access the task needs
Working through the screen can involve inspecting controls, clicking, typing or scrolling. On Mac, Screen Recording and Accessibility cover different parts of screen capture and computer control. A spoken request also needs microphone access. Follow the welcome guide and the permission requests shown by your installed app.
A supported browser connection can provide access to web content and browser actions. A service integration provides authorized tools for an account. Seeing an app on screen does not establish either connection. Check which account and tools are available when a task needs information beyond the visible view.
Grant access for the features you intend to use. If Denker asks to control your pointer, review that request before continuing. Access and confirmation steps vary with the action, platform and installed version; an app connection does not authorize every possible change.
See Integrations for account connections and the privacy policy for data handling.
Follow the work and review the result
During visible computer control, follow the target and avoid making competing edits to the same fields. Use the available Stop control if the task heads toward the wrong item or an unwanted action. Stopping the task does not undo changes that already happened.
Check the result where it belongs. For a form, inspect each intended value and any remaining validation errors. For a draft, open the saved draft. For a workspace result, compare the returned frame with the request and source material. Check the save state where relevant, and decide whether the work is ready for its next step.
See How Denker Works for tasks, agents and reviewable workspace frames.
Recover from a missing or uncertain result
- Inspect the destination before retrying. A change may have succeeded even when its completion message did not arrive.
- Preserve fields or drafts that already changed. Narrow the next request to the missing work so a retry does not duplicate it.
- If the source or target is wrong, stop and identify the correct account, item and requested change before continuing.
- If access is missing, review the relevant system permission or connection. Try one small step again after resolving the cause.
- If the action is unsupported in your setup, use a supported route or complete that step yourself. Repeating the same request does not add the missing capability.
Capability, app and platform limits
Available tools differ by app, operating system, account, chosen AI and installed build. Some tasks depend on a connected service; others need an accessible interface or visible computer control. Sign-in screens, dialogs and changed layouts can interrupt the flow. A successful example in one setup does not establish support for every app or guarantee a correct result.
Use a small, inspectable task to check your own workflow before extending it. Keep external submission or sending as a separate decision after you have reviewed the actual output.