sync-gbrain

To refresh gbrain search indexes, you can run a sync orchestration workflow that probes local worktree state, registers native code surfaces, and updates search guidance in CLAUDE.md. This ensures the gbrain index accurately reflects your current repo code and remains searchable.

Keeping agent search guidance current involves orchestrating a sync between local worktrees and CLAUDE.md. The process performs capability checks and surface registrations to produce a final verdict, ensuring agent search guidance aligns with the latest codebase changes.

Yes, the gbrain sync orchestration is fully idempotent and re-runnable. It safely re-executes in CI or local development environments without causing duplicate state, ensuring reproducible results across multiple sync operations.

The gbrain sync workflow operates as a standalone orchestration script with no external dependencies or additional component installations required. It runs natively within the local development environment and per-repo worktrees to manage indexing.

Your gbrain search index returns outdated results because the index has not been refreshed to reflect new code changes. Running the sync orchestrator updates local artifacts and agent search indices, bringing the index back in sync with your current worktree state.

You should trigger a gbrain re-indexing operation when you modify code in local worktrees and need updated search accuracy. It is designed to keep local artifacts and agent search indices up to date, making it ideal after significant codebase changes.