Repository navigation
Conversation
Author
|
@penberg please CR~ |
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
.agentfs/{id}.dbrelative to the current working directory instead of~/.agentfs/{id}.db.Motivation
The Rust, Python, and TypeScript SDKs, as well as the CLI and root documentation, consistently use
.agentfs/{id}.db.The Go SDK was the only implementation resolving ID-based databases under the user's home directory. As a result, the same agent ID could refer to different databases depending on which SDK was used.
Explicit paths supplied through
AgentFSOptions.Pathremain unchanged.Testing
go test ./...go vet ./...