Docs: Clarify how the temp: namespace works #612
Draft
+27
−7
Conversation
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
![google-labs-jules[bot]](https://avatars.githubusercontent.com/in/842251?s=60&v=4){kind=small}
This commit clarifies the behavior of the `temp:` namespace in the documentation. The following changes were made: - Updated `docs/sessions/state.md` to provide a more detailed explanation of the `temp:` namespace. - Updated `docs/context/index.md` to improve the clarity of an example related to passing data between tools. - Updated `docs/runtime/index.md` to add a note about the scope of `temp:` variables. - Updated `docs/agents/multi-agents.md` and `docs/agents/workflow-agents/sequential-agents.md` to clarify how the `temp:` namespace is propagated to sub-agents. - Updated `docs/tools/function-tools.md` to explain how to use the `temp:` namespace to pass data between tool calls. fixes #160
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.
This PR clarifies the behavior of the
temp:namespace in the documentation, as requested in issue #160.