You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e70d1a6
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+15-9Lines changed: 15 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,14 +148,25 @@ If you use this code or repository in your research, please cite:
148
148
}
149
149
```
150
150
151
-
## Optional: Trajectory metadata and logging
151
+
## RLMs in the Wild
152
+
There are many amazing demos and production-ready use cases of RLMs. We provide a list of notable examples that explicitly use RLMs as a central piece of their design.
*[viplismism/rlm-cli: **CLI for Recursive Language Models**](https://github.com/viplismism/rlm-cli) <ahref="https://github.com/viplismism/rlm-cli/stargazers"><imgsrc="https://badgen.net/github/stars/viplismism/rlm-cli?icon=github&label=Stars"height="14"alt="GitHub stars"></a>
157
+
*[alphaXiv Official Blog. **Reinforcing Recursive Language Models**](https://www.alphaxiv.org/blog/reinforcement-learning-for-rlms#training)
158
+
*[Daytona. **Building Deep Recursive Language Models**](https://www.daytona.io/docs/en/guides/rlm/recursive-language-models/)
159
+
*[Symbolica. **SotA ARC-AGI-2 Results with REPL Agents**](https://www.symbolica.ai/blog/arcgentica)
160
+
*[Google Cloud Community Articles. **RLMs in ADK**](https://discuss.google.dev/t/recursive-language-models-in-adk/)
161
+
*[Prime Intellect Blog. **Recursive Language Models: *the* paradigm of 2026**](https://www.primeintellect.ai/blog/rlm)
162
+
163
+
## Optional: Trajectory metadata, logging, and debugging
152
164
`RLMChatCompletion` has an optional `metadata` field (default `None`) that holds the full trajectory (run config + all iterations and sub-calls) so you can reconstruct the run. Pass an `RLMLogger` to capture it:
153
165
154
166
-**In-memory only** (trajectory on `completion.metadata`): `logger=RLMLogger()` (no `log_dir`).
155
167
-**Also save to disk** (JSONL for the visualizer): `logger=RLMLogger(log_dir="./logs")`.
We provide a simple visualizer to inspect code, sub-LM, and root-LM calls. Use `RLMLogger(log_dir="./logs")` so each completion writes a `.jsonl` file:
169
+
**Visualizing logs.** We also provide a simple visualizer to inspect code, sub-LM, and root-LM calls. Use `RLMLogger(log_dir="./logs")` so each completion writes a `.jsonl` file:
159
170
```python
160
171
from rlm.logger import RLMLogger
161
172
from rlm importRLM
@@ -168,9 +179,4 @@ To run the visualizer locally, we use Node.js and shadcn/ui:
168
179
```
169
180
cd visualizer/
170
181
npm run dev # default localhost:3001
171
-
```
172
-
173
-
You'll have the option to select saved `.jsonl` files
0 commit comments