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
Commit 674a81c
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): t3 thread and t3 project no longer create a database when statev2.sqlite is missing
Both commands built the auth layer, which opens and migrates statev2.sqlite,
before reading server-runtime.json. With the database moved aside, they left
an empty migrated database behind the live server. With no server registered,
`t3 thread` created a whole data dir only to report that no server runs.
`t3 thread` now reads the runtime state first and fails before building any
storage layer. When a server is registered and the database is missing, both
commands fail with "T3 Code's database is not at <path>. The server may be
restarting." and create nothing. Offline `t3 project` with no server
registered still creates the database on a fresh install.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
0 commit comments