settings that drive the agent should be persisted server side. this is important when running the t3 server on another machine than the client.
Why
currently, everything is stored in local storage, so if i open the web app on my phone, settings like CODEX_HOME, CODEX_PATH, git configs etc wont have effect.
How
split configs up to client-side appearance (stored in local storage, bound to the device the UI runs on) and server persisted in sqlite storage.
ideally the client side hook would be the same so consumers didn't have to care where the config is stored, it can just pull it and use it unknowingly if it's server authorative or client state.
settings that drive the agent should be persisted server side. this is important when running the t3 server on another machine than the client.
Why
currently, everything is stored in local storage, so if i open the web app on my phone, settings like
CODEX_HOME,CODEX_PATH, git configs etc wont have effect.How
split configs up to client-side appearance (stored in local storage, bound to the device the UI runs on) and server persisted in sqlite storage.
ideally the client side hook would be the same so consumers didn't have to care where the config is stored, it can just pull it and use it unknowingly if it's server authorative or client state.