Add embedded replica and sync mode
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 35
- Forks
- 4
- Avg merge
- 17h 19m
- Merged PRs (30d)
- 8
Description
Context
Future work from docs/superpowers/specs/2026-05-24-local-libsql-migration-design.md.
The local libsql migration and Turso cloud configuration model are prerequisites. This issue should build on the right-db driver boundary instead of introducing driver-specific APIs in domain crates.
Scope
- Add an embedded replica mode using local reads and remote-backed sync semantics.
- Define explicit sync triggers and startup behavior.
- Preserve local-only mode as the default for existing agents.
- Document consistency expectations, including read-your-writes behavior if enabled.
Acceptance Criteria
- Existing agents keep working without cloud configuration.
- Replica mode is configured through the approved storage config model.
- Sync errors surface through structured errors/logs rather than being swallowed.
- Tests cover local-only mode and replica-mode connection construction.
Out Of Scope
- Backup/restore UX.
- Doctor sync health thresholds.
- Migration tooling from local-only data to cloud primary.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read docs/superpowers/specs/2026-05-24-local-libsql-migration-design.md first, then trace the right-db driver boundary and approved storage configuration model. Check how local-only connections are constructed and identify the existing test entry points. Done means local-only behavior remains the default, replica construction and sync errors are covered, and consistency expectations are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sqlite
- Domain
- databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100