Sign-in and your data
How signing in works, what it unlocks, what stays on your PC, and what Griddler Social keeps.
Signing in
Your browser opens
Settings→Account→Sign in opens River Logic's sign-in page in your normal browser. You sign in there, with your River Logic account, the same way as for other company apps.
Griddler gets a short-lived pass
The browser hands the result back to Griddler on your own machine. Griddler keeps two things:
- an access token that lasts a few minutes, in memory only, and
- a refresh token, encrypted with your OS account's key, in
~/.griddler.
Griddler swaps the refresh token for a new access token on its own, so you stay signed in for weeks.
Azure DevOps comes along
Right after, Griddler asks Microsoft for an Azure DevOps sign-in the same way, usually without a second click. That one is used for work items, the knowledge archive and posting to tickets, always as you.
Every request to Griddler Social carries the access token. Social checks it each time, and lets in verified River Logic addresses only. There's no separate password, and nothing to join.
What signing in unlocks
Everything that only involves you works signed out: the grid, sessions, resume, search, hooks, copy tools, web cells, the Doctor and the solo game. Signing in adds everything that involves other people or the team server.
| Signed out | Signed in adds |
|---|---|
| Panes, tabs, presets, resume, search | Mail, the Tavern and who's online |
| Attention, notifications, the Doctor | The Guild Hall board, quests and campaigns |
The grid_* and browser_* tools in every pane | The team's tools in every pane: mail, the board, directives |
| Copy, files, web cells, themes | Directives, knowledge, Today, tasks and worries |
| The game, on this PC only | The game synced across your PCs, raids, co-op, Peek |
| Griddler Agents |
What works signed in or not has the full list, feature by feature.
Being offline never signs you out. Team panels say they can't reach the service until the network is back.
Where your data lives
Stays on your PC
- Your sessions. The terminal output of your local panes never leaves your PC. Claude Code and Codex keep their transcripts in their own folders, as they always do.
- Your settings and layout:
~/.griddler/config.json, your tabs, presets and Auth profiles. - Your sign-ins: the Griddler and Azure DevOps refresh tokens, encrypted with your OS account's key.
- Logs: a rolling log in
~/.griddler/logs, kept 30 days. - Your knowledge workspace, the checkout of the team's archive, and your standup drafts.
Goes to Griddler Social
| What | When |
|---|---|
| Mail, Tavern chat and reactions, pictures you post | When you send them |
| The Guild Hall board, quests, worries and tasks you file | When you post them |
| Directives and the knowledge index | When you save them. Knowledge is an index of who knows what; the documents stay in the archive. |
| Your game character and portrait | Synced every few minutes while you play |
| Presence | While Griddler is open and you're signed in |
| A health beat | At start, hourly, after a Doctor run, and at quit: version, OS, which checks pass. No file contents. |
| Usage counts | Batched every few minutes: which features were used, never what you typed |
| A Griddler Trace | Only when you submit one. It's scrubbed first: settings as shapes, not values; no message bodies. |
| Agent registrations and their beats | For your Griddler Agents: state, folders and titles, and the last few lines each session said |
What Social never keeps
- The terminal stream of a shared agent session. The relay passes it along and keeps no scrollback or keystrokes, only who opened which session, when, and whether they watched or drove.
- Your Claude Code or Codex sign-ins.
- Meeting transcripts. Today reads them live and keeps a note of who looked at what, not the text.
- Azure DevOps work items. Those are read live each time.
Who can see what
- Mail is between the people on it. Admins can see who wrote to whom, and opening a message's content is recorded.
- The Tavern, the Guild Hall board and co-op mission briefs are visible to everyone signed in at River Logic.
- A Griddler Agent is Private until you share it. See Who can see and drive your agent.
- Admins see health beats, usage counts and submitted Traces in the admin portal.