You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
State between runs: who remembers an integration's selection #12
j/k and s change what the next frame shows. Where does that state live between runs: devdash passes opaque state back to the command (how it is returned, size limit, lifetime across restarts), or the integration keeps it itself (where, and how it scopes to one devdash instance)?
The integration owns its state. In watch mode devdash gives each keyed integration DEVDASH_STATE_FILE (0600, in a 0700 directory devdash creates and deletes) and never reads it. State lasts one devdash process. --once sets neither variable.
Decided by the agent at Shayan's request (no grilling round, 2026-10-09). Full detail in the spec: Wiki/02-Projects/Devdash/2026-10-09 1112 Integration key contract.md (private vault).
Activity
shayan-ys commentedon Oct 9, 2026
Resolution
The integration owns its state. In watch mode devdash gives each keyed integration
DEVDASH_STATE_FILE(0600, in a 0700 directory devdash creates and deletes) and never reads it. State lasts one devdash process.--oncesets neither variable.Decided by the agent at Shayan's request (no grilling round, 2026-10-09). Full detail in the spec:
Wiki/02-Projects/Devdash/2026-10-09 1112 Integration key contract.md(private vault).