Syncing with Linear
What syncs between Areca and Linear, in which direction, and how often.
Areca keeps a synced copy of your Linear issues so the app stays fast and always has something to show. Here's exactly what moves between the two, and when.
What Areca reads from Linear
Areca pulls in the issues assigned to you, along with the pieces it needs to display and organize them — your teams' statuses, labels, and cycles. That's the read side, and it's what makes your list and calendar reflect reality.
What Areca writes back
The write side is narrow and always driven by you. When you edit an issue in Areca — its status, priority, labels, or due date — that single change is saved back to Linear. Nothing is written without an action from you.
Scheduling never leaves Areca
Your calendar is one-way. The blocks you place, move, and resize live in Areca and are never sent to Linear. Only issue-field edits sync back.
How often it syncs
Areca refreshes on its own, and it pays attention to whether you're around:
- While you're using it, your issues refresh every couple of minutes.
- When you step away, it eases off to about every half hour to avoid needless work.
- The moment you come back, it syncs right away so you're looking at current data.
- Statuses, labels, and cycles — which change far less often — refresh a few times a day.
New data arrives on its own; you don't need to reload the page to see it.
Syncing now
If you just changed something in Linear and want it reflected immediately, press the Sync issues button — in the logo menu, or on the collapsed sidebar rail. Areca fetches right away and tells you how many issues came through.
If the connection lapses
If your Linear authorization expires or is revoked, Areca can no longer sync and will pause rather than keep failing quietly. Sign in with Linear again to restore the connection and pick up where you left off.
Next
To manage what's stored and how to disconnect, see Your data & account.