Skip to content

Enable Entire for Codex - #50

Merged
jdx merged 1 commit into
mainfrom
codex/enable-entire-20260625141953
Jun 25, 2026
Merged

Enable Entire for Codex#50
jdx merged 1 commit into
mainfrom
codex/enable-entire-20260625141953

Conversation

@jdx

@jdx jdx commented Jun 25, 2026

Copy link
Copy Markdown
Owner

Summary

  • enable Entire project config
  • add Codex hooks and the Entire search subagent
  • keep local Entire runtime state ignored

Generated with entire enable --agent codex --no-init-repo.


Note

Low Risk
Adds agent/tooling configuration and optional external CLI hooks only; no changes to application runtime or auth/data paths in this repo.

Overview
Enables Entire in .entire/settings.json and adds .entire/.gitignore so local runtime artifacts (tmp/, logs/, metadata/, etc.) stay out of git.

Codex integration: .codex/config.toml turns on hooks, and .codex/hooks.json routes SessionStart, UserPromptSubmit, PostToolUse, and Stop to entire hooks codex … when the CLI is on PATH (otherwise hooks no-op; session start can emit an install hint).

New entire-search subagent (.codex/agents/entire-search.toml) is read-only and restricted to entire search --json for checkpoint/transcript history, with explicit guardrails against shell injection and ad-hoc grep/git log fallbacks.

Reviewed by Cursor Bugbot for commit ab54d01. Bugbot is set up for automated code reviews on this repo. Configure here.

@coderabbitai

coderabbitai Bot commented Jun 25, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@jdx, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 59 minutes and 57 seconds. Learn how PR review limits work.

To continue reviewing without waiting, enable usage-based billing in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 2fc54bb7-83c4-4437-8c05-d8e7d0ddce8c

📥 Commits

Reviewing files that changed from the base of the PR and between 95b86e3 and ab54d01.

📒 Files selected for processing (5)
  • .codex/agents/entire-search.toml
  • .codex/config.toml
  • .codex/hooks.json
  • .entire/.gitignore
  • .entire/settings.json

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Jun 25, 2026

Copy link
Copy Markdown

Greptile Summary

This PR wires up the Entire checkpoint/history tool for Codex by adding four lifecycle hooks, a read-only search subagent, and the minimal shared settings file. All files were generated by entire enable --agent codex --no-init-repo and require no manual editing.

  • .codex/hooks.json: Registers PostToolUse, SessionStart, Stop, and UserPromptSubmit hooks; each defensively skips execution when the entire binary is not on PATH, and the SessionStart fallback emits a correctly-escaped JSON systemMessage directing the user to install the CLI.
  • .codex/agents/entire-search.toml: Defines a read-only sandboxed subagent that exclusively uses entire search --json, with explicit prompt-injection mitigation and a clear failure mode.
  • .entire/: Adds the shared settings.json (enabled: true) and a .gitignore that excludes all local runtime state (tmp/, metadata/, logs/, redactors/local/, settings.local.json).

Confidence Score: 5/5

All changes are auto-generated tooling configuration with no modifications to production Ruby code.

Every changed file is a config or ignore file for the Entire integration. The hooks are purely additive, gracefully no-op when the CLI is absent, and touch no application logic. The .gitignore correctly excludes local runtime state. No concerns identified.

No files require special attention.

Important Files Changed

Filename Overview
.codex/hooks.json Adds four Codex lifecycle hooks (PostToolUse, SessionStart, Stop, UserPromptSubmit) that delegate to the entire CLI with a defensive install check; JSON escaping in the SessionStart fallback message is correct.
.codex/agents/entire-search.toml Declares a read-only search subagent scoped to entire search --json; includes prompt-injection mitigation and clear fallback behavior.
.codex/config.toml Minimal config that opts the repository into the Codex hooks feature.
.entire/.gitignore Ignores local Entire runtime directories (tmp/, metadata/, logs/, redactors/local/) and settings.local.json to prevent ephemeral state from being committed.
.entire/settings.json Minimal shared Entire settings file enabling the integration; intentionally sparse per the auto-generation note.

Reviews (1): Last reviewed commit: "Enable Entire for Codex" | Re-trigger Greptile

@jdx
jdx merged commit b686b5d into main Jun 25, 2026
11 checks passed
@jdx
jdx deleted the codex/enable-entire-20260625141953 branch June 25, 2026 19:33
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