> 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/archive/phases/phase_23/session_01_claude_code_agent_route.md).

# Session 01: Claude Code Agent Route

**Session ID**: `phase23-session01-claude-code-agent-route` **Status**: Not Started **Estimated Tasks**: \~12-18 **Estimated Duration**: 2-3 hours

***

## Objective

Add the v2.3 Claude Code agent route by reusing the aios Mission Control component with `agent="claude-code"` and route/sidebar wiring, after Hermes Mission Control exists.

***

## Source Reference Detail

* v2.3 source route: [V23/src/routes/agents.claude-code.tsx:1](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/routes/agents.claude-code.tsx:1) through `:153`.
* aios target route is absent: `AIOS/src/routes/agents.claude-code.tsx`.
* aios dependency: `AIOS/src/components/hermes-mission-control.tsx`, delivered by Hermes Phase 19.
* sidebar nav target near Hermes: [AIOS/src/components/app-sidebar.tsx:108](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/aios/src/components/app-sidebar.tsx:108).
* v2.3 home placement wants Mission Control placement at: [V23/src/routes/index.tsx:16251](https://github.com/moshehbenavraham/ai-os/blob/main/home/aiwithapex/projects/claudeos/claude-os-v2.3/src/routes/index.tsx:16251).

***

## Scope

### In Scope (MVP)

* Add `AIOS/src/routes/agents.claude-code.tsx`.
* Reuse the aios Mission Control component rather than copying a parallel implementation.
* Pass `agent="claude-code"` or the equivalent local prop/API established by the Hermes Phase 19 implementation.
* Apply the v2.3 blue skin in aios style without importing unrelated Hermes monolith code.
* Add a sidebar nav entry next to Hermes.
* Add route metadata/tests/smoke coverage consistent with existing local-agent routes.
* Add home placement only if the current aios home IA has an established Mission Control slot; otherwise document deferral in implementation notes.

### Out of Scope

* Implementing Hermes Mission Control; Phase 19 owns it.
* Adding unsafe writes or spawn behavior outside the existing Mission Control safety gates.
* Rebranding AI OS around Claude Code.

***

## Prerequisites

* [ ] Hermes Phase 19 Session 01 complete and `AIOS/src/components/hermes-mission-control.tsx` available.
* [ ] Confirm Mission Control props/API for selecting an agent.
* [ ] Confirm current sidebar route conventions and generated route-tree flow.

***

## Deliverables

1. Claude Code route file.
2. Sidebar navigation entry.
3. Route tests or smoke coverage.
4. Implementation note confirming Mission Control safety reuse.

***

## Success Criteria

* [ ] `/agents/claude-code` renders through the shared Mission Control surface.
* [ ] The route uses the Claude Code agent configuration and blue skin.
* [ ] Sidebar navigation reaches the route.
* [ ] No write, spawn, or polling path bypasses Mission Control safety.
* [ ] Route tree generation is handled by the normal build/dev tooling, not by hand-editing `src/routeTree.gen.ts`.


---

# 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/archive/phases/phase_23/session_01_claude_code_agent_route.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.