Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Send Data that is not an object as `data`, so instructions never fail the step. - Tell users what to do on a 410 or 429, and to set the task's replay key. - Offer T3 Code to generated workflows through the built-in step allowlist. - Log only the hostname when a fetch connection resets, so a token in the URL stays out of logs. - Mark Beta steps on the catalog node instead of a separate template id list. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A workflow saved through the API or MCP gets no default for an optional input, so the step sent only the instructions. The agent docs now also cover the 410 reply, keeping the result with output_variable, and what turning the flag off stops. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A T3 Code step runs on its owner's T3 Code account. Only the workflow's owner, an org admin, or someone the owner shares it with as an editor can now change a workflow with a T3 Code step, live-test it, or start runs by hand. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The T3 Code step can now set itself up from a T3 Code connection in MCP servers settings. The member picks a machine and a project, and PostHog creates a T3 Code task there that starts a new thread for each run, then fills in the step's webhook URL. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…o feat/t3-code-thread-picker
…r write paths Turning a T3 Code workflow off stays open to every editor. Publishing a draft, restoring a revision and approving a suggestion now need the owner or someone they share it with. A transactional email workflow refuses a T3 Code step, because every send would start a run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
T3 Code creates a task only in a project with a default model. The setup panel now says so when no project on the machine has one, and says when the step already sends its runs to a task. The workflow building docs point agents to the in-app setup. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
Contributor
Author
|
Note 🤖 Claude Opus 5.5 responding on behalf of Michael Decisions for this PR:
|
A teammate's save or canvas enable that raced the owner adding a T3 Code step passed the check on the read state. Both writes now repeat the check on the locked row. The bytecode refresh command also crashed on workflows without a creator, because the check read the user of its bare request. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A late reply for a machine or project the member left no longer replaces the projects or sets the step's webhook URL. - A failed project load offers "Try again", and a machine retry clears its old error. - Only a signed-in member can use the T3 Code setup endpoints, so an API token cannot answer its own approval. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…flow Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…er left - A late failure for a machine or project the member left no longer clears the current projects or shows the old error. - The machine and project pickers wait while the task is created. - The 403 for API keys says that only a signed-in member can set up the step. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…o feat/t3-code-thread-picker
The previous check called the unenforced most-specific resolver, which the repo guard forbids, and in legacy resolution a teammate with an object-wide viewer rule and a resource-wide editor rule could act for the owner. The check now uses the enforced methods, and a share must name a member or role. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…content A teammate could restore a revision or approve a suggestion that stages a T3 Code step on a workflow without one, and both checks ran before the row lock. The early check now covers the staged actions, and both services check the locked workflow again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…th a t3 code step Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…o feat/t3-code-thread-picker
…trol is off Without the access control feature, the legacy resolver returned the default editor level before it applied specific_only, so every member counted as shared. Only explicit member or role rules count now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…o feat/t3-code-thread-picker
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…workflows Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…o feat/t3-code-thread-picker # Conflicts: # products/workflows/skills/building-workflows/references/graph-schema.md
The T3 Code step now sends a webhook-id header that stays the same across retries, and no longer sends x-posthog-delivery-id. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Silthus
added
posthog-review
hogbox-preview
Contributor
Author
|
Moved to #127139, a branch in PostHog/posthog, so it can run CI. The commits and the decisions comment moved with it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Impact: Grow Workflows: faster setup of the T3 Code step.
Warning
🟡 Merge risk: medium · two-way door (merge-risk rubric)
workflow-t3-code-stepflag, signed-in members only, approval per call, stale replies dropped.Changes
mcp_storefacade function, the skill reference.How did you test this code?
Test rationale: API tests with real MCP installations and a faked T3 Code catch leaked connections, self-approving API keys and hidden errors. Logic tests catch a late reply that sets the URL for a machine the member left.
Release status
Docs update
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Agent: Claude Code, Claude Opus 5.5
Skills:
/improving-drf-endpoints,/writing-tests,/writing-ui-components,/writing-pr-descriptionsMore context for AI agents
t3_project_list,schedule_task), not a new integrationInvolvement: design pass by GPT-6.1 Sol; qa-swarm panel rounds 1 (7 lenses) and 2 (6 lenses) with GPT-6.1 Sol and Claude Opus 5.5; five final reads; live run captured, plus a replay-key run at 4492b78.
schedule_task(fix(server): scheduled tasks created over MCP can set their model and effort pingdotgg/t3code#23566) would lift the default-model limit.workflow_t3_code.pyand the approval flow int3CodeTaskSetupLogic.ts.🤖 Generated with Claude Code