Academy → Using HermesOfficial documentation · clear explanation

1Password — Set up op CLI, sign in, and read or inject secrets

1Password — Set up op CLI, sign in, and read or inject secrets

Essential8 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains 1Password — Set up op CLI, sign in, and read or inject secrets as part of operating Hermes with explicit security boundaries. 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 Skill metadata, Reference: full SKILL.md, Requirements, then verify failure modes and version compatibility.

What do you need first?

You only need to know which files and accounts the agent may access.

What will you know?

A clear outcome before you read.

  • Understand 1Password — Set up op CLI, sign in, and read or inject secrets 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.

Skill
An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Official page description

Set up op CLI, sign in, and read or inject secrets

Topic map

What does the source say, and in what order?

  1. 01
    Skill metadata

    Start here to understand the core idea or structure.

  2. 02
    Reference: full SKILL.md

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

  3. 03
    Requirements

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

  4. 04
    When to Use

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

  5. 05
    Authentication Methods

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

  6. 06
    Service Account (recommended for Hermes)

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

  7. 07
    Desktop App Integration (interactive)

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

  8. 08
    Connect Server (self-hosted)

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

  9. 09
    Setup

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

  10. 10
    Hermes Execution Pattern (desktop app flow)

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

export OP_SERVICE_ACCOUNT_TOKEN="your-token-here" op whoami # verify — should show Type: SERVICE_ACCOUNT
export OP_CONNECT_HOST="http://localhost:8080" export OP_CONNECT_TOKEN="your-connect-token"
# macOS brew install 1password-cli # Linux (official package/install docs) # See references/get-started.md for distro-specific links. # Windows (winget) winget install AgileBits.1Password.CLI
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 “1Password — Set up op CLI, sign in, and read or inject secrets” 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?