Originally created by: fu351
Today an AUTH challenge blocks on a local prompt (terminal/GUI). For CI agents and non-interactive runs, an agent shouldn't stall a whole session waiting on a synchronous prompt. Let's add a non-blocking challenge mechanism.
What to build
Out of scope (deliberately): the hosted delivery channels (Slack/push/email routing) — this issue is the local mechanism/interface only.
Where to start: src/doberman/auth/ (the Prompter interface, provider.py, elevation). The dashboard's DB-mediated pending_approvals queue (src/doberman/storage/approvals.py) is a working reference for an async, single-use, race-safe resolve.
Difficulty: hard — touches the auth/elevation state machine. A strong hard part.
Building this? A few project invariants any change must respect:
New here? See CONTRIBUTING.md (github.com), and come chat in the Discord — happy to help you scope any of this.
Originally posted by: Maqbool61
Hi, Can you assign this to me?
Ticket changed by: fu351
Originally posted by: fu351
Sorry for the quiet day here: you answered your own question by shipping [#273], which is now merged and closes this. Review notes are on the PR, along with a suggestion for what you might enjoy next.
Related
Tickets:
#273