feat(config): split AgentV home and data directories#1278
Merged
Conversation
Deploying agentv with
|
| Latest commit: |
db5d503
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://26b35b30.agentv.pages.dev |
| Branch Preview URL: | https://session-age-8.agentv.pages.dev |
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.
Summary
AgentV can now use a shared home/global
config.yamlwithout forcing every project to carry.agentv/config.yaml. Project-local YAML config still wins, and the implementation deliberately avoids merge semantics: AgentV uses the first valid project-local file, then falls back to$AGENTV_HOME/config.yamlor~/.agentv/config.yaml.AgentV home/config files and heavy runtime data can now be mounted separately.
AGENTV_HOMEcontrols lightweight config/home files, whileAGENTV_DATA_DIRcontrols workspaces, subagents, trace state, dependency caches, and results clones; whenAGENTV_DATA_DIRis unset, heavy data still falls back toAGENTV_HOME/~/.agentvfor existing users.Docker docs and compose defaults now show separate
HOME,AGENTV_HOME, andAGENTV_DATA_DIRmounts.Before / After Evidence
origin/mainonly searched project-local.agentv/config.yaml;$AGENTV_HOME/config.yamlwas not consulted.AGENTV_HOME=<tmp>/home agentv eval run suite.eval.yaml --dry-run --stricthonors a homerequired_versionand aborts with the expected strict-version warning.origin/mainkept config at~/.agentvregardless ofAGENTV_HOME, and heavy helpers only followedAGENTV_HOME.AGENTV_HOME=/tmp/agentv-config AGENTV_DATA_DIR=/tmp/agentv-dataresolves config to/tmp/agentv-configand workspaces to/tmp/agentv-data/workspaces.Green UAT output:
Verification
bun test packages/core/test/paths.test.ts packages/core/test/evaluation/loaders/config-loader.test.tsbun test packages/core/test/evaluation/results-repo.test.tsbun test apps/cli/test/commands/results/serve.test.tsbun run buildbun run typecheckdocker compose -f docker-compose.yml configgit push: build, typecheck, lint, test, validate eval YAML files