Opportunities › Chat history organization for AI code assistants › Proposed app
Thread Shelf
Keep finished AI coding chats in view, dimmed not hidden, per project
- Score
- 35
- confidence 44
- Evidence
- 5
- items on the page
- Rivals
- 1
- named in sources
- First version
- 25 d
- estimate
- Type
- Desktop app
- PWA: runs in the browser, installs on Mac and Windows
- Market since
- 2025
- New market · AI estimate
ScreensConcept
Desktop app: Developers browse chat histories, search across projects, and manage archived conversations while writing code at their workstation. Sample screens on a computer, in the proposed brand. Their numbers are sample data.
api-gateway
Showing: All23 chats
About this appAI proposal
Thread Shelf is a project history view for conversations with AI code assistants. Finished chats are archived but stay in the list as muted rows, so active work stays prominent and past work stays findable. No trip to a settings page.
Import conversations from your assistant's exports or logs, group them by project, and switch between All, Active and Archived with one tap. Archive and unarchive from a row's menu. Search covers every chat, archived or not.
It is for developers and small teams who run many conversations per project and want archiving to feel safe: a way to tidy up without losing sight of past work.
- Tagline
- Archive without losing sight of it.
- Voice
- CalmClearPractical
- Why this name
- A shelf keeps finished things in sight and in order. Thread is the word for a chat. Two plain words, easy to say.
In the first version
Members say which features they would use. It tells PWAS what people want; it changes no score.
Muted archived rows
Archived chats stay in the project list, greyed and compact. Active chats keep full weight, so the list is easy to scan.
No member yet
All / Active / Archived toggle
One control switches the view. Your choice is remembered per project.
No member yet
Archive from the row menu
Archive and unarchive from a row's context menu or a swipe. Undo is always one tap away.
No member yet
Search across everything
Find a chat by title, file name or text. Archived results are marked so you know what you are opening.
No member yet
Brand identityAI proposal
Check the name against trademark registers before using it.
Palette
#2F6B5ESpruce · primary#F6F3ECPaper · surface#1F2A2EInk · text#D9822BAmber · accent#8A9490Mist · muted archived rows
Typography
Aa
Thread Shelf
ABCDEFGHIJKLMNOPQRSTUVWXYZ 0123456789
Archive without losing sight of it.
PricingAI proposal
The material gives no competitor or market prices. These tiers are a starting point to test, not based on any figure in the evidence.
Free
Free
- 1 project
- Up to 50 imported chats
- All / Active / Archived views
Solo
$6 a month
- Unlimited projects and chats
- Full search
- Timeline view
- Digest export
Team
$12 a month
- Per seat, shared projects
- Shared read-only digest links
- Shared archive rules
Would you pay Solo · $6 a month?
Your answer tells PWAS which prices people accept. It changes no score.
No answers yet.
What it could be worthEstimate
What a software business making this much sells for today, from real deals. Pick a monthly revenue.
If it makes
Worth about
$194,000
Sale range $132,000 to $263,000
$120,000 a year in revenue
From 87 software businesses listed and sold on Empire Flippers in the last year, revenue vetted by the broker: they sell for about 19× their monthly revenue, most between 13× and 26×.
Measured on profit, the middle deal is 32× monthly net profit: about 2.7 years of profit.
An estimate, not an offer or financial advice. A real price depends on profit, growth, churn, how much of the work is the owner's, and the buyer.
How it would growAI proposal
How the product would reach new customers through its own use, and how the first ones would be found. A plan to test, not a result.
- Built-in loop
- Shared outputs. Users share a read-only project digest link or Markdown file with teammates or in a handoff. The page lists chats and their status and carries a small Thread Shelf mark.
- Do they become customers?
- Recipients are often developers on the same project, so some may become users. To test: how many digest links are opened, and how many viewers import their own chats.
- First customers
- Developers who use one AI code assistant daily and keep dozens of chats per project, starting with those who commented on the public feature request.
- Where to reach them
- GitHub issue threads: Reply in the open issue and related ones with a short demo and a free import link. Offer it as a stopgap.
- Developer communities: Post a short before-and-after clip in forums and subreddits where users of the assistant discuss workflow.
- First milestone
- Fifty imports from real users and ten paying Solo subscribers within 60 days of launch.
Why people already pay for this
- VerifiedOpen GitHub issue has 24 reactions and 8 comments
- Public claimUsers with many Codex conversations per project use archiving to declutter the active chat list, but archived chats become difficult to rediscover.
- Public claimThe current workflow forces users to navigate to Settings or use search to find archived chats.
- Public claimUsers perceive the current archive feature as hiding work rather than preserving it as part of project history.
- AI inference
Tech stack
Every proposal builds on the same PWA base, installable from the browser on any phone or computer. Dashed boxes are what this app adds.
- AppNext.js and TypeScript
- PWAManifest and service worker
- UITailwind CSS
- Data and authSupabase Postgres
- PaymentsStripe
- EmailResend
- HostingVercel
- This app · Import parsersExport and log file parsers for chosen assistantsThe app needs a way to read chats from the assistants' exports. This is the core integration work.
- This app · Local storageBrowser database (IndexedDB) with offline cacheLets users browse history offline and keeps imported chat text on their device if they prefer.
RisksAI inference
- PlatformA web app cannot read a desktop assistant's chats directly. It depends on exports or logs that may be missing, limited or changed without notice.
- CommercialThe vendor could add muted archived rows to its own app, since the request is public. A separate tool would then have little reason to exist.
- DataChats may hold private code and secrets. Storing them on a server needs clear consent, encryption and a local-only option.
- CommercialThe evidence is one issue with 24 reactions and 8 comments. Willingness to pay for a separate tool is untested.
- TechnicalEach assistant exports in a different format, and formats change. Keeping parsers current is ongoing work.
Everything marked AI proposal or AI inference was written by a model from the evidence on the opportunity page. The proposed name must be checked against trademark registers before it is used.