Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#73 コメント 3 件 リアクション 8 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@Mrdifferent2022 がすでに取り組んでいます。

2026年10月7日 から。

  • #166 @Mrdifferent2022 による — オープン

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
38/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript
領域
api, backend, mobile, testing-qa

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
TypeScript
スター
5.2k
フォーク
730
平均マージ
3日 20時間
マージ済み PR（30日）
96

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

CopilotKit/openmuse のほかの issue

CopilotKit/openmuse の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。