Delegating tasks

How to ask

Write the outcome you want in plain language. Esan figures out the steps. The clearest requests share three things:

• The goal — what "done" looks like.
• The context — who it's for, the format, the constraints.
• The material — any files, links, or images that hold the answer.

"From this PDF, pull the pricing table and turn it into a clean comparison with a recommendation for a small team."

Attachments

Use the + button to attach files, images, or documents. Esan reads them as part of the task — spreadsheets, PDFs, images, code, and more. Attach the source material rather than pasting long excerpts.

Watching the work

As Esan works it shows what it's doing — researching, reading, building — so you can follow along and trust the result. When it's done you get a structured deliverable: a written answer with sources, plus any files it produced, ready to download.

Steering and stopping

• Steer mid-task. Send a follow-up while Esan is working to add a detail or change direction. It folds your input into the run.
• Stop anytime. Use the stop control to end a run. Nothing is lost — the session stays in your sidebar.
• Continue later. Pick up any past session from the sidebar and keep going; Esan keeps the thread.

Confirmations

For actions that have real-world effects — sending an email, making a purchase, posting to a connected app — Esan pauses and asks you to confirm first. You stay in control of anything that leaves the session. You can also choose to let a session run more autonomously when you want it to move without check-ins.

Getting better results

• Be specific about the format: a table, a one-pager, a deck, a CSV.
• State the audience: "for a non-technical client."
• Set limits: length, tone, language, deadline.
• For big jobs, consider a Project so files and context stay together across sessions.

Next: Specialists →