Elsewhere is an Express + SQLite app for account-based chat, persona management, roleplay chat sessions, and a simple persona market backed by a remote model API.

A space for every conversation. Six appearance styles (Grove, Parchment, Aurora, Current, Iris, and Graphite) each support light and dark modes. The Elsewhere identity stays consistent across styles. Internal theme and storage keys remain stable to preserve saved preferences.

Setup

Node.js 22 or newer is required.

Install dependencies with npm install.
Copy .env.example to .env and set at least SESSION_SECRET.
Start the app with npm run dev for local development or npm start for a normal server run.

Scripts

npm start: run the production server entrypoint.
npm run dev: run the server with Node watch mode.
npm run lint: syntax-check the backend and browser modules.
npm test: run API tests with Node's built-in test runner.

Environment Variables

PORT: HTTP port for the Express server.
DB_PATH: SQLite database path. Use :memory: for isolated tests.
SESSION_SECRET: session signing secret. Required outside local throwaway environments.
COOKIE_SECURE: set to true when serving over HTTPS. Required in production unless ALLOW_INSECURE_COOKIES=true is set.
ALLOW_INSECURE_COOKIES: explicit production override for non-HTTPS deployments.
TRUST_PROXY: Express trust proxy setting for reverse proxy deployments.
SESSION_MAX_AGE_MS: cookie lifetime.
EVENT_LOOP_LAG_*: enable and tune event-loop lag warnings.
SLOW_REQUEST_*: enable and tune slow request warnings.
CHAT_LIMIT: per-account maximum chat sessions.
CHAT_HISTORY_LIMIT: number of recent messages included in model prompts.
MODEL_API_BASE_URL: base URL of the remote model backend. The server expects /chat and /tags.
MODEL_REQUEST_TIMEOUT_MS: timeout for chat generation requests.
MODEL_LIST_TIMEOUT_MS: timeout for model list requests.
MODEL_UNLOAD_AFTER_MS: delay before an idle model unload is attempted.
MODELS_CACHE_TTL_MS: model list cache TTL.
AUTH_RATE_LIMIT_*: rate-limit window and thresholds for registration/login.
CHAT_RATE_LIMIT_*: rate-limit window and thresholds for chat and retry endpoints.
RATE_LIMIT_CLEANUP_INTERVAL_MS: interval for pruning stale in-memory rate-limit buckets.
DROP_LEGACY_CHATS: when true, migrate any legacy chats table into chat_sessions / chat_messages and remove the old table.

Model Backend Expectations

The server is configured around an Ollama-compatible API surface:

POST /chat: accepts { model, messages, stream: true } and returns newline-delimited JSON stream chunks with message.content.
GET /tags: returns the available model list.

qwen3:14b is the default model for chat and roleplay. The model selector loads available models from /tags and selects qwen3:14b when available (otherwise the first returned model). Existing chats retain their saved model selection.

Chat replies display Ollama's optional message.thinking output in a collapsed “Reasoning” section above the answer, updated through SSE thinking events during generation. This text is stored separately from the answer and excluded from conversation prompts. An additive SQLite migration preserves it when reopening chats; exports, imports and branches preserve it too. Models without thinking output show no section.

The refactor adds explicit upstream timeout handling, cached model listing, and GET /health for degraded-state visibility.

Schema Notes

Primary runtime tables are:

users
chat_sessions
chat_messages
personas
user_settings
persona_market

Legacy chats migration is handled during startup. New code only reads the session/message schema.

Persona And Market Flow

Assistant and user personas are stored separately through persona_type.
Roleplay chats can bind an assistant persona, an optional user persona, and scenario metadata to a chat session.
Publishing copies a local persona into persona_market.
Collecting clones a market persona back into the current user's personas table with source metadata.

Frontend Structure

The browser UI remains framework-free and uses native ES modules. Shared behavior lives under public/app/:

api.js: JSON and streaming request helpers
constants.js: theme and onboarding metadata
themeController.js: validated theme/mode persistence and application
theme-bootstrap.js: applies stored appearance before page initialization
personaForm.js: shared persona form serialization
statusNotice.js: shared status and error presentation
dom.js: cached chat-page DOM references

public/style.css is a self-contained design system rebuilt around semantic tokens, shared components, and deliberate responsive breakpoints. It contains the six visual identities and their dark variants without legacy imports or precedence layers. public/legal.css contains only the legal-page layout.

Pure chat message, retry, memory, summary, and persona-state formatting lives in src/services/chatMessageHelpers.js; chatService.js remains responsible for orchestration and persistence.

Optional Web Search

The globe button next to the composer enables search for one message. It defaults to off and resets once the server accepts the message. The browser sends webSearch: true (or false) through the existing authenticated POST /chat/stream; POST /chat supports the same optional boolean. Omitting it preserves the normal chat flow. No generic tool/agent system is needed.

The existing chat service saves the user message, performs one server-side SearXNG search using the current message (whitespace normalized, at most 500 characters), then supplies up to five numbered results as a separate context alongside the existing history, model, personas and generation settings. Instructions require numbered citations, acknowledgement of insufficient results and treating all result content as untrusted data. This is a basic prompt-injection precaution, not a guarantee that a model will follow instructions. No result pages are fetched.

Set environment variables in the server/container environment, or load the example explicitly with node --env-file=.env server.js (the existing npm start command does not load .env automatically):

SEARXNG_URL=http://searxng:8080
WEB_SEARCH_TIMEOUT_MS=8000

SEARXNG_URL is optional and server-only. It must be an HTTP(S) base URL reachable from Express, for example over the same Docker network. Use the final URL: redirects are rejected. Missing/invalid configuration leaves ordinary chat available and returns Web search is currently unavailable. for search requests. WEB_SEARCH_TIMEOUT_MS limits the whole search response, including body download (default 8000 ms). Responses are limited to 1 MiB; each source has at most a 300-character title, 2048-character URL and 1500-character snippet. Only HTTP(S) source links without embedded credentials are accepted. No user input can override the provider URL.

Enable JSON in SearXNG's settings.yml:

search:
  formats:
    - html
    - json

The provider calls GET {SEARXNG_URL}/search?q=...&format=json using encoded query parameters. SearXNG must allow requests from the application server; disabled JSON output returns HTTP 403. See the official Search API documentation. Only the current query is sent to SearXNG, not conversation history or personas; configured SearXNG engines can forward that query to their search services.

The server-side WebSearchProvider JSDoc contract is search(query, {signal, limit}?) -> Promise<SearchResult[]>; SearXNGSearchProvider is the initial implementation. Results have {title, url, snippet}. This repository uses JavaScript ES modules, so types are documented with JSDoc rather than introducing a TypeScript build.

Search adds SSE status events: {status: "searching"} after message acceptance and {status: "generating", sourceCount} before model generation. Existing chunk events are unchanged. done adds optional sources to {reply}; the non-streaming response does likewise. Empty results produce sources: [] and an explicit insufficient-results instruction. Failures produce the existing error event (HTTP 503 on /chat); no model answer is generated after search failure. The saved failed user message remains visible, and the composer restores its text for resending without search.

Sources appear below assistant messages as numbered links. They persist in a nullable SQLite chat_messages.sources JSON column, added automatically on startup using the existing additive schema mechanism; no manual migration is needed. Old messages remain valid. Sources are preserved in JSON exports/imports and branches. Regenerating an answer reuses its stored results without performing another search; a fresh search requires sending another message with the toggle enabled.

Run node --test --test-isolation=none and npm run lint to check the feature and existing flows. test/webSearch.test.js uses local HTTP protocol fixtures and an isolated in-memory database; no production search results are mocked. Live SearXNG/Ollama verification still requires configured, reachable services. There is no TypeScript or build command in this framework-free project.

Legal

/ is the public landing page, even for signed-in visitors.
/login and /register provide dedicated account forms. Registration starts a session automatically.
/app is workspace home, with recent chats and optional starters.
/app/chats/new opens an empty composer; sending the first message creates the conversation.
/app/chats/:id opens a conversation. Legacy /?chat=:id links redirect here.
/app/personas provides persona management, using the shared settings editor module.
/app/settings contains account and appearance settings. /settings redirects here.
/market allows visitors to browse public summaries and signed-in users to use the full persona market.

Protected pages redirect to sign-in with a local return destination. Public discovery only returns published persona summaries; using a persona requires an account.

All page routes render the same navigation from src/pageLayout.js into the  placeholder. public/shell.css owns the shared header, page spacing, and mobile navigation; public/app/workspaceNavigation.js owns sign-out. Page-specific headers contain only local titles and actions. The chat sidebar is reserved for conversation history. Public and home content share public/pages.css and public/pages.js. Page routes run before static assets and authenticated API routers; rendered pages use private, non-cacheable responses.

For environments that block child-process test workers, run node --test --test-isolation=none.

README.md

Elsewhere