Repository navigation
Conversation
Connect canonical workflows with verified examples, access boundaries and a paired evaluation procedure so platform builders can find and check the answers. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Document the existing cache and access metadata contracts in the API sources, generated references and agent examples. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Validate the guide together with current contribution and translation sources. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Check caller and run-history guidance with the agent integration documentation. Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
This branch has not been deployed
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.
Changelog category (leave one):
Changelog entry
Not required for documentation.
Why
Agents need a direct path from integration and repository questions to valid requests, access outcomes and provider diagnostics. Canonical guides connect those workflows with explicit evaluation and release boundaries.
Scope and risk
Adds an agent-platform guide and links it from the documentation and generated agent indexes. Extends repository Q&A, linked-memory, evaluation and repository-access guides with concrete examples, observable outcomes and limitations. The proposed paired evaluation records actual tool use, objective task outcomes, total cost and latency without claiming a measured benefit. Customer delivery guidance distinguishes technical integration from support and commercial agreements.
Corrects operation descriptions at their source and regenerates the affected references and SDK comments. Uncached retrieval-only requests need both
synthesize: falseandno_cache: true. Repository listings can include permitted request-only metadata withreadable: false; that metadata grants no code reads. Namespace authorization, indexed-source freshness and asynchronous memory-link boundaries remain explicit.Adds a native-provider setup recipe, corrects embedding-provider selection and dimension descriptions, and makes proxy provider and model selection explicit. Dashboard guidance distinguishes displayed jobs from the conflict resolver's separate setting. The health checklist distinguishes configured fakes, passive process-local outcomes and actual inference, including compatible-embedding coverage limits.
Compatibility, rollout and rollback
Tests
AI assistance in the code (leave one; writing this description with AI is fine):
AI-generated: Codex wrote the documentation; operation contracts, SDK interfaces and provider behavior were checked against implementation source.
I can explain every line of this diff and how it interacts with the rest of Loom.
Checklist
make format-check,make lint,make typecheckandmake test-unitpass; the integration suite passes if server behaviour changed.