Project · Persistent agent

Hermes Persistent Agent

An investment-research agent that runs on schedule, saves reports, synchronizes versions and can recover after operational failures.

A useful agent has to survive the conversation

Hermes moves investment research from a one-off conversation into a scheduled cloud service that saves reports, synchronises versions and retains a recovery path when operations fail.

Treat recovery and observability as product capabilities

Only valuable recurring work stays online; deployment follows actual availability; recovery is treated as a product capability; and every completed state must be observable.

From prototype to long-running operation

The project narrowed the persistent-agent scope, changed hosting when capacity was unavailable, connected Discord, memory and scheduling, then added remote maintenance and observable execution records.

Scope the persistent work

A recorded operating stage with a visible completion state.

Deploy to an available environment

A recorded operating stage with a visible completion state.

Connect input, memory and schedules

A recorded operating stage with a visible completion state.

Add remote maintenance

A recorded operating stage with a visible completion state.

Verify execution and recovery records

A recorded operating stage with a visible completion state.

The operating record is part of the result

Scheduled research, saved reports and remote maintenance now operate in one environment. Deployment, task execution, synchronisation and recovery records remain available for review.