[codex] Integrate CodeGraph into issue workflows and modularize platform#1
Merged
Conversation
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.
What changed
@colbymchenry/codegraph@0.9.3CLI integration.data/codegraph/<owner>--<repo>/codegraph.db, restore it for later Issue sandboxes, and run upstreamcodegraph sync --quietinstead of rebuilding a new database.codegraph context --format jsonand injects the resulting graph/code context intoContextPackbefore planning and implementation.codegraph.queryandcodegraph.contextgateway tools, artifacts/events for graph creation and task context, and repository-level configuration withfail_on_error: true.JASON-QWeb/CodeZero, platform configuration, operator documentation, coverage support, and ignored local index/environment/build output.Why
An Issue-driven agent should not start planning or editing with only an ad hoc source scan, and it should not rebuild an unchanged repository graph for every Issue. CodeGraph's normal Git fast path sees working-tree changes but not a stale cache versus a new clean checkout, so the workflow now deliberately reconciles shared baseline caches by file hashes, keeps task-branch edits local, and supplies task-specific CodeGraph context to the agent for quicker navigation and better-scoped pull requests.
Validation
pnpm checkpassed: lint, typecheck, coverage test run, and production build.tests/codegraph-indexer.test.ts,tests/repo-navigation-graph.test.ts,tests/config-loading.test.ts,tests/issue-workflow.test.ts,tests/tool-gateway.test.ts).codegraph init ... --index, while the second restored the platform cache and invokedcodegraph sync ... --quiet..env, sandbox.codegraph/, platformdata/codegraph/, dependency directories, caches, build output, coverage output, and.DS_Storeremain ignored and are not part of the commit.