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

[Task][RFC]: Qualify the effective manager runtime profile across sessions

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

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

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
python
領域
ai-infra-agents

調査の方向性

Read the canonical RFC and start with loopx/capabilities/manager_runtime/machine_profile.py, loopx/chat_manager.py, and apps/presentation/dashboard; coordinate with the current owners and #5187 before choosing an unowned acceptance gap. Verify the effective profile across the real supported endpoint and the affected CLI/frontend entrypoints, then report commands and passed, failed, and untested evidence against the acceptance checklist.

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

説明

direction/architecture-evolution

Outcome / 目标

验收管家有效运行配置与会话一致性。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree.

Canonical design: RFC. Roadmap: S1/S4/S9 · manager M1, under #4574. Design acceptance is distinct from implementation, live qualification and promotion.

Current boundary

Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim.

The machine-level restricted/trusted_owner configuration, controller integration and focused tests are already recorded as shipped. The RFC explicitly separates that implementation from deployment and full M1 qualification.

Work remaining

  • Verify the effective config, sandbox, prompt, workspace instructions and active upstream Session agree on the real supported endpoint.
  • Finish restart/profile-change/downgrade recovery and existing settings readback without adding a second configuration source.

Ownership and ongoing work

Reuse #4339 and current manager/App work; coordinate with #5187 settings consolidation. This RFC owns profile consistency, not general handoff, outbox or a new permission system.

Contribution route: implementation/integration overlaps active work. Start from the linked current owners/PRs and identify an unowned acceptance gap in a claim comment; do not begin a competing rewrite.

Acceptance

  • Default/invalid config remains restricted with actionable repair; unsupported endpoints do not pretend to enforce trusted_owner.
  • A material profile change rotates the upstream thread while preserving visible history; unrelated settings do not rotate it.
  • External audiences remain restricted absent the existing scoped grant; protected operations retain their own authorization. CLI and actual frontend expose the effective Session profile.
  • Reconcile the RFC's current delivery checkpoint and this issue with the integrated revision, commands, passed/failed/untested evidence and remaining gates. Close the accepted scope only; no claim that a merged PR alone completes the RFC.

Starting points and delivery boundary

Base: latest main. Reuse the existing typed owner and provider boundaries. Include affected CLI/frontend/Lark companions; verify real entrypoints and backend where changed. Preserve existing first-screen review and maintainer merge gates. Public artifacts contain only synthetic/public-safe evidence, no private operational state. This task does not authorize provider promotion, benchmark launches, release/deployment or unrelated protected effects.

主要言語
Python
スター
6.2k
フォーク
596
平均マージ
7時間 35分
マージ済み PR（30日）
928

環境構築

はじめの一歩

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

loopx-project/loopx のほかの issue

loopx-project/loopx の issue をすべて見る

似ている issue

Python の issue をもっと見る

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

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