Show HN: Tabverse – a free, open-source, with self-hostable server Workona clone
Hi, I want to share with you my chrome extension: Tabverse, as it is now passed the reveiw of Chrome Web Store and live at: https://chromewebstore.google.com/detail/tabverse/lffblcippn... Tabverse is a local first workona like chrome extension for managing tabs, with its source open at https://www.github.com/liyu1981/tabverse . In essential it has the core functions workona has, but can operate totally locally, which means it will not need an account nor subscription. The only limit is your loca
Read original sourceSource record
Recorded metrics
points · 1 votes
2026-10-26 18:00:30.153Z
cumulative since publication
Research analysis
Project record
Source account: Hi, I want to share with you my chrome extension: Tabverse, as it is now passed the reveiw of Chrome Web Store and live at: https://chromewebstore.google.com/detail/tabverse/lffblcippn... Tabverse is a local first workona like chrome extension for managing tabs, with its source open at https://www.github.com/liyu1981/tabverse . In essential it has the core functions workona has, but can operate totally locally, which means it will not need an account nor subscription. The only limit is your loca
Observed adoption & comparisons
Source votes: 1 votes (Oct 26, 2026 UTC; cumulative since publication); previous same-scope observation: 1 (Oct 26, 2026 UTC). These observations do not establish demand growth. Recent records to compare: “Show HN: GitHub-like reply with "R" for Basecamp and Slack” (Show HN, Nov 5, 2026); “Show HN: calsdk, one TypeScript API for Google Calendar, Outlook and iCloud” (Show HN, Nov 5, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.