Point at What You Want to Code
Communicate a change by pointing, dispatch it directly to your coding tool, and stay involved as the work progresses.
Summary
Denker lets you start a coding task with what you can see. Point at an element or draw around it, then say what should change. Your marked screen and instruction give the coding tool a shared reference, reducing the effort of explaining locations and moving context between apps. Dispatch the request directly to your chosen coding tool, open the actual session, and continue working with it. You can follow its activity, clarify the request and review the changes as the work develops.
Key points
- Pointing makes the request easier to communicate. A mark identifies the exact button, spacing or broken state you mean; your words explain the change you want.
- Direct dispatch reduces the handoff. Send that context to Claude Code, Codex or OpenCode from Denker, then open the coding session to continue the work.
- Stay in control of the real work. See the coding session's state, respond to approval requests and send corrections or follow-ups. Review the changed files and running result before deciding what comes next.
Pointing gives the coding tool a shared reference
When you can see a problem, pointing is a natural way to explain it. Draw around the button that belongs lower on the page, mark the spacing that feels wrong, or show the state where a layout breaks. The coding tool gets a visible reference for your request, so you spend less effort describing where to look.
Your words add the intent: move this button below the paragraph, match the existing style, or keep these two controls aligned. The mark answers where; the instruction answers what should change. Together, they make a specific request you can return to when reviewing the result.
Send the request directly to your coding tool
Denker connects this visual request to the coding tool that will do the implementation. Choose your configured Claude Code, Codex or OpenCode destination and dispatch the request with its context. You can begin where you noticed the change and carry that reference into the coding session.
This reduces the work of assembling the same request across apps: describing the location, copying the instruction and attaching its visual reference. The coding tool still works in the project you select. Denker makes that handoff part of the interaction, so you can move from showing an idea to working on it.
Keep control as the coding work develops
Denker shows the coding session's state, including starting, running, waiting for approval and idle. Follow its output in the linked conversation and use the Open action, when available, to continue in the coding tool itself. This keeps the task connected to the session doing the implementation.
Send a correction or follow-up from the task panel. While a turn is running, you can queue a message for when it finishes. Respond to pending approval requests with Allow or Deny. Use Stop for a turn started from Denker; if the turn is running in your coding app, stop it there.
If the first version misses your intent, use the result as the next visual reference. Point at what still needs adjusting and explain the correction. Check the changed files and the running preview together, then decide whether to refine the work, accept it or move on to publishing.
Example: change a button from the page you are viewing
Suppose a consultation button belongs beneath the introduction. Keep the page in view and use it as the shared reference for the entire task.
- Point at the introduction and mark where the button should go.
- Say what you want, including the button wording, destination and styling.
- Choose the project and dispatch the request to your configured coding tool.
- Open the coding session, follow its implementation and review the local preview. Give a follow-up if the placement or behavior needs adjusting.
Add a Book a consultation button below this paragraph in the Forma site project. Match the existing button style and show the local result for review.
Connect your coding tool and project
Set up Claude Code, Codex or OpenCode in Denker, select the project and make its repository available to the tool. A marked screen supplies visual context; the project supplies the code to change. Your provider's subscription or usage charges remain separate from Denker.