feat: graphify support (auto-install /graphify in compatible agents) - #30
Merged
Conversation
Contributor
Merging this branch will not change overall coverage
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. |
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.
Adds graphify support, modeled on RTK: a global
Settings.Graphifytoggle that, when enabled, auto-installs the/graphifyknowledge-graph skill into compatible agents — and removes it when disabled.How it works
Settings.Graphify(config + setup-wizard checkbox "Graphify knowledge graph").--build-arg INSTALL_GRAPHIFY→Dockerfile.baseinstalls thegraphifyypip package (CLIgraphify) globally. Toggling requires a rebuild (same model as RTK; confirmed acceptable).run.gopasses-e EXITBOX_GRAPHIFY=true. New entrypointsetup_graphifyruns afterapply_active_workspace_links/link_skills:graphify install --platform <agent>(registers/graphifyinto the agent's persisted skill dir).…/skills/graphify/dir (file-based, so it works after a rebuild drops the CLI).Compatible agents
claude, codex, opencode, copilot, pi — graphify's skill destination matches ExitBox's config layout for these (verified against graphify's
_PLATFORM_CONFIG).Excluded (intentionally, with reason):
kimiplatform writes~/.kimi/, but ExitBox's Kimi Code uses~/.kimi-code/(skill would never be read)..cursor/rules in the repo), not a global skill.Tests
setup_graphifyentrypoint test: install for a compatible agent, removal when disabled, skip for an incompatible agent.go build,go test ./...,go vet,golangci-lintgreen; entrypoint suite 112 pass / 2 pre-existing failures (codex session-storage env leak, unrelated).Note: build-time + entrypoint changes require an image rebuild to take effect.