NeuroChat
NeuroChat is NeuroGrid's chat app. It runs in your browser at chat.neurogrid.cc and talks to any OpenAI-compatible endpoint, including a NeuroGrid deployment.
There is no account to create and nothing to install.
NeuroChat has no database of its own and no user accounts. Your chats, files, settings and API keys are saved only in your browser, on your device. We never receive them, so we cannot read, sell, recover or delete them.
Where your data lives
Everything NeuroChat saves is kept in a SQLite database inside your browser, in the browser's private storage for the site (OPFS). That includes:
- your chats, messages and chat titles
- files and images you attach
- connections: endpoint URLs and API keys
- MCP tool servers and their tokens
- settings such as the system prompt, theme and voice choices
What this means in practice:
- No sync between devices. Chats on your laptop are not on your phone, and a different browser on the same machine starts empty.
- Clearing your browser's site data deletes your chats. So does uninstalling the browser or resetting the device. Nobody can bring them back, including us.
- Private or incognito windows don't save anything. NeuroChat falls back to memory, and the chat is gone when the window closes. The same happens if NeuroChat is already open in another tab, which holds the database.
- Temporary chats are never saved at all, not even in your browser. Use them for anything you don't want in your history.
Keeping a copy
Because nothing is stored on a server, a copy you download is the only backup. Open a chat's menu and choose Share…:
- Copy as Markdown puts the conversation on your clipboard.
- Download Markdown saves a readable
.mdfile. - Download JSON saves a complete copy, including attached images.
Sharing works the same way: the other person gets a copy of the chat, not a link to it, because there is nowhere online for a link to point to.
Deleting everything
Delete single chats from their menu. To remove everything NeuroChat has saved,
clear the site data for chat.neurogrid.cc in your browser's settings.
What does leave your browser
NeuroChat only sends data where it has to, to do what you asked:
| Where | What | When |
|---|---|---|
| The endpoint you connect to | Your messages, attachments and API key | Every time you chat. This is the model answering you. |
| MCP servers you add | The tool calls the model makes, and their token | Only after you approve each call. |
| Hugging Face | Model names, to look up icons and capabilities; one-time downloads of the speech models | When you pick a model, or first use dictation or voice mode. Never your messages or your voice. |
Your messages go to the endpoint you chose: a NeuroGrid deployment, or any other provider you configure. That endpoint's own privacy terms apply to what it receives.
The connection proxy
Some endpoints refuse requests that come straight from a browser (a CORS error when you test the connection). For those, a connection can be set to Route through NeuroChat proxy. Requests then pass through chat.neurogrid.cc on their way to the endpoint.
The proxy forwards the request and streams the reply back. It does not store
or log your messages or your API key. It only connects to NeuroGrid
deployments (*.neurogrid.cc, *.trycloudflare.com) over HTTPS, and only
forwards model and chat requests.
Leave the proxy off and your browser talks to the endpoint directly, with nothing passing through NeuroGrid at all.
Voice stays on your device
Dictation transcribes your voice with Whisper running in your browser. Voice mode (beta) speaks replies with Kokoro, also in your browser, or with your phone's own voices. The models download once from Hugging Face, then are cached by the browser. Your audio is never uploaded.
Get started
- Open chat.neurogrid.cc.
- In Settings → Connections, add a connection: a name, the endpoint URL and the API key. For a NeuroGrid deployment, both are in your NeuroGrid console.
- Press Test, then Add. NeuroChat lists the models the endpoint serves.
- Pick a model and start chatting.
Any OpenAI-compatible provider works the same way (OpenAI, OpenRouter, Groq, a local Ollama or LM Studio), as long as it accepts requests from a browser.
Invite someone
Invite turns a connection into a link that opens NeuroChat already
connected. The endpoint and key travel in the part of the link after #, which
browsers never send to the website, and NeuroChat removes them from the address
bar as soon as it opens.
The link contains your API key. Anyone who has it can use your endpoint, so send it only to people you'd give the key to. It shares the connection, never your chats.
What it can do
- Streaming replies, with a Stop button that keeps what was written so far.
- Files and images: attach PDFs, text files and pictures.
- Rich answers: syntax-highlighted code, maths, Mermaid diagrams and live HTML previews beside the chat.
- Long chats: see how much of the model's context is used, and compact a conversation so it keeps going.
- Organising: search, pin, tag, archive and file chats into folders.
- MCP tools: add MCP servers in Settings → Tools. Models that support tool calling can use them, and you approve each call.
- Voice: dictate messages, or talk hands-free in voice mode (beta).
- Light and dark mode, and it works on phones.
Troubleshooting
My chats disappeared
Cause. The browser's site data was cleared, you are in a private window, or you opened NeuroChat in a different browser or profile.
Fix. Chats saved in another browser or profile are still there; open NeuroChat in that one. Cleared data cannot be recovered. Download chats you want to keep.
Chats aren't being saved
Cause. NeuroChat is open in another tab, which holds the database, or the window is private.
Fix. Close the other NeuroChat tabs and reload, or use a normal window.
"Couldn't reach the provider"
Cause. The endpoint is down, the URL is wrong, or it blocks requests from browsers (CORS).
Fix. Check the endpoint URL in your console. For a NeuroGrid deployment, turn on Route through NeuroChat proxy for that connection.
"The API key was rejected"
Fix. Copy the key again from the console and update it in Settings → Connections.