It's invite-only for now. Join the waitlist and we'll email you a signup link the moment a place opens up.
Six tabs, and four of them aren't called what they do. That table comes first, because every other instruction on this page depends on you finding the right tab.
The tab labels are deliberately in the app's own voice. That reads well and hides what they do, so here is the map. Hover any tab in the app and it tells you the same thing.
Tailing is the card that matters. If it names a file, the app is watching your log right now and everything else on this page is a detail. If it doesn't, nothing is being recorded and no amount of re-parsing will help — troubleshooting starts there for that reason.
Below it: Recent activity over the last 48 hours, Top event types, a Session timeline, and Parser coverage — how much of your log the app understood, which is the honest version of “is this working”. Sources and Discovered logs show which files it found.
Remote sync reports whether this machine is paired and sending. Paired and tailing are different things: a machine can be reading your log perfectly and sending none of it.
Star Citizen writes lines StarStats doesn't recognise — new patches invent them constantly. Those land in Review with a count on the tab. For each one you can submit it, attribute it to your handle, or dismiss it.
Submitting sends the shape of the line so it can become a supported event type. Dismissing drops it locally and stops the app asking again. Neither is urgent — an empty queue is not a goal, it's just tidier.
This is the only place in the app where you decide what leaves your machine line by line, which is why it's a queue and not a background job.
Game.log — where your log lives. Set automatically; change it only if you moved your install or run more than one.
Cloud sync — off by default, greyed out until the app is paired, and it holds your changes until you press Save. Covered as step 05 on the setup page.
Updates — whether to check on launch, and which channel to follow. You can switch channels whenever you like; the next check reads the new channel's manifest.
RSI session cookie — optional, and worth reading its own page before you paste anything. Without it, everything works except hangar data.
Unreadable log entries — off by default. Sends the names of log entry types the app couldn't read, never the lines themselves. It's how we spot a game update breaking tracking before you have to report it.
Appearance and Org platform connector live here too. Appearance follows you to other machines if cloud sync is on.
Re-parse local store runs the current classifier over lines the app has already stored. It's fast. It can only re-read what was kept.
Re-ingest rotated logs walks every rotated Game-*.log still on disk and feeds each line through the classifier again, from source. It takes minutes.
The distinction that matters: if an event type was never recognised in the first place, re-parsing can't recover it — those lines were never stored as events. Re-ingest goes back to the original files and can. So after an update that adds support for something, re-ingest is the one that fills the gap.
Rotated logs only survive as long as your disk keeps them. If the files are gone, so is the history — no button brings back a log Star Citizen has already overwritten.
The desktop app reads and sends. Everything you actually look at lives on the site — your dashboard covers the tiles and the two controls that drive them, and sharing covers who else gets to see them.