Journal
Journal is a read-only record of every run in Erebros, at /journal, and what it actually asked a model: the exact calls, what was sent and what came back, ok, failed or running.
What it does
Section titled “What it does”Every app that calls a model writes a run here, so Journal answers “what actually happened” instead of you guessing from an app’s own log. Runs are filterable, by app, or trouble first, so a failing course build or a broken diagram round is a couple of clicks away rather than a scroll through everything.
What’s recorded
Section titled “What’s recorded”- The exact model calls a run made, in order: which model, what was sent, what came back.
- Status per call and per run: ok, failed, running.
- Excerpts of long prompts and answers, kept short enough to read, not the whole payload.
What’s stripped
Section titled “What’s stripped”Keys and tokens are removed before anything is written to disk, so a Journal entry is safe to look at, screenshot or hand to someone else without leaking a credential.
Rebuild the deck
Section titled “Rebuild the deck”From a course run, Rebuild the deck reassembles the course’s slides for free: the text, visuals and narration already generated are reused rather than regenerated, so a broken assembly step doesn’t cost another model call to fix.
Setup and dependencies
Section titled “Setup and dependencies”None. Journal only reads what other apps already wrote.
Where output goes
Section titled “Where output goes”Journal displays data; it produces no files of its own.
- Filter to trouble first when chasing a failed run, it skips the long list of runs that finished fine.
- Journal is the fastest way to see whether a slow course build is actually stuck or just working through a long queue of scenes.