You built the chat. Now you need someone else to pick it up mid-thread.
You want to show an assistant to a colleague, a class, or a client. You send a link. They read the thread. Then they ask the obvious follow-up: can I keep going from here, on my own copy, without sitting in your account?
Most off-the-shelf chat products stop at a read-only snapshot. You are left wiring persistence, public links, and fork logic yourself if you want that social flow in your own app.
IndieGPT is a full-stack starter built around that gap: multiple conversations, shareable threads, and a fork path so someone can continue from a public chat.
Pass the link. They fork it. You both move on.
What you get
- Shareable conversations. Expose a thread with a link so someone else can view the context you chose to make public.
- Fork and continue. Let a viewer branch from a public conversation and keep replying on their own copy of the thread.
- A dashboard for many threads. Start and switch between separate chats instead of one endless list.
- Sign-in your way. The repository lists Google and GitHub login options so users are not anonymous by default when you deploy it.
- A base you can extend. Client and backend setup steps live in the repository README paths cited on this page, so you can plug in your own models and policies.
Picture your Tuesday afternoon
An illustrative case: you run a short demo for three people. You share one conversation link in the call. One person forks it during the session and keeps asking questions on their own copy while you start a fresh thread for the group. Nobody needs your password. Nobody loses the original context you published.
Ready to try it?
Treat anything public-facing as needing your own content policies and moderation choices before you invite strangers.










