how to make permission request persist in external DB and not ephermal

[ajasingh]

HI I want to create a HITL reqeust for multi user conversations but right now document mentions its ephermal and there looks no provision to store those requests in database and resume from there , so is there any guide to help on that ?

[IeuanWalker]

That would probably have to be your own logic, not within the SDK

When the user accepts a permission request, you persist it wherever you want, and when the same permission request comes in, you auto-approve it on behalf of the user

[ajasingh]

That does not work if the container dies because the approval request id is a stored within the cli process especially for pending approvals , so unlike the resumeSession which can hydrate back the running session from session files stored on disk the approval state is not stored in those session files and once the container/cli is restarted that approval request id is gone and we are not able to resume that session from there on

[Keesan12]

The missing primitive is usually not store the approval somewhere, but make approvals durable objects with stable ids.

If the pending request id lives only inside the CLI process, external persistence can't faithfully recover after a restart. What tends to work better is a receipt model: approval request id, requested capability, scope, expiry, approver identity, and final disposition all persisted independently of the live process.

That's the point where an external DB becomes reliable instead of being a best-effort cache.