Export uploads
Here’s where things stand.
- 01What changed
Export uploads now retry when they fail.
- 02Tests
All five tests passed.
- 03Still to do
The live site still needs checking.
Catch up with your coding agents
Pick up where you left off without rereading every chat. Draken sums up what changed and helps you work out what to do next.
Reads your agent history. Doesn’t edit your code.
“The tests passed.
I’d check the live site next.”
01 / Here’s an example
Draken reads the sessions you choose and sums up the work. You can follow each reference back to the original message.
Here’s where things stand.
Export uploads now retry when they fail.
All five tests passed.
The live site still needs checking.
02 / Find your place again
Pick the sessions you want Draken to read. It won’t read Codex or Claude histories unless you turn those sources on.
What changed? Why did the agent do that? What’s left? Ask in text, or talk to Draken with ChatGPT voice.
Save your decisions and what to do next. Mark the sync reviewed when you’re ready. Simply reading or listening won’t mark it done.
03 / Prepare ahead
On by default for new installations.
Your original logs stay intact.
New installations automatically index enabled history, summarize new work and prepare a briefing while the server runs. Turn this off with Automatically prepare conversations in Settings if you prefer manual preparation. Compaction creates cached summaries; it does not edit or delete original agent logs. Matching summaries and ready briefings are reused, rather than starting over every time.
Settings’ Preparation usage dashboard shows estimated USD cost, completed batches and model requests. Choose a 6-hour, 1-day, 7-day or 14-day window and hourly, 6-hour or daily buckets. Labelled cost/batch axes and bucket details make values readable. Manual preparation, automatic work, retries and failures stay counted.
Missing prices stay unavailable or partial; older timing is approximate. These are not invoices, total spending or account quota. Chat, voice, standalone post-conversation recaps and local machine/network costs are excluded.
Automatic mode is on by default for new installations and uses your configured summary and briefing models, including quota or API billing, within the saved invocation limit. Existing installations keep their previous behavior, including off or no saved preference. Provider failures pause for an explicit retry. Older local-index-only permission does not silently authorize model usage. No automatic microphone, call, saved decision or review. Opening the explanation or cost dashboard only reads metadata.
04 / What it does—and doesn’t
You still choose what to do,
what to trust, and what to review.
It doesn’t run project commands, edit your code, start coding agents or make Git changes.
Links in the summary lead back to your agent logs. If a file is missing or changed, Draken tells you. It doesn’t keep a hidden copy of the original text.
Reading and searching logs happen locally. For summaries and text replies, pi sends content to the model provider you use. If you use voice, your audio and some history go to OpenAI.
Draken won’t treat an AI suggestion as your decision, or mark work reviewed for you.
Release notes
Fewer recap interruptions.
Clearer preparation status.
Recap prose can now wrap at existing spaces without dropping words or qualifications. A line just over the width limit no longer needs a model correction if the result still fits five lines and 600 characters. Unbreakable tokens and other invalid output remain checked; retries are still bounded.
Preparation metrics retain content-free validation reasons and line lengths, not rejected model text. If both responses fail validation, the error explains the failing rule. Older rejected responses cannot be reconstructed after the fact.
Home distinguishes entries not yet in a sync from entries already held in an unfinished batch. A stopped batch shows its entry count and stage. Zero unassigned entries does not mean preparation succeeded. The same automatic settings, source permissions, model limits and explicit failure retries remain.
Chat defaults to one paragraph or up to three bullets, usually 60–100 words plus citations. Ask for a detailed breakdown when you want more. The same evidence and later-report checks remain; the length target is guidance to the model, not a hard cutoff or an extra model request. Opening briefings keep their own format.
No new tables, columns or dependencies from 0.5.0. The default is stored only when initializing an empty database. Conversations, notes, review state, summaries and compatible search vectors are retained. Back up logs and Draken data, finish active work, stop the server, upgrade and restart.
Version 0.5.1 / Available on npm
Install Draken with npm, then start it from your terminal.
npm install -g draken
drakenRead the setup guideUpgrading from 0.1.6 or earlier? Back up your agent logs and Draken data first. This version replaces the old task dashboard. Read what changed.
A few practical questions
No. You can read summaries, ask questions, check the original messages and save notes without a microphone. Voice is optional and has its own setup.
No. It can only use logs it supports and sessions you’ve included. Summaries leave details out, and search can miss things. If something matters, check the original message.
This page is just a demo. In Draken, opening Settings or checking setup doesn’t read your chat logs, start a summary or turn on your microphone. Automatic preparation is enabled by default for new installations and can be turned off in Settings. When enabled, it can index history and use your configured summary and briefing models while the server runs, independently of whether a page is open.
Your original agent logs and Draken’s saved data. Old summaries still need the original logs when you open their sources. Back up both before an upgrade. Don’t try to undo a database change by running an older version of Draken.