Navigation
ELOWEN · Documentation

Last updated: October 20, 2026

Browse documentation · First useful conversation
Everyday use

First useful conversation

A useful first chat asks for one concrete outcome, gives Elowen the relevant context and leaves time to check the answer. For example, ask it to summarize a report into five key points for a non-specialist, rather than asking it to “help with work.”

Before you start

Open Chat to start a text-only conversation; you do not need to select a Project for that. Choose the Project that contains the files or environment you intend to use, and confirm it in the chat header before attaching files or requesting work there. Use only a Project you are authorized to access; a guide or administrator label does not grant access.

Gather the source material and decide what a successful answer should contain. You can describe the material in your message or attach relevant files. Do not include unrelated or sensitive information. If the task depends on a particular format, audience, deadline or restriction, say so explicitly.

Send a clear request

  1. Open Chat and start a new chat, or open the conversation you intend to continue.
  2. For work with Project files or its environment, confirm the selected Project in the chat header and switch to the intended one before attaching files or sending the request. For a text-only conversation, no Project selection is required.
  3. State the action and expected result: “Summarize the attached report in five bullets for a new customer; include the three dates and flag anything unclear.” Add essential context and constraints.
  4. Attach the relevant material if needed, wait until its upload finishes, then send the message. Follow any question or approval request that appears.

While Elowen is working, follow the conversation for questions, progress and the final response. A busy or waiting state is not completion. Answer a request for input; use the conversation’s Stop control if you want to stop active work.

Check the result

Compare the answer with your requested outcome and the original material. Check quoted facts, dates and calculations against their sources. If a detail is missing, ask a focused follow-up in the same conversation. Treat claims about changed files or completed actions as unconfirmed unless the conversation reports the result.

If something goes wrong

If the Project is unavailable, ask its administrator or computer owner to check your access. If a file upload fails, read the error and verify the selected Project before trying again. If the answer is vague, provide a concrete example of the format you want.

Continue with Web UI, Brain & Chat and Projects, Environments & GitHub.