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

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

Aperta
  • Qualcosa non va?
#5,212 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
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
ai-infra-agents

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
Python
Stelle
6.2k
Fork
596
Merge medio
7h 35m
PR unite (30g)
928

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 loopx-project/loopx

Tutte le issue di loopx-project/loopx

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.