Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature] A working keyless local thread store (follow-up to #73)

Aperta
  • Qualcosa non va?
#179 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
postgresql, typescript
Ambito
backend, database, documentation

Direzione di ricerca

Start with apps/server/src/standalone/, the Hono thread routes, and the existing configuration and runner tests. The relevant suites cover AgentRunner, the chat_threads, chat_runs, and chat_events stores, Postgres/PGlite persistence, SSE recovery, locking, and the documented routes in docs/STANDALONE.md and docs/STANDALONE-THREADS.md. Completion means the listed typecheck, Biome, node:test, Postgres, and browser scenarios pass, though this cross-cutting feature and existing fork make it unsuitable for a first-time contribution.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

What outcome should OpenMuse handle?

Self-hosting OpenMuse without CopilotKit Intelligence, with conversations kept in the deployment's own Postgres or PGlite: the request in #73.

I built this as a fork and released it as OpenMuse Standalone v0.1.0: https://github.com/caspianchan31/openmuse-standalone (MIT, based on main at 1ac68f3). I'm sharing it in case it helps consolidate #94 and #166, and I'm happy to open a PR or split pieces out, whichever the maintainers prefer.

Proposed behavior
  • Without CPK_INTELLIGENCE_API_KEY the API starts in local mode. With the key, behavior is unchanged from upstream, and upstream's config tests for the keyed path are kept.
  • The runtime runs in SSE mode on a persistent AgentRunner (run/connect/isRunning/stop) backed by the app's own store (chat_threads, chat_runs, chat_events). It does not implement LocalThreadEndpointRunner, whose synchronous methods would force an in-memory store.
  • /api/copilotkit/threads* (list, messages, rename, archive, restore, delete) and /api/main-thread are served by the Hono layer and scoped to the signed-in owner; /info.threadEndpoints is rewritten so the app uses them.
  • A send on a busy thread gets 409 agent_thread_locked before any SSE response, so the app holds the message as it does with AgentThreadLockedError.
  • Replies are journaled while running, and the terminal event waits for the durable save; a failed save surfaces as persistence_failed. Interrupted replies are recovered from the journal (PGlite at startup, Postgres once the lock is stale). Optional CHAT_RETENTION_DAYS.
  • Edits to upstream files are small and marked // Standalone:; new code lives in apps/server/src/standalone/.

On the points raised in the #166 review: new side chats persist through the agent-clone path with restart coverage; owner checks apply to every thread route and to run/connect/stop; failed and concurrent runs end cleanly and completion stays behind the durable write; there is no in-memory eviction, the database is the history.

How would we verify it works?
  • 583 tests (typecheck, biome, node:test); the runner and store suites also run against Postgres 17.
  • Keyless end-to-end in a browser: streaming, reload mid-reply resumes, Stop keeps the partial reply, a second tab's send is held via 409, side chats rename/archive/restore/delete, history survives an API restart and a kill -9.
  • Docs: docs/STANDALONE.md (architecture, upstream merge procedure) and docs/STANDALONE-THREADS.md (routes, schema, validation).

Known limits: no live cross-device thread metadata sync; live resume needs a single API instance.

Lingua principale
TypeScript
Stelle
5.2k
Fork
730
Merge medio
3g 20h
PR unite (30g)
96

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CopilotKit/openmuse

Tutte le issue di CopilotKit/openmuse

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.