Academy → Using HermesOfficial documentation · clear explanation

Sessions

الجلسات

Beginner to advanced29 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Sessions as part of using Hermes and understanding its behavior. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?

For hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect How Sessions Work, What Counts Toward Context, Session Sources, then verify failure modes and version compatibility.

What do you need first?

Start with installation if you have not run Hermes yet.

What will you know?

A clear outcome before you read.

  • Understand Sessions without assumed prior knowledge.
  • Separate the source description from what still needs testing in your environment.
  • Read the first command and identify its inputs and outputs before copying it.
Lesson terms

Short definitions before the details.

Session & memory
A session holds conversation context, while memory keeps selected facts that should persist.
Official page description

Session persistence, resume, search, management, and per-platform session tracking

Topic map

What does the source say, and in what order?

  1. 01
    How Sessions Work

    Start here to understand the core idea or structure.

  2. 02
    What Counts Toward Context

    Read this after the foundation, then connect it to the previous step.

  3. 03
    Session Sources

    Read this after the foundation, then connect it to the previous step.

  4. 04
    CLI Session Resume

    Read this after the foundation, then connect it to the previous step.

  5. 05
    Continue Last Session

    Read this after the foundation, then connect it to the previous step.

  6. 06
    Resume by Name

    Read this after the foundation, then connect it to the previous step.

  7. 07
    Resume Specific Session

    Read this after the foundation, then connect it to the previous step.

  8. 08
    Resume in a Specific Directory

    Read this after the foundation, then connect it to the previous step.

  9. 09
    Resume Restores the Working Directory

    Read this after the foundation, then connect it to the previous step.

  10. 10
    Filtering Sessions by Workspace

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

# Resume the most recent CLI session hermes --continue hermes -c # Or with the chat subcommand hermes chat --continue hermes chat -c
# Resume a named session hermes -c "my project" # If there are lineage variants (my project, my project #2, my project #3), # this automatically resumes the most recent one hermes -c "my project" # → resumes "my project #3"
# Resume a specific session by ID hermes --resume 20250305_091523_a1b2c3d4 hermes -r 20250305_091523_a1b2c3d4 # Resume by title hermes --resume "refactoring auth" # Resume the most recent session — same lookup as -c hermes --resume latest # Or with the chat subcommand hermes chat --resume 20250305_091523_a1b2c3d4
Try it now

Read the first command and identify its inputs and outputs before copying it.

Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Sessions” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?