Conversation
There was a problem hiding this comment.
Pull request overview
Adds a roadmap/proposal document describing a small, local-only “fnox secret input UI” intended to complement the existing !secure flow by enabling write-only secret entry without leaking values into chat history.
Changes:
- Introduces a new roadmap note documenting goals/non-goals for a local fnox secret input form.
- Specifies default behaviors (loopback bind, create-only, stdin transport, no plaintext readback) and a minimal API sketch.
- Captures security requirements and open questions for a potential implementation.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| Status: proposal | ||
| Related work: `!secure` command flow, OneCLI/fnox wrapper work |
There was a problem hiding this comment.
For consistency with the other roadmap notes, consider formatting the header metadata using the same bold-key style (e.g., **Status:** …, **Priority:** …, **Depends on:** … as in docs/roadmap/outbound-sensitive-data-detection.md:3-5). This makes the metadata easier to scan across documents.
| Status: proposal | |
| Related work: `!secure` command flow, OneCLI/fnox wrapper work | |
| **Status:** proposal | |
| **Related work:** `!secure` command flow, OneCLI/fnox wrapper work |
There was a problem hiding this comment.
Codex integration sweep: acknowledged. I am leaving this PR branch untouched per the parallel-agent boundary; this remains actionable for the PR owner or a follow-up unless it is superseded by #38.
|
Closing — design ideas from this proposal were pulled into RFC #29 (now merged via #44 in main as |
Summary
Why
This captures a safer complement to
!secure: a local form for entering new secrets without putting values into chat history, while keeping the scope smaller than a secret browser or dashboard.Validation
Draft until the fnox wrapper PR lands and we decide whether to implement this as a standalone binary or a
oneclimode.