From 01d1c15d917bb8cc29ce18c10d7f62eace17afce Mon Sep 17 00:00:00 2001 From: Dave Date: Fri, 20 Mar 2026 09:16:27 +0000 Subject: [PATCH] story-kit: create 345_story_gemini_agent_backend_via_google_ai_api --- .../345_story_gemini_agent_backend_via_google_ai_api.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.story_kit/work/1_backlog/345_story_gemini_agent_backend_via_google_ai_api.md b/.story_kit/work/1_backlog/345_story_gemini_agent_backend_via_google_ai_api.md index 66c61d0..8c1d2fd 100644 --- a/.story_kit/work/1_backlog/345_story_gemini_agent_backend_via_google_ai_api.md +++ b/.story_kit/work/1_backlog/345_story_gemini_agent_backend_via_google_ai_api.md @@ -13,7 +13,8 @@ As a project owner, I want to run agents using Gemini (2.5 Pro, etc.) via the Go - [ ] Implement GeminiRuntime using the AgentRuntime trait from refactor 343 - [ ] Supports Gemini 2.5 Pro and other Gemini models via the Google AI generativeai API - [ ] Manages a conversation loop: send prompt + tool definitions, execute tool calls, continue until done -- [ ] Tool definitions map to the same tools agents currently use (file read/write, bash, grep, etc.) +- [ ] Agents connect to storkit's MCP server for all tool operations — no custom file/bash tools needed +- [ ] MCP tool definitions are converted to Gemini function calling format - [ ] Configurable in project.toml: runtime = 'gemini', model = 'gemini-2.5-pro' - [ ] GOOGLE_AI_API_KEY passed via environment variable - [ ] Token usage tracked and logged to token_usage.jsonl