Hermes Base Camp

Build the harness, not the folklore.

This repo is not a running agent system yet. It is the staging ground for an honest Hermes fork: better sessions, better continuity, better deployment posture, and fewer theatrical status claims. The façade is paced to the actual state of the work.

Surface Static and honest
Model routing OpenRouter first
Host posture API-backed agents
Big risk Infra drift
Validated claims are narrow.
  • The repo currently contains notes and report stubs, not a real Clojure application or live agent harness.
  • The right deployment shape today is a small static façade plus provenance, not a fabricated dashboard.
  • The host described in project notes is suitable for API-backed agents and operational surfaces, not local heavy inference.

OpenRouter Wiring

Provider choice is normalized around OpenRouter so later harness work does not hard-bind itself to Anthropic transport. Use OpenRouter-compatible environment variables and pass an explicit base URL.

OPENROUTER_API_KEY=your_key_here
OPENROUTER_BASE_URL=https://openrouter.ai/api/v1
OPENROUTER_MODEL=anthropic/claude-3.7-sonnet
OPENROUTER_APP_NAME=hermesbase
OPENROUTER_SITE_URL=https://hermesbase.dissemblage.art

That keeps model selection flexible while preserving access to Anthropic models through OpenRouter when you want them.

Next reliable moves

  • Split harness, workbench, bots, and façade into clear concern boundaries with real remotes.
  • Replace synthetic report logs with generated telemetry only after a real process emits it.
  • Add a thin service layer in Rust, Elixir, or Clojure that reads OpenRouter config and exposes one narrow, testable agent endpoint.
Known brittle points
  • No git remote is configured, so continuity is local-only until the repo gets a private upstream.
  • The existing report files overstate system reality and should not be treated as operational truth.
  • The target VPS notes already show disk and reboot pressure, which makes premature long-lived agents brittle.

Provenance

Every durable artifact in this repo should point back to a recoverable session trail and concrete git identity. This page reads that from the adjacent provenance.json.

Project
loading
Repo Path
loading
Remote
loading
Branch
loading
Commit
loading
Session
loading