Problem
When the server changes the name of a device or the team it is associated with, the device (ox CLI / daemon) does not learn about the change. It continues to use whatever name/team it had at init time until the user manually re-runs something that fetches config.
Desired behavior
A periodic poll (or push) mechanism that pulls authoritative device config from the server so that:
- Device renames on the server propagate to the local device identity
- Team reassignments propagate to the local device
- Other server-owned config fields stay in sync without re-init
Open questions
- Daemon-driven poll vs. opportunistic refresh on existing API calls
- Polling interval and backoff
- Conflict resolution if local state has diverged
- Which API surface returns the canonical device config
Problem
When the server changes the name of a device or the team it is associated with, the device (ox CLI / daemon) does not learn about the change. It continues to use whatever name/team it had at init time until the user manually re-runs something that fetches config.
Desired behavior
A periodic poll (or push) mechanism that pulls authoritative device config from the server so that:
Open questions