Add the Kotlin tab for driving a long-running tool to completion - #2159
Open
happyhuman wants to merge 1 commit into
Open
Add the Kotlin tab for driving a long-running tool to completion#2159happyhuman wants to merge 1 commit into
happyhuman wants to merge 1 commit into
Conversation
The call_reimbursement_tool group showed Python, TypeScript, Go and Java but not Kotlin, even though the page already carries a Kotlin tab for defining the tool a few sections earlier. Defining a long-running tool without showing how to resume it leaves the Kotlin reader at the point where the invocation pauses. The new region extends the file that already backs this page rather than adding a second one. It mirrors the Python flow: watch for the call whose id appears in Event.longRunningToolIds, keep the matching FunctionResponse, then send a copy of it back with the final status to resume the paused invocation. Scoped deliberately to that group. RequestInputTool and GetUserChoiceTool were also on this backlog row, but they have no host page in ANY language - they appear nowhere in the narrative docs, only in generated API reference - so adding a Kotlin-only section for them would invent structure rather than close a gap. Recorded for a product-docs request instead.
✅ Deploy Preview for adk-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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.
What
Adds the missing Kotlin tab to the
call_reimbursement_toolgroup ondocs/tools-custom/function-tools.md, via a newcall_reimbursement_toolregion in theLongRunningTool.ktfile that already backs this page.Why
The page already has a Kotlin tab for defining a long-running tool (
@Tool(isLongRunning = true)), but none for resuming one. That leaves the Kotlin reader exactly at the point where the invocation pauses, with no shown way forward — while Python, TypeScript, Go and Java all continue.The Kotlin flow mirrors Python's: find the call whose id the event lists in
Event.longRunningToolIds, hold on to the matchingFunctionResponse, then send a copy back with the final status to resume.Scope: half this backlog row is deliberately not here
The row also named
RequestInputToolandGetUserChoiceTool. I did not document them, because they have no host page in any language:docs/**.mdpage — only in generated API reference, plus incidental mentions (docs/agents/config.mdname list, BigQuery analytics event names).docs/graphs/human-input.mdis the graphs subsystem, which Kotlin does not have, so it is the wrong home — as the backlog itself noted.Adding a Kotlin-only section would invent page structure rather than close a Kotlin gap, so this is Kotlin being level with the other SDKs, not behind. Recorded for a product-docs request instead.
Verification
Grounded against the
v0.8.0git tag. Full ladder green (L0, L1 compile with KSP, L2 ktlint, L3, L5, L6). L4runSnippetsreports SKIP — no such Gradle task exists in this repo.Tracked as KT-26.