o7 Debrief
Commander Mission Debrief
A local-first app that turns your Elite Dangerous journal into a self-contained mission debrief. Every figure traces back to a real journal field. Nothing is estimated, inferred or padded.
Windows 10 and 11 and Linux as a Flatpak · runs quietly from the system tray
What it does
Live background watcher
Follows the active journal in the background and generates a debrief automatically when you shut the game down.
Debrief any time
Cold one-shot mode reports your last session or your whole history to date, even if the app was not running while you played.
Real numbers only
Every credit, jump and scan maps to a real entry in your journal, so the figures are verifiable and never guessed, inferred or padded. A figure the journal never stated is never printed as zero: where the slot must hold something it says there was no reading; where nothing has to occupy it the figure is simply left out.
What you actually made
The credit change is the difference between your balance at each end of the session, so a rebuy, an outfitting bill or a hold full of tritium counts against you exactly as it did in game. A session that ended poorer says so.
What the priced events came to
When the journal states only one balance it can state no change; saying so and stopping there tells you nothing. Beside the balance sits the total of every event the journal does price, income less outgoings, in a card of its own that says plainly it is not the balance change.
A balance that says its age
The journal states your balance when you log in and never again, so on a long session that figure is what you had when you sat down. The report prints the moment it was read beneath it, rather than letting a reading hours old pass for a current one.
Outfitting and the shipyard
Modules and ships bought and sold, counted and priced on each side rather than netted off, so a refit reads as the two things it was. Ship transfers get their own line, since a transfer buys nothing and still costs. Each one is a row in the log naming the item and the price.
Distance travelled
The light years your ship covered, read from the distance each jump states. Your fleet carrier is measured too, worked out from where it arrived, since a carrier jump never records how far it came.
Self-contained report
A session debrief is one self-contained file you can open in any browser or keep, plus a text version ready to paste onto Discord or Reddit.
Dated where it matters
A log covering several days heads each day with its date, so a history report reading 15:15 above 11:48 is plainly two days rather than a broken sort. A single session shows no dates and keeps its narrow time column. Times are the journal's own UTC, shown unconverted and labelled.
A history that stays readable
Years of play will not fit in one page, so the history debrief is a small set of pages: an index, a page per month and one shared stylesheet, opening from your own filesystem with no server and no scripts. It is rebuilt every time you quit and only the pages that actually changed are rewritten.
Honest rank reporting
Tier-ups show at once and fractional rank percentages settle at the next launch, because the journal only snapshots progress at startup.
Your ship, tracked
The header names your current ship and its type. Every swap or purchase is also logged as a session event, from the ship you left to the one you boarded.
Deaths that stand alone
A death row names who died, the vehicle actually lost at that moment (an SRV, not the ship it launched from), the killer with their ship and squadron read from the targeting scan, then what the rebuy cost.
Every row says what you did
An engineering roll names the blueprint, the grade, the module and the engineer who applied it, so an evening of two hundred rolls reads as the work it was rather than two hundred identical lines. Applying an experimental effect is its own row and its own figure, because the journal reports it as a roll and it is not one. It reads in English too: the journal calls a module int_sensors_size5_class2 and the report calls it a 5D Sensors. Where the journal did not record something a row needs, the row says less rather than guessing.
Material trading
Exchanges at the raw, manufactured and encoded traders are logged with both sides named, then counted in the Trade section. No credit figure is shown against them, because they cost no credits: you pay in materials.
Check for updates
Shortly after launch and once a day, the app asks GitHub anonymously whether a newer release exists; a Check for updates button on the home screen and a tray entry both do the same on demand. You choose Download, Skip this version or Later; it never downloads or runs anything without you choosing it.
Local-first
No cloud, no account, no telemetry. Your journal never leaves your machine and the app needs no administrator rights to install. Nothing listens either: the app opens no port and accepts no connection, so the only network call it ever makes is the update check going out.
Three ways in
The third is simply launching o7 Debrief again. It does not start a second copy; the one already running opens its home screen, so the Start menu shortcut reaches the app rather than appearing to do nothing.
Example output
A debrief covering a commander's whole journal history. Open the full example report →
A log covering several days heads each day with its date. A single session shows none and keeps the narrow time column.
Every month is one click away and every tab counts the whole history rather than the page.
Common questions
What is o7 Debrief?
o7 Debrief is a free, local-first Windows app that turns your Elite Dangerous Player Journal into a self-contained Commander Mission Debrief you can read in any browser or share as text.
Is o7 Debrief free and open source?
Yes. o7 Debrief is free and released under the GNU Lesser General Public Licence v3.0, with the full source on GitHub.
Does o7 Debrief upload my journal or data anywhere?
No. It is local-first with no cloud, no account and no telemetry. Your Player Journal never leaves your machine and the app needs no administrator rights to install.
What does an Elite Dangerous debrief track?
Credits, jumps, distance travelled by your ship and your fleet carrier, scans across exploration, mining, trading, bounty hunting and exobiology, outfitting and shipyard trade (modules and ships bought, sold and transferred, each side priced separately), engineering split between grade rolls and experimental effects, plus missions and Operations (naming each mission and the Merc Coins an Operation pays, kept separate from your credits), deaths (who died, in what, at whose hands and what the rebuy cost) and Commander rank progress, with every figure traced to a real journal entry. Where the journal states nothing, the report says so rather than printing a zero you would read as a real figure.
Do I need to keep o7 Debrief running while I play?
No. The background watcher can generate a debrief automatically when you close the game; one-shot mode can also report your last session or your whole history to date after the fact.
Does o7 Debrief record ship changes?
Yes. Swapping ship or buying a new one is logged as a session event naming the ship you moved from and the one you boarded; the header also names your current ship and its type.
Does o7 Debrief check for updates?
Yes. Shortly after launch and once a day while running, the app asks GitHub anonymously whether a newer published release exists; the home screen and the tray menu both carry a Check for updates button that does the same on demand. If one is found you choose Download, Skip this version or Later; a skipped version never prompts again. This anonymous ask is the only network call the app makes and nothing is ever downloaded or installed without you choosing it.
Which Windows versions does o7 Debrief support?
Windows 10 and Windows 11. It runs quietly from the system tray and reads the Player Journal that Elite Dangerous writes on your PC.
Does o7 Debrief run on Linux?
Yes, with one honest caveat. Every release publishes a Flatpak. On Ubuntu with Elite Dangerous under Proton it has been left watching through a real session: it read the journal from inside the prefix, produced the debrief when the game closed and opened that report in a browser on the host. The parts that matter most are therefore proven rather than intended. Starting it at sign-in did not work in the Flatpak before this release, because the entry was written inside the sandbox's own configuration rather than the session's; that is fixed and confirmed on a real reboot, so tick the setting off and on again after upgrading. Note that a Flatpak install can never arrive with that setting already on, so switching it on is one trip into Settings after installing. What has not been exercised is narrower still: launching it again to summon the window inside the sandbox and the case where Steam itself is installed as a Flatpak. The repository records exactly what has and has not been verified. Windows is the platform every release is built and tested on.
How do I install or upgrade o7 Debrief?
Run the setup program. It installs for your user account only, so it never asks for administrator rights. It names the phase it is in and shows its progress as it works. Upgrading over a copy that is still running in the tray is handled for you: setup offers to close it and carry on. The same program repairs and uninstalls.
Download o7Debrief
Download the newest release with one click. Free and LGPL-3.0, local-first software with no cloud, no account and no telemetry.
Version 2.6.0Windows
Windows 10 or 11, 64-bit
Download for WindowsRun the setup: it installs per-user, so no administrator rights are needed. It shows its progress as it works and offers to close a running copy when you upgrade.
Linux
Any distribution with Flatpak
Download for LinuxInstall with flatpak install o7debrief.flatpak. On Ubuntu it has watched a real session with the game under Proton and opened the finished debrief in a browser on the host. Starting it at sign-in was broken in the Flatpak before this release and is fixed here; switch it on in Settings after installing, which a Flatpak cannot do for you.
What's new in this release · All releases · Source on GitHub