Documentation

    Elara turns

    When an Elara turn changes your project, it becomes one saved version. The row's message is Elara: followed by the start of your prompt, and its author is Elara.

    When a version is created

    • One turn creates one version, however many rounds it took.
    • A turn that only reads or answers creates no version. Not every message adds a row.
    • If you stop a turn, or it ends in an error, edits that already landed are saved as a version.
    • If you had unsaved work when you sent the message, it's included in that version, so the version can hold your edits as well as Elara's.

    Go back after a turn

    To keep your own work separate, select Save before you send a message. Then:

    1. In History, select the row just below the Elara row. Read the diff to confirm what changed.
    2. Select Open on that row. The project returns to how it was.

    The Elara version stays in the list. Opening an earlier version doesn't remove it, so you can Open it again later. If you edit from the earlier version, Oplema creates a new branch. See Saves.

    Keep only part of a turn

    Stay on the Elara version and change the parts you don't want by hand, or ask Elara to change them. Versions can't be merged, and you can't take a single change out of a version by itself.

    Save your work. Go back any time.

    Echo is Oplema's version history. Guest copies are deleted about 30 days after the guest session started.