How a job runs
What happens after you ask, how to steer the work and where a result or decision appears.
Ask and clarify
A message starts work in the conversation. OpenTag uses the request, relevant context, applicable skills and available tools. If a missing detail changes the job, it can ask you to choose or clarify.
For a complex request, it may show a plan or progress. You can follow up while it is working to correct the scope.
Work continues in the cloud
OpenTag runs work on hosted infrastructure and can use connected apps, files and a browser. Closing your laptop does not itself stop a run.
Longer jobs can take time because they read sources, make tool calls and produce files. Check the thread or the conversation in the web app for progress.
Some steps need you
An account may need connecting, a website may need sign-in, or an action may need a decision. OpenTag provides the relevant link or control.
Gmail sends require approval of the prepared email. A channel-originated email approval arrives privately in the requester's DM. Other supported writes can run without a card for every operation; see Approvals.
Read the result
The result may be an answer, file, source links or links to changed records. Check what completed and what remains unresolved. Results and sources explains citations and feedback.
Useful preferences and company evidence can inform future work through memory and the wiki. This happens separately from producing the immediate answer.
If the job stops
Check for a pending control, broken connection, exhausted credits or failure message. A routine may have held an action while completing the rest of its report.
Continue in the original thread with the missing information or a retry request. If a change might already have reached an external tool, check there before asking OpenTag to repeat it.
Conversation records, source data and learned memory have separate lifecycles. See Data handling rather than assuming the end of a run deletes them.