Getting started with Devlog
Start with your game’s history. Connect reporting whenever you’re ready.
1. Add your game
Open your workspace and choose Add game. A Steam store link can fill in the name and capsule. You can also start without a store page.
2. Review the first discoveries
Initial research looks for public milestones and coverage. Check each source, date and game match. Use Dates still to confirm for uncertain events, and Ask assistant on a card to explain a correction.
3. Connect reporting when you need it
Open Steam reporting from the workspace menu. Follow the Financial API Group instructions there, or import a CSV. Steam sign-in alone would not grant access to these reports.
4. Load your history once
Choose the reporting date range you need. Older completed reports are cached, so repeated loads can reuse them. The growth chart distinguishes daily net additions from outstanding wishlists.
Let Devlog check while you are away
When monitoring beta access is enabled, select games and check frequency from Account. The first check covers the last seven days; later checks overlap the previous check to catch delayed results. Enable a weekly digest or discovery alerts if you want emails. Monitoring currently checks YouTube and Steam; scheduled press and social searches are not connected yet.
What the assistant remembers
Conversations are saved per game. Each turn includes recent messages, game details and relevant card summaries; it can search other saved cards with its tools. Discussing a specific card attaches that card directly. It does not receive every historical message or your financial API key.
What to expect
Discovery is an attempt, not a complete archive. Follower and review history begins with saved snapshots. Financial and wishlist reporting retain their Steam date conventions; a nearby event is context, not proof of attribution.