Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Feature] Make CopilotKit Intelligence optional for self-hosted deployments

Abierto
  • ¿Algo no está bien?
#73 3 comentarios 8 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Mrdifferent2022 ya está trabajando en esto.

Desde el 7/10/2026.

  • #166 de @Mrdifferent2022 — abierto

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
api, backend, mobile, testing-qa

Línea de trabajo

Start by reading apps/server/src/config.ts and apps/server/src/app.ts to trace the unconditional Intelligence requirement and existing local conversation endpoints, then inspect apps/mobile/src/chat.tsx for the local-history path. Verify the proposed mode without CPK_INTELLIGENCE_API_KEY, using a separately configured model provider, while preserving history across restarts and reloads and keeping Intelligence behavior unchanged when selected.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What outcome should OpenMuse handle?

I'd like to self-host OpenMuse with my own model provider and local conversation storage, without requiring hosted Intelligence or a commercial self-hosted Intelligence license.

The README introduction makes Rich Threads sound optional, but the current implementation requires CPK_INTELLIGENCE_API_KEY at startup.

References:

  • PR #15 required Intelligence for live deployments.
  • PR #38 extended that requirement to every mode and removed the branches that skipped Intelligence.
  • config.ts:108 requires the key unconditionally.
  • app.ts still contains local /api/conversation GET/PUT endpoints, and chat.tsx retains a local-history path. I have not verified that these work without Intelligence.
Proposed behavior

Would you support an explicit local-persistence mode? A single saved conversation would be enough initially; Intelligence-specific thread management could remain disabled.

The mode should start without an Intelligence key and use a separately configured model provider. Authentication, token encryption, action approvals, browser tools, and background tasks should retain their existing behavior.

When Intelligence is selected, its existing behavior should remain, including errors rather than silently falling back to local storage.

If Intelligence is intentionally mandatory, could the README explain why local-only operation was removed and distinguish self-hosting OpenMuse from self-hosting its required persistence service?

How would we verify it works?
  • Start without an Intelligence key and confirm no Intelligence requests are made.
  • Complete a conversation using a separately configured model provider.
  • Preserve history across server restarts and web/iOS client reloads, without silent overwrites between clients.
  • Verify authentication, token encryption, action approvals, browser tools, and background tasks remain functional.
  • Confirm existing Intelligence thread operations still work when that mode is selected.

Source inspection is based on commit 205cc386b75aae1a862f3fdd43104b570c8d0911; no local-only deployment was tested.

Lenguaje dominante
TypeScript
Estrellas
5.2k
Forks
730
Merge medio
3 d 20 h
PR fusionados (30 d)
96

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CopilotKit/openmuse

Todos los issues de CopilotKit/openmuse

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.