pingdotgg / pingdotgg/t3code

[Bug]: Hook audits for codex don't block threads

Open
#5,024 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs-triage
Dominant language
TypeScript
Stars
23k
Forks
5.9k
Avg merge
11h 14m
Merged PRs (30d)
357

Description

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/desktop

Steps to reproduce

1: create a new hook in codex
2: start a thread in t3 chat
3: observe that the thread starts without the hook firing (this is because for new hooks in the codex tui you need to sign off on them in the tui)

Expected behavior

either a workflow to audit the new hooks appears or the hooks are auto approved, or the new thread isn't allowed to run until hooks are approved.

Actual behavior

Thread starts without any of the hooks present.

Impact

Major degradation or frequent failure

Version or commit

main @ 3513fa0

Environment

Ubuntu 24

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

Manually approve the hooks by sshing in and running codex (in every project, on every machine...) (or make a custom slop commit)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in apps/desktop by reproducing the issue: create a Codex hook, then start a thread in t3 chat and observe whether the hook is audited or approved. Trace the hook approval flow and thread-start path; done means a new thread cannot bypass hook approval, or the hooks are automatically approved or audited as specified by the implemented workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.