[FEATURE] Browser History, Bookmarks & Tab Session Persistence

[Wombatfreak6]

Details

The browser currently holds all tab state in-memory only (BrowserService uses an Arc<RwLock<BrowserState>>), so every app restart loses all open tabs, navigation history, and bookmarks. The SQLite infrastructure already exists from Phase 5 (sqlx + AppDb in services/memory/db.rs) — this feature layers browser-specific persistence on top of it.

Note: PR #78 attempted this using rusqlite (bundled), which conflicts with the existing sqlx driver. PR #78 should be closed in favour of this issue.

Implementation Notes

• Add history, bookmarks, and tabs_session tables to migrations/001_initial.sql
• Expose IPC commands in src-tauri/src/commands/browser.rs: db_add_history_entry, db_get_history, db_add_bookmark, db_remove_bookmark, db_get_bookmarks, db_save_session, db_restore_session
• Create src/stores/dbStore.ts for history and bookmark actions using the existing AppDb pattern
• Add TypeScript models in src/types/db.ts, re-export from src/types/index.ts
• Debounce db_save_session in browserStore.ts on navigation/tab changes
• Call db_restore_session on app launch in App.tsx

Acceptance Criteria

• history table created and db_add_history_entry / db_get_history commands work
• bookmarks table created and add/remove/get commands work
• tabs_session table saves and restores open tabs across restarts
• App.tsx restores previous session on launch via db_restore_session
• dbStore.ts exposes history and bookmark actions to the frontend
• TypeScript types defined in src/types/db.ts and exported from index
• Uses existing sqlx AppDb — no new SQLite crate introduced
• Existing Vitest and Rust unit tests continue to pass

[Atharv094]

Hi! I'd love to work on this. I can build the persistence layer using the existing sqlx AppDb pattern—avoiding rusqlite—and expose the IPC commands in browser.rs.

Could you please assign this issue to me? Also, is this under the ECSoC program? If so, please add the "EcSoc26" label.

[Wombatfreak6]

@Atharv094 Great, can you share the plan of action. Yes, and the label has been added

[Atharv094]

@Wombatfreak6 are you the project admin of the CMTRL repo??. i am asking this question since it is mentioned that this repo is owned by Omnikon-Org but not mentioned that who is owner or project admin of this repo.

[Atharv094]

Plan of Action

1. Database Layer Updates (Rust/SQL)

• Migrations: Update migrations/001_initial.sql to define the schemas
for the new tables: history, bookmarks, and tabs_session.
• Database Queries: Implement the underlying database queries utilizing
the existing sqlx + AppDb infrastructure in services/memory/db.rs to
ensure no conflicting SQLite drivers (like rusqlite) are introduced.

2. Backend IPC Commands (Tauri/Rust)

• Expose Commands: Add the following IPC commands in src-
tauri/src/commands/browser.rs:
• History: db_add_history_entry, db_get_history
• Bookmarks: db_add_bookmark, db_remove_bookmark, db_get_bookmarks
• Session: db_save_session, db_restore_session
• Ensure these commands correctly interface with the AppDb state
provided by Tauri.

3. Frontend Types & State Management (TypeScript)

• Types: Define strict TypeScript interfaces for History, Bookmarks,
and Tab Sessions in src/types/db.ts and re-export them from
src/types/index.ts.
• Store Creation: Create a new src/stores/dbStore.ts to handle history
and bookmark actions, following the existing AppDb pattern to
communicate with the IPC commands.

4. Frontend Integration & Lifecycle (React/Zustand)

• Session Saving: Update browserStore.ts to listen for navigation or
tab changes and trigger a debounced call to db_save_session (preventing
excessive database writes).
• Session Restoration: Hook into the app's initialization phase in App.
tsx to call db_restore_session on launch, restoring the previously open
tabs to the browserStore.

5. Testing & Validation

• Verify the app builds correctly and that all existing Rust unit tests
and Vitest tests continue to pass.
• Manually verify the acceptance criteria: adding/removing bookmarks,
history tracking, and ensuring tabs persist after closing and reopening
the app.

this is my plan of action.please assign this issue to me so i can start working asap