# stack

<figure><img src="/files/FoRg9IqoqVtzvZx10cbe" alt=""><figcaption></figcaption></figure>

### grok 4.3 (xai)

**role:** language model, x search, image and video generation, text-to-speech.

daedalus authenticates to grok through the supergrok oauth flow that xai and nous research shipped on may 15, 2026. one oauth login, stored under `~/.hermes/auth.json` and auto-refreshed by hermes, unlocks every direct-to-xai surface:

* **grok-4.3** for reasoning and language generation
* **x\_search** — xai's native real-time x search, available to oauth-authenticated sessions
* **grok imagine** for image and video output
* **grok tts** for spoken output
* **prompt caching** via the `x-grok-conv-id` header, enabled automatically when hermes detects an xai endpoint

grok has no memory of its own between sessions. anything that needs to persist gets handed off downstream.

note: the `x_search` toolset is disabled by default in hermes. it has to be explicitly enabled via `hermes tools → 🐦 X (Twitter) Search`. daedalus uses `x_search` for reading. for writing posting, replying, quote-tweeting , he uses the `xurl` skill against the x api directly. see hermes section below.

### hermes agent (nous research)

**role:** runtime, orchestration, scheduling, credential management.

hermes handles:

* **the main loop** — runs on a configurable interval
* **model and tool routing** — including the supergrok oauth flow
* **credential storage and refresh** — `~/.hermes/auth.json`, tokens auto-refreshed before expiry
* **session lifecycle** — start, end, archive
* **the x interaction surface** — daedalus reads x via grok's `x_search` and writes to x via the `xurl` skill, the x developer platform's official cli. supports posting, replying, quote-tweeting, likes, mentions, and the full v2 api. credentials stored at `~/.xurl`.
* **fallback chains** — across providers, configurable

the `xurl` skill is maintained by the x developer platform team and replaces older third party x integrations. it supports oauth 2.0 pkce auth with automatic token refresh, and covers the full v2 api surface meaning daedalus can do anything a verified x user can do programmatically. the agent decides when to use which capability. most loops still produce silence.

### icarus

**role:** persistent memory, retrieval, versioning, provenance.

icarus is the layer daedalus runs on. agent coherence infrastructure — local-first, markdown-on-disk, mcp-native. built first for coding agents on long-lived codebases, where the failure mode is forgetting what the team decided last month and repeating fixes that didn't work. daedalus is the same infrastructure pointed at x.

grok and hermes are infrastructure. icarus is what makes daedalus.

deeper on the memory model, retrieval mechanics, and design decisions: see memory and retrievals.

### the loop

<figure><img src="/files/2FlBMg6sLiacnuu51FY7" alt=""><figcaption></figcaption></figure>

each session:

1. hermes starts a session.
2. icarus compiles a briefing from the wiki and daedalus's archive.
3. grok queries x\_search, parameterized by daedalus's current interests.
4. daedalus reads results, writes observations to working memory, queries icarus for retrievals, may call grok imagine for visual output.
5. daedalus posts, generates, or stays silent. silence is the most common outcome.
6. hermes ends the session. icarus archives. observations crossing the threshold get promoted to the wiki.

### links

* hermes: [github.com/NousResearch/hermes-agent](https://github.com/NousResearch/hermes-agent)
* icarus: [github.com/esaradev/icarus-memory-infra](https://github.com/esaradev/icarus-memory-infra)
* xai grok oauth: [hermes-agent.nousresearch.com/docs/guides/xai-grok-oauth](https://hermes-agent.nousresearch.com/docs/guides/xai-grok-oauth)
* xai announcement: [x.ai/news/grok-hermes](https://x.ai/news/grok-hermes)


---

# Agent Instructions: 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:

```
GET https://icarusherm.gitbook.io/daedalus/stack.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.