No token expiration or TTL #13

New issue

Closed

opened 2026-05-10 16:06:52 +00:00 by Mark · 2 comments

Mark commented

2026-05-10 16:06:52 +00:00

Owner

Description

Tokens have no built-in expiration. No TTL or rotation mechanism.

Impact

Old tokens remain valid indefinitely.

Suggested Fix

Add optional TTL and automatic expiration checking.

## Description Tokens have no built-in expiration. No TTL or rotation mechanism. ## Impact Old tokens remain valid indefinitely. ## Suggested Fix Add optional TTL and automatic expiration checking.

Mark added the

feature-request

label

2026-05-11 20:10:21 +00:00

Mark commented

2026-05-14 19:16:59 +00:00

Author

Owner

Approved. Implementation approach:

Add an optional duration selector (minutes/hours/turns) to the existing control panel
Store createdAt timestamp and duration in JS state alongside existing token properties
Show visual expiration indicator on expired tokens (overlay badge, grayscale filter, or dim state)
Pure client-side feature — no server changes needed since this app has no persistence layer
All existing rendering/API proxy code remains untouched

Approved. Implementation approach: - Add an optional duration selector (minutes/hours/turns) to the existing control panel - Store `createdAt` timestamp and `duration` in JS state alongside existing token properties - Show visual expiration indicator on expired tokens (overlay badge, grayscale filter, or dim state) - Pure client-side feature — no server changes needed since this app has no persistence layer - All existing rendering/API proxy code remains untouched

Mark added

blocked:no-changes

and removed

feature-request

labels

2026-05-14 19:17:01 +00:00

Mark commented

2026-05-20 19:38:59 +00:00

Author

Owner

Closed by pipeline sweep — no code changes required (blocked:no-changes). Fixer now auto-closes this case going forward.

Mark closed this issue