Align docs, examples, the setup wizard, and telemetry tests with the
current Doubao multimodal embedding model so generated configs keep
referencing the supported default consistently.
* docs: fix docker deployment
* reorg: remove third_party/agfs
* feat(s3fs): add disable_batch_delete option for OSS compatibility
Port of PR #1333 from Go version to Rust:
- Add disable_batch_delete config option to S3Client
- When enabled, use sequential single-object deletes instead of DeleteObjects
- This is for S3-compatible services like Alibaba Cloud OSS that require
Content-MD5 for DeleteObjects but AWS SDK v2 does not send it by default
- Add documentation and config example for OSS
* fix(s3fs): pass disable_batch_delete config from Python to Rust
Add disable_batch_delete to the s3_plugin_config dict in _generate_plugin_config
so that the Python config can properly control the Rust S3FS plugin's behavior.
* reorg: remove third_party/agfs
* reorg: remove third_party/agfs
* change some docs
* change some docs
---------
Co-authored-by: openviking <openviking@example.com>
* fix(resource): resolve 'file exists' errors on resource add
Two bugs caused mv to fail with "file exists" during add_resource:
1. When `to` URI has a trailing slash, parent_uri was computed as the
target directory itself instead of its parent. mkdir then created
the exact path that mv was about to rename into.
2. _resolve_unique_uri in Phase 3.5 ran outside bind_request_context,
so stat checked the default account path instead of the actual
account. On repeated adds it failed to detect the existing resource
and returned the original URI, causing mv to collide.
Also pass ctx to viking_fs calls in index_resource that were missing it.
* Update GUIDE.md
---------
Co-authored-by: qin-ctx <qinhaojie.exe@bytedance.com>
* feat: define a system path for future deployment
* feat: define a system path for future deployment
* fix: golang downgrade to 1.19
* fix: golang downgrade to 1.19, and change doc
* docs: change model recommendation
* fix: golang downgrade to 1.19, and change doc
* fix: mv test files
* fix: loguru
---------
Co-authored-by: openviking <openviking@example.com>
- Python HTTP client reads `timeout` from ovcli.conf when using default value,
with priority: SDK explicit param > ovcli.conf > default 60.0
- Rust CLI: replace unused `user` field with `agent_id`, send X-OpenViking-Agent
header to align with Python client behavior
- Rust CLI: read `timeout` from ovcli.conf and pass to reqwest client
- Move timeout documentation from configuration guide to API overview
- Update examples and ovcli.conf.example with timeout field
Closes#306
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
MaojiaSheng