# Local-first project management: prepare for work anywhere

Understand what local-first means in vikan, how to prepare for offline work, and what to check when your connection returns.

Canonical URL: https://blog.vikan.dev/posts/local-first-project-management/
Author: vikan team
Published: 2026-09-22
Language: en

Local-first project management keeps a working copy of relevant data on your device. In vikan, that local copy supports access to previously downloaded workspace data and descriptions when your connection is unavailable.

The practical question is what your device has already received. A workspace you have never opened, or a description you have never downloaded, is not made available simply by going offline.

## Prepare before you disconnect

Use the browser and device you intend to work on, then follow this short checklist while you have a connection:

1. Sign in and open the workspace you need.
2. Allow the workspace to load and pending changes to sync.
3. Open the issue descriptions and project documents you expect to read or edit.
4. Check that the important context is visible before leaving the connection behind.

Descriptions download and cache when you open them. That makes a quick review of tomorrow's work a useful preparation step before a journey or a day with unreliable connectivity.

## Know what offline access covers

The app can reopen with its cached application shell and previously downloaded data. Description edits preserve a local draft before attempting a network save. Reconnecting lets the app refresh its workspace snapshot and continue pending work.

File attachments have separate constraints. vikan does not provide an offline file-upload queue, so plan new uploads for a connected session. A cached description also should not be treated as a guarantee that every linked file is available offline.

Keep the working browser session available. Explicit sign-out clears the app's device data, including unsent work. Sync pending changes before signing out or changing devices. One browser window can edit at a time; other windows are read-only.

## Review changes when you reconnect

Local persistence and server confirmation are different steps. After reconnecting, allow synchronization to finish and review the current task state before handing work to someone else.

Other people may have changed the same description while you were offline. If a description conflicts, vikan preserves both versions for copying, exporting, or an explicit merge. It does not promise automatic character-by-character merging. Read both versions and keep the information the task still needs.

## Remember what connected assistants can see

MCP clients work with synced data in the workspace you authorized. They cannot see browser edits that have not synced. If you want an assistant to summarize a description you just changed, wait for that change to reach the shared workspace first.

Local-first work benefits from a simple habit: prepare the context, keep pending work on the device, then confirm the shared state when the connection returns. Pair that habit with [a short weekly planning routine](/posts/a-calmer-weekly-planning-workflow/) to make the next working session easier to begin.