Automatically discover local T3 and manage credentials - #1
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![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: 8759aa7fb8
ℹ️ 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".
|
@codex review Fixed both findings in the latest commit: resolve CLI symlinks relative to the server cwd before validation, and continue using a valid credential when proactive renewal fails, with a five-minute retry delay. Regression tests cover absolute/relative symlinks, fallback requests, expiration, and recovery. All 26 tests and TypeScript checks pass. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c3b8aaccc6
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a2b7cecdf3
ℹ️ 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".
1 participant
The first
watchorlist {threads:true}call now discovers an installed local T3 instance and creates a verified credential. Standard local installations only need the MCP launch entry; the three tools stay unchanged.Managed credentials are replaced on use within one day of expiration, including from the detached worker. A SQLite lease coordinates simultaneous callers, replacement files are private and atomic, and failed issuance or verification preserves the previous token. Proactive renewal failures continue using a still-valid token with a five-minute retry delay. Explicit token files remain user-managed. Multiple discovered instances require a
T3POLL_BASE_DIRor URL selection.Validation: 28 tests pass, TypeScript check passes, and the packed artifact includes the setup module. An isolated copy of T3
0.0.41-nightly.20260910.1507verified configuration-free MCP connection, initial issuance, worker renewal during delivery, and reuse from a fresh CLI process with a scripted provider.Automatic discovery currently supports Linux and installed T3 Node CLI processes, including package-manager symlinks, with the
userdatalayout. Source runners and olderdevlayouts retain manual overrides. T3's issuance CLI grants administrative scopes; t3poll only uses orchestration read/operate. Previous successfully used credentials expire naturally; failed verification revokes the new session, with persistent cleanup retry if needed. Documentation covers setup, renewal, selection, and these boundaries.The installed local build and live T3 server were not changed. No npm publication.