Track Go runtime parity gaps

[supreme-gg-gg]

Summary

This issue tracks user-facing differences between Go and Python runtimes. Solutions to the following issues can either be enhanced documentation or feature additions to the Go runtime. Please comment below if any more differences are found when you are using the Go runtime.

Action Items

• Tighten embedding model compatibility for Go runtime.
  Python memory embeddings support openai, azure_openai, ollama, gemini/Vertex AI, and bedrock. Go currently supports only openai and azure_openai, even though translated embedding configs can point at other providers. Either validation or additional support could work here. Python embedding models also can use a refactor to move them out from _memory_service.py.

• Clarify or fix Bedrock model support in Go runtime.
  Python Bedrock uses the Bedrock Converse API and supports Bedrock model families broadly. Go currently routes Bedrock through the Anthropic Bedrock client, so Bedrock is effectively Anthropic-only today.

• Implement apiKeyPassthrough in the Go runtime.
  Users can enable it today, but Go does not currently apply it to LLM clients.

• Apply model TLS settings in the Go runtime.
  ModelConfig TLS fields are translated, but Go does not currently honor them when creating model clients.

• Honor ollama.options in the Go runtime.
  Python uses them; Go currently ignores them. A solution would be to use Ollama SDK if available.

• Decide whether context compaction is a must-fix or a documented Go limitation.

• Decide whether memory auto-save parity is required.
  Python auto-saves periodically; Go currently relies more on explicit save_memory tool usage.

• Decide whether skills sandboxing parity is required.
  Python uses srt; Go currently executes skills shell commands directly.

[jsonmp-k8]

Regarding the skills sandboxing item (marked as resolved with the note "moving away from SRT"):

SRT is still actively used in both Python and Go runtimes:

• Python: sandbox_code_executer.py, shell.py, and bash_tool.py all invoke srt for command execution
• Go: go/adk/pkg/skills/shell.go runs commands via srt bash -c with settings from KAGENT_SRT_SETTINGS_PATH
• Dockerfiles: Both python/Dockerfile and go/Dockerfile.full install SRT from anthropic-experimental/sandbox-runtime

SRT hasn't been removed — it's still a core dependency for sandboxing shell commands in both runtimes. Should this item remain checked, or should it be reopened until SRT is actually removed (or a decision is documented)?

[supreme-gg-gg]

Yes you're correct, that statement was invalid and I'll remove it. But in fact it was marked resolved because we've already added SRT support to Go runtime and Skills (with network allowlist configuration) in #1648 I haven't got a chance to test it myself but seems like we've got Python parity with skills & shell sandbox