Rename AgentDeck branding to Talocode (CLI, env, docs, UI, tests)#5
Rename AgentDeck branding to Talocode (CLI, env, docs, UI, tests)#5Abdulmuiz44 wants to merge 1 commit into
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1f5b71044b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| export function hashToken(token: string): string { | ||
| return createHash('sha256').update(`agentdeck:v1:${token}`).digest('hex'); | ||
| return createHash('sha256').update(`talocode:v1:${token}`).digest('hex'); |
There was a problem hiding this comment.
When an existing AgentDeck data directory is migrated, the copied pairedDevices[].accessTokenHash values were created with the old agentdeck:v1: namespace, but verifyToken() now hashes incoming tokens only with talocode:v1:. In that upgrade scenario every previously paired phone token fails authentication even though the store was migrated; keep verifying the legacy namespace or migrate those hashes in a way that does not require the raw token.
Useful? React with 👍 / 👎.
| const LEGACY_TOKEN_KEY = 'agentdeck_phone_token'; | ||
| const LEGACY_DEVICE_KEY = 'agentdeck_phone_device'; |
There was a problem hiding this comment.
Existing paired phones stored their token under the old keys agentdeck.phone.accessToken and agentdeck.phone.device, but the compatibility lookup now checks agentdeck_phone_token / agentdeck_phone_device, so upgraded browsers never find their saved credentials and force users to re-pair. Point these legacy constants at the dotted keys used by the previous PhoneDashboard constants before copying them into the new Talocode keys.
Useful? React with 👍 / 👎.
|
|
||
| export function prepareDataDirMigration(options: DataDirOptions = {}): void { | ||
| const env = options.env || process.env; | ||
| if (env.TALOCODE_DATA_DIR || env.AGENTDECK_DATA_DIR) return; |
There was a problem hiding this comment.
When users keep a custom AGENTDECK_DATA_DIR, resolveDataDir() still points Talocode at that legacy directory, but this early return skips renaming agentdeck.json to the new talocode.json; JsonStore then creates a default empty talocode.json in the same directory and the existing providers/projects/sessions appear lost. Either read the legacy filename for this fallback or perform the same safe copy inside the explicit legacy data dir.
Useful? React with 👍 / 👎.
1 participant
Motivation
TALOCODE_*env vars primary withAGENTDECK_*as legacy fallbacks and update default data directories to Talocode naming with safe migration from legacy AgentDeck data.talowhile keepingagentdeckas a temporary alias and update user-facing copy to present Talocode as “a local-first control plane for coding agents.”Description
package.json(name,description,build.productName,repository,bugs,homepage) and addedtaloas primary bin while retainingagentdeckas an alias; CLI help showstalofirst and documents the compatibility alias.src/main/agentdeck/*→src/main/talocode/*, updated imports and names (AgentDeckCore→TalocodeCore, error types, daemon, sessions, etc.).envValue()andresolveDataDir()insrc/main/talocode/paths.tsto preferTALOCODE_*then fallback toAGENTDECK_*, addedprepareDataDirMigration()to copy safe JSON files from legacy AgentDeck default data dir to the new Talocode dir when appropriate.talocode_phone_*with read-from-legacyagentdeck_phone_*fallback and automatic migrate-on-read behavior.docs/agentdeck-architecture.mmd→docs/talocode-architecture.mmd, updated README and docs to Talocode wording, added migration note "Talocode started as the AgentDeck prototype." and removed public AgentDeck branding.talocode(e.g.talocode-backup-...) and replaced string occurrences for generated headers and TOML sections.scripts/smoke-test.mjsto exercise legacyAGENTDECK_PORTfallback..gitignoreentries to Talocode architecture asset names and verified no image/pdf/zip/etc. files were added in the diff.Testing
npm run lint(TypeScript typecheck) and it completed successfully with the repo dependencies installed.npm testwhich compiles tests and executed them; all tests passed (21 tests, 0 failures).npm run build(main + renderer) and the build succeeded (Vite renderer build completed anddistproduced).npm run smoke(end-to-end smoke script) and it passed, including phone pairing and legacy-port fallback verification (smoke reported success on a free port).git ls-filesgrep for binary extensions andgrepforagentdeck-architecture.pngreturned no introduced binary files; verifiedgit diff --numstatto summarize file changes.All automated checks listed above passed.
Codex Task