t3code-session-manager 0.0.0-stage → 0.4.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (172) hide show
  1. package/.claude-plugin/marketplace.json +21 -0
  2. package/.claude-plugin/plugin.json +19 -0
  3. package/CHANGELOG.md +149 -0
  4. package/LICENSE +21 -0
  5. package/README.md +661 -2
  6. package/README.pt.md +617 -0
  7. package/bin/entry.d.mts +2 -0
  8. package/bin/entry.mjs +19 -0
  9. package/bin/t3sm.mjs +44 -0
  10. package/commands/import.md +30 -0
  11. package/commands/organize.md +36 -0
  12. package/commands/status.md +24 -0
  13. package/commands/sync.md +26 -0
  14. package/dist/apply/apply.js +993 -0
  15. package/dist/apply/claudeWriter.js +168 -0
  16. package/dist/apply/copyTranscript.js +116 -0
  17. package/dist/apply/importer.js +697 -0
  18. package/dist/apply/materialize.js +335 -0
  19. package/dist/apply/waves.js +108 -0
  20. package/dist/assistant/core.js +295 -0
  21. package/dist/assistant/deps.js +256 -0
  22. package/dist/assistant/i18n.js +38 -0
  23. package/dist/assistant/messages.en.js +494 -0
  24. package/dist/assistant/messages.pt.js +495 -0
  25. package/dist/assistant/runner.js +64 -0
  26. package/dist/assistant/steps.js +1362 -0
  27. package/dist/build.json +1 -0
  28. package/dist/cli/applyScreen.js +158 -0
  29. package/dist/cli/commands/accounts.js +254 -0
  30. package/dist/cli/commands/apply.js +199 -0
  31. package/dist/cli/commands/changelog.js +61 -0
  32. package/dist/cli/commands/doctor.js +105 -0
  33. package/dist/cli/commands/help.js +158 -0
  34. package/dist/cli/commands/merge.js +224 -0
  35. package/dist/cli/commands/organize.js +872 -0
  36. package/dist/cli/commands/plan.js +161 -0
  37. package/dist/cli/commands/projects.js +430 -0
  38. package/dist/cli/commands/quarantine.js +203 -0
  39. package/dist/cli/commands/recover.js +230 -0
  40. package/dist/cli/commands/rollback.js +281 -0
  41. package/dist/cli/commands/scan.js +117 -0
  42. package/dist/cli/commands/schedule.js +288 -0
  43. package/dist/cli/commands/start.js +45 -0
  44. package/dist/cli/commands/status.js +615 -0
  45. package/dist/cli/commands/sync.js +336 -0
  46. package/dist/cli/commands/update.js +398 -0
  47. package/dist/cli/errors.js +53 -0
  48. package/dist/cli/failures.js +91 -0
  49. package/dist/cli/flags.js +53 -0
  50. package/dist/cli/help.en.js +549 -0
  51. package/dist/cli/help.pt.js +566 -0
  52. package/dist/cli/helpText.js +211 -0
  53. package/dist/cli/helpTopics.js +58 -0
  54. package/dist/cli/locked.js +12 -0
  55. package/dist/cli/main.js +155 -0
  56. package/dist/cli/screen.js +3 -0
  57. package/dist/cli/ui.js +111 -0
  58. package/dist/cli/words.js +2 -0
  59. package/dist/core/activity.js +16 -0
  60. package/dist/core/changelog.js +47 -0
  61. package/dist/core/config.js +530 -0
  62. package/dist/core/fsutil.js +171 -0
  63. package/dist/core/glob.js +34 -0
  64. package/dist/core/history.js +32 -0
  65. package/dist/core/journal.js +274 -0
  66. package/dist/core/lock.js +337 -0
  67. package/dist/core/mask.js +31 -0
  68. package/dist/core/paths.js +68 -0
  69. package/dist/core/pid.js +101 -0
  70. package/dist/core/run.js +4 -0
  71. package/dist/core/semver.js +18 -0
  72. package/dist/core/sysroot.js +29 -0
  73. package/dist/core/types.js +229 -0
  74. package/dist/core/uuid.js +29 -0
  75. package/dist/core/version.js +72 -0
  76. package/dist/help/convert.md +20 -0
  77. package/dist/help/convert.pt.md +21 -0
  78. package/dist/help/cwd-unreadable.md +22 -0
  79. package/dist/help/cwd-unreadable.pt.md +22 -0
  80. package/dist/help/decisions.md +20 -0
  81. package/dist/help/decisions.pt.md +20 -0
  82. package/dist/help/errors.md +20 -0
  83. package/dist/help/errors.pt.md +22 -0
  84. package/dist/help/held.md +20 -0
  85. package/dist/help/held.pt.md +20 -0
  86. package/dist/help/history.md +27 -0
  87. package/dist/help/history.pt.md +29 -0
  88. package/dist/help/instance-unavailable.md +18 -0
  89. package/dist/help/instance-unavailable.pt.md +19 -0
  90. package/dist/help/not-imported.md +19 -0
  91. package/dist/help/not-imported.pt.md +19 -0
  92. package/dist/help/orphaned.md +19 -0
  93. package/dist/help/orphaned.pt.md +19 -0
  94. package/dist/help/project-mismatch.md +15 -0
  95. package/dist/help/project-mismatch.pt.md +15 -0
  96. package/dist/help/t3-native.md +22 -0
  97. package/dist/help/t3-native.pt.md +22 -0
  98. package/dist/help/updates.md +26 -0
  99. package/dist/help/updates.pt.md +28 -0
  100. package/dist/help/watcher.md +24 -0
  101. package/dist/help/watcher.pt.md +25 -0
  102. package/dist/i18n/cli.js +41 -0
  103. package/dist/i18n/lang.js +55 -0
  104. package/dist/i18n/messages.en.js +1140 -0
  105. package/dist/i18n/messages.pt.js +1149 -0
  106. package/dist/i18n/words.js +12 -0
  107. package/dist/ops/accounts.js +170 -0
  108. package/dist/ops/autoUpdate.js +223 -0
  109. package/dist/ops/discoverAccounts.js +343 -0
  110. package/dist/ops/doctor.js +811 -0
  111. package/dist/ops/elevated.js +47 -0
  112. package/dist/ops/errorCodes.js +39 -0
  113. package/dist/ops/follow.js +558 -0
  114. package/dist/ops/merge.js +830 -0
  115. package/dist/ops/notify.js +249 -0
  116. package/dist/ops/plugin.js +92 -0
  117. package/dist/ops/projects.js +113 -0
  118. package/dist/ops/quarantine.js +415 -0
  119. package/dist/ops/rollback.js +868 -0
  120. package/dist/ops/schedule.js +464 -0
  121. package/dist/ops/successor.js +51 -0
  122. package/dist/ops/sync.js +859 -0
  123. package/dist/ops/syncStatus.js +290 -0
  124. package/dist/ops/update.js +273 -0
  125. package/dist/ops/updater.js +641 -0
  126. package/dist/ops/watch.js +676 -0
  127. package/dist/ops/watcherControl.js +212 -0
  128. package/dist/ops/watcherHealth.js +75 -0
  129. package/dist/organize/apply.js +495 -0
  130. package/dist/organize/history.js +192 -0
  131. package/dist/organize/plan.js +283 -0
  132. package/dist/organize/rename.js +58 -0
  133. package/dist/organize/sessions.js +100 -0
  134. package/dist/organize/titles.js +70 -0
  135. package/dist/organize/types.js +73 -0
  136. package/dist/plan/categories.js +104 -0
  137. package/dist/plan/dedupe.js +137 -0
  138. package/dist/plan/folders.js +82 -0
  139. package/dist/plan/names.js +93 -0
  140. package/dist/plan/ownership.js +316 -0
  141. package/dist/plan/planner.js +669 -0
  142. package/dist/plan/rehome.js +101 -0
  143. package/dist/plan/report.js +407 -0
  144. package/dist/sources/cache.js +89 -0
  145. package/dist/sources/claude.js +297 -0
  146. package/dist/sources/codex.js +496 -0
  147. package/dist/sources/flatten.js +23 -0
  148. package/dist/sources/jsonl.js +169 -0
  149. package/dist/sources/native.js +233 -0
  150. package/dist/sources/opencode.js +483 -0
  151. package/dist/sources/pi.js +133 -0
  152. package/dist/sources/registry.js +67 -0
  153. package/dist/sources/types.js +80 -0
  154. package/dist/t3/api.js +492 -0
  155. package/dist/t3/auth.js +248 -0
  156. package/dist/t3/compat.js +62 -0
  157. package/dist/t3/decode.js +408 -0
  158. package/dist/t3/errors.js +185 -0
  159. package/dist/t3/rpc.js +185 -0
  160. package/dist/t3/runtime.js +80 -0
  161. package/dist/ui/caps.js +56 -0
  162. package/dist/ui/components.js +202 -0
  163. package/dist/ui/layout.js +205 -0
  164. package/dist/ui/list.js +423 -0
  165. package/dist/ui/locale.js +73 -0
  166. package/dist/ui/organizePreview.js +72 -0
  167. package/dist/ui/progress.js +237 -0
  168. package/dist/ui/style.js +32 -0
  169. package/dist/ui/terminal.js +126 -0
  170. package/dist/ui/text.js +186 -0
  171. package/package.json +58 -4
  172. package/skills/t3code-sessions/SKILL.md +183 -0
@@ -0,0 +1,229 @@
1
+ // Shared types. Types only: no runtime code here.
2
+ // src/core/types.ts
3
+
4
+
5
+
6
+
7
+
8
+
9
+
10
+
11
+
12
+
13
+
14
+
15
+
16
+
17
+
18
+
19
+
20
+
21
+
22
+
23
+
24
+
25
+
26
+
27
+
28
+
29
+
30
+
31
+
32
+
33
+
34
+
35
+
36
+
37
+
38
+
39
+
40
+
41
+
42
+
43
+
44
+
45
+
46
+
47
+
48
+
49
+
50
+
51
+
52
+    
53
+
54
+
55
+
56
+
57
+
58
+
59
+
60
+
61
+
62
+
63
+  
64
+
65
+
66
+
67
+
68
+
69
+  
70
+
71
+
72
+
73
+
74
+
75
+
76
+
77
+
78
+
79
+
80
+
81
+
82
+
83
+
84
+
85
+
86
+
87
+
88
+
89
+
90
+
91
+
92
+
93
+
94
+
95
+
96
+
97
+
98
+
99
+
100
+
101
+
102
+
103
+
104
+
105
+
106
+
107
+
108
+
109
+
110
+
111
+
112
+
113
+
114
+
115
+
116
+
117
+
118
+  
119
+
120
+
121
+
122
+
123
+
124
+
125
+
126
+
127
+
128
+
129
+
130
+
131
+
132
+
133
+
134
+
135
+
136
+
137
+
138
+
139
+
140
+
141
+
142
+
143
+
144
+
145
+
146
+
147
+
148
+
149
+
150
+
151
+  
152
+
153
+
154
+
155
+
156
+
157
+
158
+
159
+
160
+
161
+
162
+
163
+
164
+
165
+
166
+
167
+
168
+
169
+
170
+
171
+
172
+
173
+
174
+
175
+
176
+ /** What `t3sm organize` changes in T3 Code (spec §5); re-exported by src/organize/types.ts. */
177
+
178
+
179
+ /** Where a session's folder came from (spec §4): `project` is always imported as is. */
180
+
181
+
182
+ /** The history rule: the last `days` days (1..3650, or "all") stay visible, and at least `minPerProject` (0..1000) per project. */
183
+
184
+ /** What config.json may hold for `organize.history`: the rule, or a 0.2 string kept readable ("off" = no history rule). */
185
+
186
+ /** The `organize` settings of config.json, every field filled (see `organizeSettings`). */
187
+
188
+
189
+
190
+
191
+
192
+
193
+
194
+
195
+
196
+
197
+
198
+
199
+
200
+
201
+
202
+
203
+
204
+
205
+
206
+
207
+
208
+
209
+
210
+
211
+
212
+
213
+
214
+
215
+
216
+
217
+
218
+
219
+
220
+
221
+
222
+
223
+
224
+
225
+ /**
226
+ * Where t3sm updates come from (remembered in `<state>/update.json`): the npm registry's published versions, GitHub's
227
+ * tags, or a local checkout's tags.
228
+ */
229
+
@@ -0,0 +1,29 @@
1
+ import { createHash } from "node:crypto";
2
+
3
+ export const T3SM_NAMESPACE = "b7e1c3a2-5f4d-4e8b-9a6c-2d1f0e3b4a59";
4
+
5
+ const UUID_RE = /^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/i;
6
+
7
+ export function isUuid(s ) {
8
+ return UUID_RE.test(s);
9
+ }
10
+
11
+ /** RFC 4122 version-5 (SHA-1, name-based) UUID. */
12
+ export function uuidV5(name , namespace = T3SM_NAMESPACE) {
13
+ if (!isUuid(namespace)) throw new Error(`invalid namespace UUID: ${namespace}`);
14
+ const ns = Buffer.from(namespace.replace(/-/g, ""), "hex");
15
+ const h = createHash("sha1").update(ns).update(Buffer.from(name, "utf8")).digest();
16
+ const b = h.subarray(0, 16);
17
+ b[6] = (b[6] & 0x0f) | 0x50;
18
+ b[8] = (b[8] & 0x3f) | 0x80;
19
+ const x = b.toString("hex");
20
+ return `${x.slice(0, 8)}-${x.slice(8, 12)}-${x.slice(12, 16)}-${x.slice(16, 20)}-${x.slice(20, 32)}`;
21
+ }
22
+
23
+ /**
24
+ * Merge revision id of a Claude session at a given transcript size (spec §4.6): deterministic, so a re-run on the same
25
+ * unchanged session finds the same revision; any growth of the transcript is a new revision.
26
+ */
27
+ export function revisionUuid(nativeId , size ) {
28
+ return uuidV5(`rev:${nativeId}:${size}`);
29
+ }
@@ -0,0 +1,72 @@
1
+ // What t3sm build this is, and what build an install root holds now. The background watcher records its own stamp at
2
+ // start and compares it with the install root's after every cycle: a different one means a newer t3sm was installed
3
+ // (or the checkout was updated), and the watcher restarts into it (src/ops/watch.ts, src/cli/commands/sync.ts).
4
+ //
5
+ // The stamp: an installed package (it runs dist/) has dist/build.json `{version, builtAt}` written by scripts/build.js,
6
+ // and its stamp is builtAt; a checkout (it runs src/; same rule as bin/entry.mjs) is stamped `checkout:<package.json
7
+ // mtimeMs>`. The version always comes from package.json.
8
+
9
+ import { readFileSync, statSync, existsSync } from "node:fs";
10
+ import { join } from "node:path";
11
+ import { fileURLToPath } from "node:url";
12
+
13
+
14
+
15
+ /** This install's root: the folder holding package.json, bin/ and src/ or dist/ (two levels above src/core, dist/core). */
16
+ export function installRoot() {
17
+ return fileURLToPath(new URL("../..", import.meta.url));
18
+ }
19
+
20
+ /** This install's version, read fresh from package.json. */
21
+ export function packageVersion() {
22
+ try { return (JSON.parse(readFileSync(new URL("../../package.json", import.meta.url), "utf8")) ).version ?? "0.0.0"; } catch { return "0.0.0"; }
23
+ }
24
+
25
+ /** A checkout runs src/ (src/ next to bin/, not inside node_modules); everything else runs dist/ (bin/entry.mjs). */
26
+ function isCheckout(root ) {
27
+ return !root.split(/[\\/]+/).includes("node_modules") && existsSync(join(root, "src", "cli", "main.ts"));
28
+ }
29
+
30
+ /** The file whose content (dist) or time (checkout) makes the stamp. */
31
+ function stampFile(root ) {
32
+ return isCheckout(root) ? join(root, "package.json") : join(root, "dist", "build.json");
33
+ }
34
+
35
+ /** What `root` holds now. Throws when package.json or (for an installed package) dist/build.json cannot be read. */
36
+ export function installStamp(root ) {
37
+ const pkg = JSON.parse(readFileSync(join(root, "package.json"), "utf8"));
38
+ const version = pkg && typeof pkg === "object" ? (pkg ).version : undefined;
39
+ if (typeof version !== "string" || version === "") throw new Error(`${join(root, "package.json")} has no version`);
40
+ if (isCheckout(root)) return { version, stamp: `checkout:${statSync(join(root, "package.json")).mtimeMs}` };
41
+ const b = JSON.parse(readFileSync(join(root, "dist", "build.json"), "utf8"));
42
+ const builtAt = b && typeof b === "object" ? (b ).builtAt : undefined;
43
+ if (typeof builtAt !== "string" || builtAt === "") throw new Error(`${join(root, "dist", "build.json")} has no builtAt`);
44
+ return { version, stamp: builtAt };
45
+ }
46
+
47
+ /**
48
+ * When the stamp file last changed on this disk (the later of its mtime and ctime: npm packs files with a fixed 1985
49
+ * mtime, but extracting them moves the ctime), or null when it cannot be read. `doctor` uses it to tell a watcher that
50
+ * has not had a cycle to notice a new install yet from one that does not restart.
51
+ */
52
+ export function installChangedAt(root ) {
53
+ try {
54
+ const st = statSync(stampFile(root));
55
+ return Math.max(st.mtimeMs, st.ctimeMs);
56
+ } catch { return null; }
57
+ }
58
+
59
+ /** How long a new install's stamp file must be left alone before the watcher restarts into it. */
60
+ export const INSTALL_SETTLE_MS = 30_000;
61
+
62
+ /**
63
+ * Whether `root` looks complete and settled enough to restart into: bin/t3sm.mjs and, for an installed package,
64
+ * dist/cli/main.js exist, and the stamp file last changed at least INSTALL_SETTLE_MS before `now` (npm may still be
65
+ * writing the rest). Not ready: the watcher keeps running and looks again after its next cycle.
66
+ */
67
+ export function installReady(root , now ) {
68
+ if (!existsSync(join(root, "bin", "t3sm.mjs"))) return false;
69
+ if (!isCheckout(root) && !existsSync(join(root, "dist", "cli", "main.js"))) return false;
70
+ const at = installChangedAt(root);
71
+ return at !== null && now - at >= INSTALL_SETTLE_MS;
72
+ }
@@ -0,0 +1,20 @@
1
+ # Conversion: sessions t3sm converts before importing
2
+
3
+ ## What it means
4
+
5
+ T3 Code cannot read some sessions as they are: OpenCode sessions, and Codex sessions that Codex compressed. t3sm
6
+ writes a copy of each as a Claude conversation next to the account's other ones, then T3 Code imports that copy. Your
7
+ original files are never changed.
8
+
9
+ ## Why a conversion fails
10
+
11
+ - The agent's storage changed and this t3sm cannot read it: update t3sm (`t3sm update`).
12
+ - The session could not be read (a locked or damaged file): try again later; `t3sm scan` counts read errors.
13
+ - The copy could not be written (disk full, no permission), or a file with the same name is already there: free some
14
+ space, or move that file away.
15
+ - The destination folder cannot be used (a temporary or system folder): pick one in `t3sm start`.
16
+
17
+ ## What to do
18
+
19
+ Run `t3sm apply` again once the cause is fixed. `t3sm rollback --run <id> --dry-run` shows the copies a run wrote;
20
+ a rollback deletes them unless you edited them.
@@ -0,0 +1,21 @@
1
+ # Conversão: sessões que o t3sm converte antes de importar
2
+
3
+ ## O que quer dizer
4
+
5
+ O T3 Code não consegue ler algumas sessões tal como estão: as do OpenCode e as do Codex que o Codex comprimiu. O t3sm
6
+ escreve uma cópia de cada uma como conversa do Claude, ao lado das outras da conta, e o T3 Code importa essa cópia.
7
+ Os teus ficheiros originais nunca mudam.
8
+
9
+ ## Porque falha uma conversão
10
+
11
+ - O formato do agente mudou e este t3sm não o consegue ler: atualiza o t3sm (`t3sm update`).
12
+ - A sessão não pôde ser lida (um ficheiro bloqueado ou danificado): tenta mais tarde; o `t3sm scan` conta os erros
13
+ de leitura.
14
+ - A cópia não pôde ser escrita (disco cheio, sem permissão), ou já lá está um ficheiro com o mesmo nome: liberta
15
+ espaço, ou tira esse ficheiro de lá.
16
+ - A pasta de destino não pode ser usada (uma pasta temporária ou do sistema): escolhe uma no `t3sm start`.
17
+
18
+ ## O que fazer
19
+
20
+ Corre `t3sm apply` outra vez depois de resolver a causa. O `t3sm rollback --run <id> --dry-run` mostra as cópias que
21
+ uma execução escreveu; um rollback apaga-as, a menos que as tenhas editado.
@@ -0,0 +1,22 @@
1
+ # Folder unreadable: T3 Code cannot tell where a conversation ran
2
+
3
+ ## What it means
4
+
5
+ T3 Code files each conversation under a project by the folder written at the start of its transcript, and it only
6
+ looks at the first 1 MiB (and the first 1000 records). This conversation's folder is past that point, or not recorded
7
+ at all, so T3 Code cannot place it:
8
+
9
+ - `t3sm apply` (and `t3sm sync`) report it as not imported: "its folder is unreadable" (exit 5);
10
+ - `t3sm plan` counts it under the skipped sessions: "folder unreadable", or "no folder recorded" when the transcript
11
+ names no folder.
12
+
13
+ ## Why it happens
14
+
15
+ The conversation began with a very large first message or attachment, so the folder comes too late, or the agent
16
+ never wrote a folder into it.
17
+
18
+ ## What to do
19
+
20
+ - Nothing to fix in t3sm, and running `t3sm apply` again does not change it: the transcript stays as it is.
21
+ - The conversation is safe on disk. Continue it in a terminal from its project folder, for a Claude Code session with
22
+ `claude --resume <session id>` (the id is the transcript's file name).
@@ -0,0 +1,22 @@
1
+ # Pasta ilegível: o T3 Code não sabe onde a conversa correu
2
+
3
+ ## O que quer dizer
4
+
5
+ O T3 Code põe cada conversa num projeto pela pasta escrita no início do registo dela, e só olha para o primeiro
6
+ 1 MiB (e para os primeiros 1000 registos). A pasta desta conversa está depois disso, ou nem está escrita, por isso o
7
+ T3 Code não a consegue colocar:
8
+
9
+ - o `t3sm apply` (e o `t3sm sync`) indicam-na como não importada: "pasta ilegível" (saída 5);
10
+ - o `t3sm plan` conta-a entre as sessões ignoradas: "pasta ilegível", ou "sem pasta registada" quando o registo
11
+ não indica pasta nenhuma.
12
+
13
+ ## Porque acontece
14
+
15
+ A conversa começou com uma primeira mensagem ou um anexo muito grande, e a pasta aparece tarde demais, ou o agente
16
+ nunca escreveu a pasta no registo.
17
+
18
+ ## O que fazer
19
+
20
+ - Não há nada a corrigir no t3sm, e correr `t3sm apply` outra vez não muda nada: o registo fica como está.
21
+ - A conversa está segura no disco. Continua-a num terminal a partir da pasta do projeto; numa sessão do Claude Code,
22
+ com `claude --resume <id da sessão>` (o id é o nome do ficheiro do registo).
@@ -0,0 +1,20 @@
1
+ # Decisions: conversations that wait for your answer
2
+
3
+ ## What it means
4
+
5
+ Some conversations need a yes or no from you before t3sm brings them into T3 Code, and t3sm never guesses. Until you
6
+ answer, they wait; everything else is imported as usual.
7
+
8
+ ## Why it happens
9
+
10
+ t3sm asks about:
11
+
12
+ - conversations started in your home folder, or in a folder T3 Code refuses to open;
13
+ - conversations in temporary or system folders;
14
+ - automated conversations (started by the Agent SDK);
15
+ - conversations you deleted in T3 Code.
16
+
17
+ ## What to do
18
+
19
+ - Run `t3sm start`: it asks each question once, explains the choices and remembers your answers in config.json.
20
+ - `t3sm status` and `t3sm plan` say how many conversations wait for each question.
@@ -0,0 +1,20 @@
1
+ # Decisões: conversas à espera da tua resposta
2
+
3
+ ## O que quer dizer
4
+
5
+ Algumas conversas precisam de um sim ou de um não teu antes de o t3sm as trazer para o T3 Code, e o t3sm nunca
6
+ adivinha. Enquanto não respondes, esperam; tudo o resto é importado como de costume.
7
+
8
+ ## Porque acontece
9
+
10
+ O t3sm pergunta sobre:
11
+
12
+ - conversas começadas na tua pasta pessoal, ou numa pasta que o T3 Code recusa abrir;
13
+ - conversas em pastas temporárias ou do sistema;
14
+ - conversas automáticas (começadas pelo Agent SDK);
15
+ - conversas que apagaste no T3 Code.
16
+
17
+ ## O que fazer
18
+
19
+ - Corre `t3sm start`: faz cada pergunta uma vez, explica as escolhas e guarda as tuas respostas no config.json.
20
+ - O `t3sm status` e o `t3sm plan` dizem quantas conversas esperam por cada pergunta.
@@ -0,0 +1,20 @@
1
+ # Errors: when a t3sm command stops
2
+
3
+ ## What it means
4
+
5
+ The command stopped and says what happened. Nothing is left half done: file times are restored, and every change
6
+ made so far is journaled and can be undone with `t3sm rollback --run <id>`.
7
+
8
+ ## The common ones
9
+
10
+ - T3 Code is not running (exit 3): open it from the Start menu or your launcher, then run the command again.
11
+ - Lost contact with T3 Code (exit 3): it closed or stopped answering; open it and run the command again.
12
+ - T3 Code answered in a way t3sm does not know (exit 4): nothing was changed; update t3sm with `t3sm update`.
13
+ - A usage or configuration problem (exit 2): do what the message says. A command that writes needs `--yes` when it
14
+ does not run in a terminal.
15
+ - Another t3sm run is in progress (exit 0): wait for it; `t3sm status` shows what runs.
16
+
17
+ ## What to do
18
+
19
+ Run `t3sm doctor`: it checks everything t3sm needs and says what to fix. For an issue report, add the output of
20
+ `t3sm doctor --json` (emails are masked and your home folder is shown as ~; read it before you share it).
@@ -0,0 +1,22 @@
1
+ # Erros: quando um comando do t3sm para
2
+
3
+ ## O que quer dizer
4
+
5
+ O comando parou e diz o que aconteceu. Nada fica a meio: as datas dos ficheiros são repostas, e cada alteração feita
6
+ até ali fica no diário e pode ser desfeita com `t3sm rollback --run <id>`.
7
+
8
+ ## Os mais comuns
9
+
10
+ - O T3 Code não está a correr (saída 3): abre-o pelo menu Iniciar ou pelo teu lançador e corre o comando outra vez.
11
+ - Sem contacto com o T3 Code (saída 3): fechou ou deixou de responder; abre-o e corre o comando outra vez.
12
+ - O T3 Code respondeu de uma forma que o t3sm não conhece (saída 4): nada foi alterado; atualiza o t3sm com
13
+ `t3sm update`.
14
+ - Um problema de uso ou de configuração (saída 2): faz o que a mensagem diz. Um comando que escreve precisa de `--yes`
15
+ quando não corre num terminal.
16
+ - Outra execução do t3sm está a decorrer (saída 0): espera por ela; o `t3sm status` mostra o que está a correr.
17
+
18
+ ## O que fazer
19
+
20
+ Corre `t3sm doctor`: verifica tudo o que o t3sm precisa e diz o que corrigir. Para reportar um problema, junta o
21
+ resultado de `t3sm doctor --json` (os emails vão mascarados e a tua pasta pessoal aparece como ~; lê-o antes de o
22
+ partilhares).
@@ -0,0 +1,20 @@
1
+ # Held: a project waits while a conversation is in use
2
+
3
+ ## What it means
4
+
5
+ A conversation of this project was written in the last 10 minutes, so t3sm leaves the whole project for the next
6
+ run. T3 Code imports every recent conversation of a project at once, and moving file times under a conversation
7
+ that is being written could disturb it.
8
+
9
+ ## Why it happens
10
+
11
+ - You (or an agent) are working in that project right now, in a terminal or in T3 Code.
12
+ - The conversation that runs `/t3sm:sync` inside T3 Code is itself in use, so its own project waits.
13
+ - A file of the project stayed locked by another program (an antivirus, OneDrive).
14
+
15
+ ## What to do
16
+
17
+ - Nothing: the project is imported once its conversations have been idle for 10 minutes. `t3sm sync` (and the
18
+ background watcher) retries on its own.
19
+ - To import it now, close or pause that conversation, wait 10 minutes and run `t3sm apply`.
20
+ - `t3sm status` shows each waiting project and since when.
@@ -0,0 +1,20 @@
1
+ # À espera: uma conversa do projeto está em uso
2
+
3
+ ## O que quer dizer
4
+
5
+ Uma conversa deste projeto foi escrita nos últimos 10 minutos, por isso o t3sm deixa o projeto inteiro para a
6
+ execução seguinte. O T3 Code importa de uma vez todas as conversas recentes de um projeto, e mudar as datas dos
7
+ ficheiros de uma conversa que está a ser escrita podia perturbá-la.
8
+
9
+ ## Porque acontece
10
+
11
+ - Tu (ou um agente) estás a trabalhar nesse projeto agora, num terminal ou no T3 Code.
12
+ - A conversa que corre o `/t3sm:sync` dentro do T3 Code também está em uso, por isso o projeto dela espera.
13
+ - Um ficheiro do projeto ficou bloqueado por outro programa (um antivírus, o OneDrive).
14
+
15
+ ## O que fazer
16
+
17
+ - Nada: o projeto é importado quando as conversas dele estiverem paradas há 10 minutos. O `t3sm sync` (e o vigilante
18
+ em segundo plano) volta a tentar sozinho.
19
+ - Para o importar já, fecha ou pausa essa conversa, espera 10 minutos e corre `t3sm apply`.
20
+ - O `t3sm status` mostra cada projeto à espera e desde quando.
@@ -0,0 +1,27 @@
1
+ # History: which conversations stay shown in each project
2
+
3
+ ## What it means
4
+
5
+ t3sm keeps each project's list short. Conversations active in the last 90 days stay shown inside their project;
6
+ older ones are settled: they stay in their project, on its Settled shelf. A project with fewer recent conversations
7
+ still shows its 10 most recent.
8
+
9
+ ## Why it happens
10
+
11
+ That is the history rule, `organize.history` in config.json (default: the last 90 days, at least 10 per project).
12
+ It covers every imported conversation (a thread whose id starts with `import:`), whether t3sm or T3 Code's own import
13
+ brought it in; a conversation you started in T3 Code is only ever moved by T3 Code's own auto-settle option.
14
+ `t3sm organize` applies the rule; the background sync applies it right after an import to the projects that got new
15
+ conversations, and once a day to every project. T3 Code's own auto-settle setting is not changed. While that setting is
16
+ on, the conversations a project keeps shown for its minimum are marked as shown in T3 Code (a week before T3 Code's
17
+ option would reach them), so T3 Code's own option never puts them away. If you keep T3 Code's option shorter than the
18
+ rule, t3sm brings such conversations back on its next pass. A mark moves the conversation in T3 Code's working-shelf sort, and it cannot be undone:
19
+ `t3sm organize --undo` lists it as kept (T3 Code keeps it shown and outside its own option).
20
+
21
+ ## What to do
22
+
23
+ - Try another rule for one run first: `t3sm organize --history 30 --min 5 --dry-run` (or `--history all`, or
24
+ `--history off`).
25
+ - Keep the one you like in config.json (`organize.history`), or answer it in `t3sm start`.
26
+ - To change T3 Code's own setting too, add `--auto-settle 90` (1 to 90 days, or off).
27
+ - Every change is journaled: `t3sm organize --undo` puts it back.
@@ -0,0 +1,29 @@
1
+ # Histórico: que conversas ficam à vista em cada projeto
2
+
3
+ ## O que quer dizer
4
+
5
+ O t3sm mantém curta a lista de cada projeto. As conversas com atividade nos últimos 90 dias ficam à vista dentro do
6
+ projeto; as mais antigas passam para Settled: ficam no projeto, na prateleira Settled. Um projeto com menos conversas
7
+ recentes continua a mostrar as 10 mais recentes.
8
+
9
+ ## Porque acontece
10
+
11
+ É a regra do histórico, `organize.history` no config.json (por omissão: os últimos 90 dias, pelo menos 10 por
12
+ projeto). Abrange todas as conversas importadas (uma thread cujo id começa por `import:`), tenha sido o t3sm ou a
13
+ importação do próprio T3 Code a trazê-las; uma conversa que começaste no T3 Code só é mexida pela opção do próprio
14
+ T3 Code. O `t3sm organize` aplica a regra; a sincronização em segundo plano aplica-a logo a seguir a uma importação aos
15
+ projetos que receberam conversas novas, e uma vez por dia a todos os projetos. A passagem automática para Settled do
16
+ próprio T3 Code não muda. Enquanto essa opção estiver ligada, as conversas que um projeto mantém à vista para o seu
17
+ mínimo ficam marcadas como visíveis no T3 Code (uma semana antes de a opção do T3 Code lhes chegar), para que a opção do
18
+ próprio T3 Code nunca as arrume. Se mantiveres a opção do T3 Code mais curta do que a regra, o t3sm traz essas
19
+ conversas de volta na passagem seguinte. Uma
20
+ marca muda o lugar da conversa na ordenação da prateleira de trabalho do T3 Code e não se desfaz: o
21
+ `t3sm organize --undo` lista-a como mantida (o T3 Code mantém-na à vista e fora da sua própria opção).
22
+
23
+ ## O que fazer
24
+
25
+ - Experimenta primeiro outra regra só numa execução: `t3sm organize --history 30 --min 5 --dry-run` (ou
26
+ `--history all`, ou `--history off`).
27
+ - Guarda a que preferires no config.json (`organize.history`), ou responde no `t3sm start`.
28
+ - Para mudar também a definição do próprio T3 Code, acrescenta `--auto-settle 90` (de 1 a 90 dias, ou off).
29
+ - Cada alteração fica no diário: o `t3sm organize --undo` repõe-na.
@@ -0,0 +1,18 @@
1
+ # Account off: the conversation's account is not usable in T3 Code
2
+
3
+ ## What it means
4
+
5
+ The conversation belongs to an account (or an agent such as Codex or Pi) whose instance in T3 Code is signed out,
6
+ disabled or missing, so T3 Code cannot import it.
7
+
8
+ ## Why it happens
9
+
10
+ - The account's sign-in expired in T3 Code.
11
+ - The instance, or the agent, is turned off in T3 Code's settings (Providers).
12
+ - The account has no instance in T3 Code yet.
13
+
14
+ ## What to do
15
+
16
+ 1. `t3sm accounts` shows every account, its instance and whether it is signed in.
17
+ 2. Sign in from T3 Code, or turn the agent on in its settings (Providers). A missing instance: `t3sm accounts --apply`.
18
+ 3. Then run `t3sm apply` again.