Timmy_Foundation/timmy-config
16
0
Fork 0
Code Issues 93 Pull Requests 6 Actions Packages Projects Releases Wiki Activity

[HARNESS] Enable Hermes v0.4.0 trajectory export for training pipeline #21

New Issue
Closed
opened 2026-03-26 19:57:09 +00:00 by perplexity · 9 comments
perplexity commented 2026-03-26 19:57:09 +00:00
Member
Copy Link

Context

Per research spike the-nexus#576, Section 2.1.2. Hermes v0.4.0 has a built-in trajectory compression pipeline (trajectory_compressor.py) that transforms raw agent execution logs into training-optimized formats — 10-50x compression with essential structure preserved. This is compatible with HuggingFace datasets, PyTorch DataLoader, and Atropos RL.

We are currently NOT capturing trajectories. The session_export() Huey task scrapes ~/.hermes/sessions/ for raw user→assistant pairs, but Hermes has a first-party trajectory export that's more structured and training-ready.

Task

Enable trajectory export in Hermes config:

/config set trajectory_export true

Set export destination in ~/.hermes/.env:

HERMES_TRAJECTORY_PATH=~/.timmy/training-data/trajectories/

Verify trajectories are being written after a few Hermes sessions.

Why this matters

  • Trajectories capture the full perceive→think→tool_call→result→response chain
  • Compressed format is directly compatible with our axolotl training pipeline
  • Closes the loop: Hermes operates → generates training data → improves model → better operations
  • This is the Nous Research-blessed way to do it, not our hand-rolled session_export()

Acceptance criteria

  • trajectory_export enabled in config
  • HERMES_TRAJECTORY_PATH set and directory exists
  • After 3+ Hermes sessions, trajectory files appear in export directory
  • Trajectory format is JSONL compatible with axolotl/ShareGPT

Pillar: Harness (training pipeline)

Research update — 2026-03-27

This is backbone work, not optional plumbing. Any OpenClaw or sidecar experiments must preserve export parity back into Hermes-native training artifacts.

## Context Per research spike the-nexus#576, Section 2.1.2. Hermes v0.4.0 has a built-in trajectory compression pipeline (`trajectory_compressor.py`) that transforms raw agent execution logs into training-optimized formats — 10-50x compression with essential structure preserved. This is compatible with HuggingFace datasets, PyTorch DataLoader, and Atropos RL. We are currently NOT capturing trajectories. The `session_export()` Huey task scrapes `~/.hermes/sessions/` for raw user→assistant pairs, but Hermes has a first-party trajectory export that's more structured and training-ready. ## Task Enable trajectory export in Hermes config: ``` /config set trajectory_export true ``` Set export destination in `~/.hermes/.env`: ``` HERMES_TRAJECTORY_PATH=~/.timmy/training-data/trajectories/ ``` Verify trajectories are being written after a few Hermes sessions. ## Why this matters - Trajectories capture the full perceive→think→tool_call→result→response chain - Compressed format is directly compatible with our axolotl training pipeline - Closes the loop: Hermes operates → generates training data → improves model → better operations - This is the Nous Research-blessed way to do it, not our hand-rolled session_export() ## Acceptance criteria - [ ] `trajectory_export` enabled in config - [ ] `HERMES_TRAJECTORY_PATH` set and directory exists - [ ] After 3+ Hermes sessions, trajectory files appear in export directory - [ ] Trajectory format is JSONL compatible with axolotl/ShareGPT ## Pillar: Harness (training pipeline) ## Research update — 2026-03-27 This is backbone work, not optional plumbing. Any OpenClaw or sidecar experiments must preserve export parity back into Hermes-native training artifacts.
Timmy was assigned by perplexity 2026-03-26 19:57:09 +00:00
Timmy commented 2026-03-26 20:00:48 +00:00
Owner
Copy Link

⚡ Dispatched to claude. Huey task queued.

⚡ Dispatched to `claude`. Huey task queued.
Timmy commented 2026-03-26 20:00:50 +00:00
Owner
Copy Link

⚡ Dispatched to gemini. Huey task queued.

⚡ Dispatched to `gemini`. Huey task queued.
Timmy commented 2026-03-26 20:00:51 +00:00
Owner
Copy Link

⚡ Dispatched to kimi. Huey task queued.

⚡ Dispatched to `kimi`. Huey task queued.
Timmy commented 2026-03-26 20:00:52 +00:00
Owner
Copy Link

⚡ Dispatched to grok. Huey task queued.

⚡ Dispatched to `grok`. Huey task queued.
Timmy commented 2026-03-26 20:00:53 +00:00
Owner
Copy Link

⚡ Dispatched to perplexity. Huey task queued.

⚡ Dispatched to `perplexity`. Huey task queued.
gemini commented 2026-03-26 21:00:31 +00:00
Member
Copy Link

🔧 gemini working on this via Huey. Branch: gemini/issue-21

🔧 `gemini` working on this via Huey. Branch: `gemini/issue-21`
grok commented 2026-03-26 21:00:39 +00:00
Member
Copy Link

🔧 grok working on this via Huey. Branch: grok/issue-21

🔧 `grok` working on this via Huey. Branch: `grok/issue-21`
grok commented 2026-03-26 21:00:44 +00:00
Member
Copy Link

⚠️ grok produced no changes for this issue. Skipping.

⚠️ `grok` produced no changes for this issue. Skipping.
Timmy commented 2026-03-28 04:53:05 +00:00
Owner
Copy Link

Closing during the 2026-03-28 backlog burn-down.

Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.

Closing during the 2026-03-28 backlog burn-down. Reason: this issue is being retired as part of a backlog reset toward the current final vision: Heartbeat, Harness, and Portal. If the work still matters after reset, it should return as a narrower, proof-oriented next-step issue rather than stay open as a broad legacy frontier.
Timmy closed this issue 2026-03-28 04:53:06 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
assigned-claw-code
Queued for Code Claw (qwen/openrouter)
 assigned-kimi
Dispatched to Kimi via OpenClaw
 assigned-sonnet
claw-code-done
Code Claw completed this task
 claw-code-in-progress
Code Claw is actively working
 enhancement
epic
kimi-done
Kimi completed this task
 kimi-in-progress
Kimi is actively working on this
 lazzyPit
Lazarus Pit automated recovery system
 research
sonnet-ready
velocity-engine
Auto-generated by velocity engine
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
KimiClaw Rockachopa Timmy allegro antigravity bezalel claude claw-code codex-agent ezra gemini google grok groq hermes kimi manus perplexity sonnet
No Assignees Timmy
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Timmy_Foundation/timmy-config#21
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?