Hermes BibleUnofficial Docs
← All docs Docs / Developer Guide

Trajectory Format

Trajectory Format Hermes Agent saves conversation trajectories in ShareGPT compatible JSONL format for use as training data, debugging artifacts, and reinforcem

Developer Guide
Section
Developer Guide
Source
hermesbible.com/docs/developer-guide/trajectory-format

Trajectory Format Hermes Agent saves conversation trajectories in ShareGPT compatible JSONL format for use as training data, debugging artifacts, and reinforcem

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. File Naming Convention
  2. JSONL Entry Format
  3. CLI/Interactive Format (from _save_trajectory)
  4. Batch Runner Format (from batch_runner.py)
  5. Conversations Array (ShareGPT Format)
  6. Complete Example
  7. Normalization Rules
  8. Reasoning Content Markup
  9. Tool Call Normalization
  10. Tool Response Normalization
  11. System Message
  12. Loading Trajectories
  13. Loading for HuggingFace Datasets
  14. Controlling Trajectory Saving

Section map

File Naming Convention

Maps file naming convention to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

JSONL Entry Format

Maps jsonl entry format to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

CLI/Interactive Format (from _save_trajectory)

Maps cli/interactive format (from _save_trajectory) to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Batch Runner Format (from batch_runner.py)

Maps batch runner format (from batch_runner.py) to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Conversations Array (ShareGPT Format)

Maps conversations array (sharegpt format) to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Complete Example

Maps complete example to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Normalization Rules

Maps normalization rules to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Reasoning Content Markup

Maps reasoning content markup to the Developer Guide documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Developer Guide doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: File Naming Convention, JSONL Entry Format, CLI/Interactive Format (from _save_trajectory), Batch Runner Format (from batch_runner.py), Conversations Array (ShareGPT Format). Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: trajectory, format, saves, conversation, trajectories. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitDeveloper Guide documentation

Use when you need orientation for trajectory format before applying exact upstream commands.

Verify firstFile Naming Convention

Open the source anchor for File Naming Convention and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Developer Guide, then open the linked source page for exact current syntax.
  2. Start with the source section for File Naming Convention; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for JSONL Entry Format if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page