Recall relevan di riwayat yang panjang
Temukan percakapan yang tepat lebih cepat dengan pemeringkatan lokal yang disetel untuk riwayat chat, bukan pencarian halaman yang umum.
Chrome Extension
Search ChatGPT History 10x Faster
Search years of ChatGPT history with local-first indexing, faster recall, and direct jumps to the exact message you need.
10x Local Search · Private by Default · Auto-Locate Jump
Product Note
Conversation content stays on your computer. Search, sync status, and jump hints stay inside the extension runtime.
Capability Anchor
Search stays local, sync stays visible, and jump results land near the exact message instead of only the right conversation.
01
Local-first search that feels instant
Build a local index on your computer and return relevant results without waiting on a remote search pipeline.
02
Jump straight to the matched message
Search results carry jump hints so Smart Search can auto-scroll near the exact answer instead of dropping you at the top of a long thread.
03
Keep sync progress visible
Stage-aware status shows discovering, fetching, indexing, and persisting so sync does not feel like a black box.
Search Results You Can Trust
Preview the core outcomes before rollout: relevant recall, message-level jump, and sync visibility that users can actually see.
Lompatan tingkat pesan, bukan hanya tingkat utas
Hasil yang cocok membawa konteks yang cukup untuk mendarat dekat balasan tepat yang ingin Anda temukan kembali.
Visibilitas sinkronisasi dari popup sampai halaman
Pengguna dapat melihat tahap sinkronisasi dan tahu apakah riwayat baru sudah diindeks sebelum mencari lagi.
Free & Pro
Start free with your latest 50 conversations indexed locally. Upgrade to Pro to remove the cap and search your full local history.
✓
10x History Search
Search ChatGPT history faster than the default in-page search flow.
✓
Message-Level Jump
Open the matched conversation and auto-scroll near the exact answer you need.
✓
Incremental Sync
Index only changed conversations instead of rebuilding everything every time.
✓
Visible Sync Stages
Popup status exposes discovering, fetching, indexing, and persisting stages.
Free
Latest 50
Everything in Smart Search, capped to your latest 50 conversations.
✓
Latest 50 conversations
Search the latest 50 conversations stored in your local index.
Pro($1.99)
Full history
Everything in Free, plus unlimited indexed conversations across your full local history.
✓
Unlimited indexed conversations
Search your full local ChatGPT history instead of stopping at the latest 50 conversations.
From History to Answer in 3 Steps
Open ChatGPT, run sync, then search and auto-locate directly to the target message.
01
Open chatgpt.com
Keep a ChatGPT tab active so the extension can read your local conversation timeline.
02
Run Sync and Build Index
Sync updates only changed conversations and reports clear stage-aware progress.
03
Search and Auto-Locate
Query over indexed recall, then auto-scroll to the matched message anchor with stable hints.
Frequently Asked Questions
Quick answers to common questions
Why is Smart Search not injected on chatgpt.com? ▼
Common causes and checks:
- Confirm the extension is enabled in chrome://extensions/
- Reload the ChatGPT tab after updating the extension build
- Check DevTools console for
smartsearch.content_loader_error - Verify host permissions include
https://chatgpt.com/*
Why does sync stay at 0/0 (discovering)? ▼
This usually means session discovery has not reached fetch/index stages yet.
- Keep an authenticated ChatGPT tab open
- Run sync again from popup and observe stage transitions
- If failures occur, wait for retry queue backoff and retry execution
Why do search results look stale after sync? ▼
Smart Search now performs incremental writes, but stale data can still appear if sync is interrupted.
- Run Rebuild Index once from popup
- Wait until status becomes completed/partial
- Retry query after sync progress reaches indexing/persisting stages
Does Smart Search upload conversation content? ▼
Conversation indexing and ranking run locally on your computer.
Current boundary:
- Conversation data for search stays local and is not uploaded by Smart Search
- Worker endpoints handle sign-in, session refresh, and billing only
- Worker
/api/auth/sessionsupports bearer token and session cookie - Popup login and ChatGPT site session are separate concerns
How should I verify production readiness? ▼
Recommended release checks:
- Run extension typecheck/test/build
- Run core engine tests
- Run browser smoke for popup/options load
- Run manual Chrome checklist for sync/search/jump
What if the above does not solve my problem? ▼
Collect build hash, extension logs, and failing route details, then open a feedback issue for maintainers to reproduce.
Engineering Notes
Implementation milestones stay visible, but they no longer lead the homepage narrative.
2026-02-18
Stateful build_or_update_index Landed
Index updates now merge changed conversations with existing state instead of full rebuilds.
2026-03-04
Browser Extension Smoke Added
Build now includes a reproducible Playwright-based smoke for loading popup/options in a real browser context.
2026-03-03
Sync Retry Queue Closed Loop
Failed conversations enter retry jobs with backoff and cleanup after successful replay.