Comunidad Guías…

Ayuda y problemas de piper-morgan-product

Pregunta a la comunidad o invita a KiBot con contexto del repositorio.

Publicar un problema

No publiques contraseñas, tokens ni claves privadas. HostingByte aplica una redacción básica de secretos evidentes antes de guardar el texto.

Problemas en HostingByte

Todavía no hay problemas publicados.

Issues abiertas upstream

#2351 Local running as a supported path for an outside tester: hidden-prompt key helper, tested step list, self-host guide · 6 comentarios #2353 The OS keychain is opt-in only: PIPER_CREDENTIAL_STORE unset means the database store (Arch ruling 11-12) · 1 comentarios #2359 Self-knowledge item 5: read-only code tools over the served snapshot, with a path allow-list and a read budget (after the experiment) · 0 comentarios #2358 Self-knowledge item 4: team methods as task-loaded procedures for every Piper, rewritten into user register one at a time · 0 comentarios #2357 Self-knowledge research: a lean deployment (measure the conduct layer's cost and the retrieval trigger rate) · 3 comentarios #2354 Self-knowledge part 1: conduct layer in the cached prompt prefix, with a size cap and code guards · 2 comentarios #2350 Hosts drop every info log line (root WARNING from the CLI quiet mode); evidence events need a named logger kept at INFO · 3 comentarios #1186 PIPER-SELF-KNOWLEDGE: support info + help-doc pointers + RAG over own docs (so Piper can answer 'how do you work?') · 2 comentarios #2349 EPIC: Piper self-knowledge: codebase, ethos, documentation, lore and best practices (design exploration first; Arch owns) · 4 comentarios #2352 Local key commands: rotate-key shows the pasted key, keys add writes the OS keychain by default · 0 comentarios #2356 Self-knowledge part 4: exclusion test and the served question set · 0 comentarios #2355 Self-knowledge part 2: Tier 1 user corpus from a manifest (generated capability answers, how Piper works, teachable practice, known limits) · 0 comentarios #2333 Slack spatial positions use salted hash(): a room's position changes on every process start · 4 comentarios #2348 /health should report Redis, as it does the database and the credential store · 4 comentarios #2189 Integrations 'Last checked' lives only in process memory, so every deploy resets it; plus a sweep for other user-facing state that does the same · 16 comentarios #2345 GitHub and Calendar connect keep their sign-in state in the process, not Redis · 2 comentarios #2335 RedisFactory logs the full REDIS_URL at startup; an Upstash URL carries the password · 4 comentarios #2344 Buttondown confirmations: read the sending-domain setup and check SPF/DKIM/DMARC (split from 2292) · 3 comentarios #2347 Remove two dead Redis paths: the conversation manager's turn cache and FeedbackCapture · 1 comentarios #1423 Silent-death pattern: broad try/except on the core path converts broken features into invisible defaults — inventory + un-swallow · 7 comentarios