Skip to content

Closed: local development setup - #6251

Closed
andresdjasso wants to merge 0 commit into
stagingfrom
chore/codex-sim-project-routing
Closed

Closed: local development setup#6251
andresdjasso wants to merge 0 commit into
stagingfrom
chore/codex-sim-project-routing

Conversation

@andresdjasso

@andresdjasso andresdjasso commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Closed without repository changes. This setup remains local to the developer environment.

@vercel

vercel Bot commented Aug 4, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Building Building Preview Aug 4, 2026 5:35pm

Request Review

@cursor

cursor Bot commented Aug 4, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
No files were modified, so there is no deployment or runtime risk from this PR.

Overview
No code changes are included in this pull request—the diff is empty.

The work was closed without merging; any local development setup stays on the developer machine and was not added to the repository.

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

@andresdjasso andresdjasso changed the title chore(codex): isolate Sim project connectors Closed: local development setup Aug 4, 2026
@andresdjasso
andresdjasso force-pushed the chore/codex-sim-project-routing branch from c580322 to 9b9da81 Compare August 4, 2026 17:38
@andresdjasso
andresdjasso deleted the chore/codex-sim-project-routing branch August 4, 2026 17:38
@greptile-apps

greptile-apps Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

The PR isolates Codex access to Sim-specific Linear and Slack connectors and adds repository-level routing and worktree instructions.

  • Disables generic Linear and Tenor MCP access and suppresses Tenor suggestions.
  • Requires the dedicated Sim connector entries.
  • Adds external-workspace identity checks and mandates task-specific worktrees.

Confidence Score: 4/5

The worktree path must be excluded from Git before merging so the required isolation workflow does not dirty the originating checkout or expose nested files to staging.

The instructions mandate creating a full checkout under .worktrees/, but the repository ignores only .claude/worktrees/, leaving the newly required directory visible as untracked repository content.

Files Needing Attention: AGENTS.md and .gitignore

Important Files Changed

Filename Overview
.codex/config.toml Adds project-specific MCP routing, disables generic connectors, and marks the isolated Sim connectors as required.
AGENTS.md Adds connector identity and worktree-isolation guidance, but the mandated .worktrees/ location is not ignored by Git.

Reviews (1): Last reviewed commit: c580322 | Re-trigger Greptile

Comment thread AGENTS.md Outdated
### Isolated implementation work

- Do not implement a new task in a dirty, detached, shared, or unrelated worktree.
- Before code changes, inspect `git status` and `git worktree list`. If the task is not already in its own clean worktree, fetch `origin/staging`, create a task-specific branch from `origin/staging`, and add a dedicated worktree under `.worktrees/<issue-id>-<slug>`.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Worktree directory remains tracked

When an agent follows this instruction, the complete checkout created under .worktrees/<issue-id>-<slug> remains visible as untracked content because .gitignore excludes only .claude/worktrees/, causing clean-tree checks to fail and unrestricted staging to include files from the nested checkout.

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