> For the complete documentation index, see [llms.txt](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/prd/phase_41/session_07_hermes_shell_identity.md).

# Session 07: Hermes Shell Identity

**Session ID**: `phase41-session07-hermes-shell-identity` **Status**: Not Started **Estimated Tasks**: \~12-25 **Estimated Duration**: 2-4 hours

***

## Objective

Replace legacy Hermes limited-access route identity and passive telemetry copy with all-access local route language.

***

## Scope

### In Scope (MVP)

* Rename or replace `HermesReadOnlyPage`, `ReadOnlyLabel`, and page primitive exports with all-access names such as `HermesAllAccessPage` and `LocalAccessLabel`.
* Update `/agents/hermes` route metadata and imports.
* Update Hermes loading/setup states, header badges, tabs, status bar, live stats, memory, connections, roles, CLI cheatsheet, skills, activity, sessions, Mnemosyne data, and browser fallback copy.
* Update Hermes route, section, and aggregation tests.

### Out of Scope

* Mutation-specific controls and chat/admin copy owned by Session 08.

***

## Prerequisites

* [ ] Session 03 route mode and hook semantics are complete.

***

## Deliverables

1. Hermes local route shell and read panels using `live-local`, `All access`, and `Writes ready` language.
2. Primary component names that no longer encode limited local behavior.
3. Updated tests for route identity and section copy.

***

## Success Criteria

* [ ] `/agents/hermes` imports and renders all-access local identity.
* [ ] Tabs and sections no longer assert legacy limited local labels for live local mode.
* [ ] Tests use the new all-access names and labels.

***

## Folded Handoff Session Details

The following session-specific details were migrated from the former ongoing-projects handoff. They preserve the original objective, scope, outputs, dependencies, notes, and acceptance checks for this session.

#### Session 07: Hermes Shell Identity

**Objective**: Replace Hermes read-only route identity and passive telemetry copy with all-access local route language.

**Scope**:

* Rename or replace `src/components/hermes/hermes-read-only-page.tsx`, `HermesReadOnlyPage`, `ReadOnlyLabel`, and page primitive exports with primary all-access names such as `HermesAllAccessPage` and `LocalAccessLabel`.
* Update `src/routes/agents.hermes.tsx` route metadata and imports.
* Update Hermes loading/setup states, header badges, tab labels, lazy Mnemosyne loading, status bar, live stats, memory card, connections, roles, CLI cheatsheet, skills, activity, sessions, Mnemosyne data, and browser fallback copy.
* Update Hermes route, section, and route aggregation tests that assert read-only labels or route metadata.

**Outputs**:

* Hermes local route shell and read panels using `live-local`, `All access`, and `Writes ready` language.
* Primary component names that no longer encode read-only as the route identity.
* Updated tests for Hermes shell identity and section copy.

**Dependencies / Notes**:

* Depends on Session 03 so UI language reflects real hook state.
* Out of scope: mutation-specific controls and chat/admin copy, covered by Session 08.

**Acceptance Checks**:

* `/agents/hermes` no longer imports or renders the read-only route identity for local live mode.
* The tab list and sections no longer assert `Hermes read-only sections`, `Recent read-only sessions`, or read-only Mnemosyne fallback for live local mode.
* Tests use the new all-access names and labels.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-os-and-trend-finder.gitbook.io/ai-os-and-trend-finder-docs/.spec_system/prd/phase_41/session_07_hermes_shell_identity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.