Memory explorer
Explore what your agent remembers
Search remembered facts, inspect their context, and preview what an agent would receive for a task.
| What was remembered | Kind | Context | Updated | Status |
|---|---|---|---|---|
| Initiated fresh running session | Note | Tied to a work session | 4h ago | Active |
| The agent successfully initiated a fresh running session that will remain active. This was achieved by following the specified task prompt. | Work session | Tied to a work session | 4h ago | Active |
| Initiated fresh running session | Note | Tied to a work session | 5h ago | Active |
| Initiated fresh running session | Note | Tied to a work session | 5h ago | Active |
| The agent successfully initiated a fresh running session that will remain active. This was achieved by following the specified task prompt. | Work session | Tied to a work session | 5h ago | Active |
| The agent successfully initiated a fresh running session that will remain active. This ensures that the required processes are continuously operational. | Work session | Tied to a work session | 5h ago | Active |
| Initiated fresh running session | Note | Tied to a work session | 5h ago | Active |
| The agent successfully initiated a fresh running session that will remain active. This ensures ongoing operations without interruption. | Work session | Tied to a work session | 5h ago | Active |
| Conducted cleanup proof | Note | Tied to a work session | 10h ago | Active |
| Verify session state | Note | Tied to a work session | 10h ago | Active |
| The agent successfully completed the cleanup proof for a stale running session. This involved verifying the state and ensuring proper termination of the session. | Work session | Tied to a work session | 10h ago | Active |
| Confirmed the session was stale | Note | Tied to a work session | 11h ago | Active |
| Proceed with cleanup | Note | Tied to a work session | 11h ago | Active |
| The agent successfully completed the cleanup proof for the stale running session. This involved verifying that the session was indeed stale and confirming its removal. | Work session | Tied to a work session | 11h ago | Active |
| Conducted cleanup proof | Note | Tied to a work session | 11h ago | Active |
| Verify session state | Note | Tied to a work session | 11h ago | Active |
| The agent successfully completed the cleanup proof for a stale running session. This involved verifying the state and ensuring that the session was properly handled. | Work session | Tied to a work session | 11h ago | Active |
| Confirmed the session was stale | Note | Tied to a work session | 11h ago | Active |
| Proceed with cleanup | Note | Tied to a work session | 11h ago | Active |
| The agent successfully completed the cleanup proof for the stale running session. This involved verifying that the session was indeed stale and confirming its removal. | Work session | Tied to a work session | 11h ago | Active |
| Mark the task as Done in Notion | Note | Tied to a work session | 2d ago | Active |
| Keep the Agent Time Capsule memory provider active | Note | Tied to a work session | 2d ago | Active |
| Josh prefers the Agent Time Capsule provider to remain active alongside Hermes built-in memory, with automatic relevant-memory prefetch and conversation/tool-event syncing enabled. | Preference | Tied to a work session | 2d ago | Active |
| Josh prefers the Agent Time Capsule provider to remain active | Note | Tied to a work session | 2d ago | Active |
| The agent confirmed the Agent Time Capsule memory provider will remain active, allowing for automatic memory prefetch and syncing. Additionally, a workbook with 50 verified business leads was successfully compiled and marked as completed in Notion. | Work session | Tied to a work session | 2d ago | Active |
| The agent successfully retrieved the username of the account on the VPS. The username is 'strohm'. | Work session | Tied to a work session | 2d ago | Active |
| Josh is located in Altoona, Pennsylvania, and wants Strohm Partners to target prospective business clients across Central Pennsylvania. | Fact | Tied to a work session | 2d ago | Active |
| Keep the Agent Time Capsule memory provider active alongside Hermes built-in memory, including automatic relevant-memory prefetch and syncing conversation turns/tool events. | Note | Tied to a work session | 2d ago | Active |
| Remove all components related to Twenty CRM | Note | Tied to a work session | 2d ago | Active |
| Log completion of task in Notion | Note | Tied to a work session | 2d ago | Active |
| Twenty CRM has been successfully removed from the VPS along with all related components. This includes the containers, Docker network, Redis volume, images, and associated files, with no backups retained. | Work session | Tied to a work session | 2d ago | Active |
| Initiated fresh running session | Note | Tied to a work session | 3d ago | Active |
| Initiated fresh running session | Note | Tied to a work session | 3d ago | Active |
| The agent successfully initiated a fresh running session that will remain active. This ensures that the required processes can continue without interruption. | Work session | Tied to a work session | 3d ago | Active |
| The agent successfully initiated a fresh running session that will remain active. This ensures ongoing operations without interruption. | Work session | Tied to a work session | 3d ago | Active |
| Use Agent Time Capsule additively with Hermes local memory: search relevant history before meaningful tasks, inspect prior rationale and evidence before unfamiliar changes, remember/update/forget selected durable non-secret facts, record important technical decisions with rationale, rejected alternative, and affected area, never store secrets, and continue locally with a clear limitation if the service is unavailable. | Procedure | General memory | 3d ago | Active |
| terminate the stale session | Note | Tied to a work session | 3d ago | Active |
| The agent conducted a cleanup proof for a stale running session. It focused on verifying the status and ensuring proper termination of the session. The process was completed successfully without any issues. | Work session | Tied to a work session | 3d ago | Active |
| terminate stale session | Note | Tied to a work session | 3d ago | Active |
| document cleanup process | Note | Tied to a work session | 3d ago | Active |
| The agent conducted a cleanup proof for a stale running session. It focused on verifying the status and ensuring proper termination of the session. The process involved checking for any lingering processes and confirming their cleanup. | Work session | Tied to a work session | 3d ago | Active |
| Keep Hermes built-in local memory enabled and primary; use Agent Time Capsule only as an additional MCP source for selected durable non-secret cross-machine context, without automatic local-session recording. — Preserves private and machine-local context while enabling explicit cross-machine memory search and selected writes. | Constraint | General memory | 3d ago | Active |
| Agent Time Capsule MCP connection verification completed successfully on 2026-09-18; Hermes can search existing durable memories and write a new durable verification memory. — The user explicitly asked to create a quick memory verifying that the MCP connection is working. | Constraint | General memory | 3d ago | Active |
| Expose only the authenticated Agent Time Capsule MCP endpoint at https://capsule.joshstrohm.me/mcp through the existing Nginx TLS vhost. | Note | Tied to a work session | 5d ago | Active |
| The agent successfully set up the Agent Time Capsule app on the VPS, making it accessible via a secure HTTPS endpoint. The integration documentation was updated, and specific instructions were provided for connecting a local Hermes agent to the Time Capsule as an additional memory source. The setup ensures that only authenticated requests can access the MCP service, while other service ports remain secure. | Work session | Tied to a work session | 5d ago | Active |
| Keep Hermes built-in local memory enabled and primary; use Agent Time Capsule only as an additional MCP source for selected durable non-secret cross-machine context, without automatic local-session recording. | Note | General memory | 5d ago | Active |
| Expose only the authenticated Agent Time Capsule MCP endpoint at https://capsule.joshstrohm.me/mcp through the existing Nginx TLS vhost; keep Recorder, Librarian, Postgres, and raw service ports loopback-only. | Note | Tied to a work session | 5d ago | Active |
| Create a logging skill for GTD projects and tasks | Note | Tied to a work session | 8d ago | Active |
| Archive the Stackwright Technical Landscape project | Note | Tied to a work session | 8d ago | Active |
| The agent confirmed access to the user's Notion account and retrieved information about current projects and tasks. The user requested the removal of the 'Stackwright Technical Landscape' project and the creation of a skill to log work within the GTD projects and tasks. The agent successfully archived the project, created the logging skill, and updated the shared GTD System page with the logging protocol. | Work session | Tied to a work session | 8d ago | Active |
| Create a verification memory | Note | Tied to a work session | Sep 18, 2026 | Active |
| Agent Time Capsule MCP connection verification completed successfully | Note | Tied to a work session | Sep 18, 2026 | Active |
| The agent successfully verified access to the Agent Time Capsule memory system and confirmed that the MCP connection is working. A new memory was created to document this verification. | Work session | Tied to a work session | Sep 18, 2026 | Active |
| Agent Time Capsule MCP connection verification completed successfully on 2026-09-18; Hermes can search existing durable memories and write a new durable verification memory. | Note | General memory | Sep 18, 2026 | Active |