Skip to content

Add T3 Connect setup for local Cate workspaces - #706

Open
Anton-Horn wants to merge 1 commit into
mainfrom
feat/t3-remote-access
Open

Anton-Horn wants to merge 1 commit into
mainfrom
feat/t3-remote-access

Conversation

@Anton-Horn

Copy link
Copy Markdown
Contributor

Summary

  • Add T3 Connect controls to Cate’s T3 Code settings for a local workspace.
  • Run the bundled T3 CLI against that checkout’s isolated harness state for status, linking, and unlinking.
  • Restart the checkout’s T3 server after linking so the managed tunnel comes online; keep operations scoped to the owning window.

Verification

  • npm run typecheck
  • npx vitest run src/main/t3Agent/T3HarnessManager.test.ts src/renderer/settings/SettingsWindow.sidebar.test.tsx
  • npx eslint src/main/t3Agent/T3HarnessManager.ts src/renderer/settings/T3RemoteAccess.tsx
  • npm run build
  • Bundled t3 connect status --base-dir <isolated temp dir> smoke check

Full account authorization and a phone connection require a real T3 account and were not exercised in this environment.

@Anton-Horn
Anton-Horn force-pushed the feat/t3-remote-access branch from 9543b9f to 1299b84 Compare September 24, 2026 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant