adk-code-mode 0.2.0__tar.gz → 0.2.1__tar.gz

adk_code_mode-0.2.1/.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+    ".": "0.2.1"
+}

{adk_code_mode-0.2.0 → adk_code_mode-0.2.1}/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## [0.2.1](https://github.com/a2anet/adk-code-mode/compare/adk-code-mode-v0.2.0...adk-code-mode-v0.2.1) (2026-05-05)
+
+
+### Bug Fixes
+
+* rename `<tools>` tag to `<code-mode>` and update `CODE_MODE_SYSTEM_INSTRUCTION` ([0a06bfb](https://github.com/a2anet/adk-code-mode/commit/0a06bfbdf22db6e0226e477d0ed074a6cc4d1515))
+
+
+### Documentation
+
+* update `README.md` with deployment instructions ([1dd7a95](https://github.com/a2anet/adk-code-mode/commit/1dd7a95197fd56231ba97182526a825baf18508a))
+
 ## [0.2.0](https://github.com/a2anet/adk-code-mode/compare/adk-code-mode-v0.1.0...adk-code-mode-v0.2.0) (2026-05-03)
 
 

{adk_code_mode-0.2.0 → adk_code_mode-0.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: adk-code-mode
-Version: 0.2.0
+Version: 0.2.1
 Summary: A "Code Mode" Code Executor for ADK for agents to interact with tools, files, and custom packages with Python
 Project-URL: Documentation, https://github.com/A2ANet/adk-code-mode#readme
 Project-URL: Issues, https://github.com/A2ANet/adk-code-mode/issues
@@ -78,12 +78,17 @@ Requires Python 3.10+. Local development requires [Docker](https://docs.docker.c
 
 ## 🚀 Usage
 
-Build a `CodeModeCodeExecutor`, wire `code_mode_before_model_callback` into the agent, and put `CODE_MODE_SYSTEM_INSTRUCTION` in the agent's `instruction`. The callback injects the tool catalog into the system prompt — skip it and the model has no idea what tools exist.
+Build a `CodeModeCodeExecutor`, then wire three things into the agent:
+
+- **`CODE_MODE_SYSTEM_INSTRUCTION`** — append to the agent's `instruction`. Teaches the model how to write code blocks and use artifacts.
+- **`code_mode_before_model_callback`** — set as `before_model_callback`. Injects the tool catalog (`<code-mode>` block) into the system prompt on every model turn.
+- **`generate_content_config`** with `function_calling_config.mode="NONE"` — disables native function calling so the model writes Python instead of attempting tool calls that fail with `MALFORMED_FUNCTION_CALL` (since `tools=[]`).
 
 ### Production (remote sandbox)
 
 ```python
 from google.adk.agents import LlmAgent
+from google.genai import types as genai_types
 from adk_code_mode import (
     CODE_MODE_SYSTEM_INSTRUCTION,
     CodeModeCodeExecutor,
@@ -105,6 +110,11 @@ root_agent = LlmAgent(
     instruction=f"You are a helpful assistant.\n\n{CODE_MODE_SYSTEM_INSTRUCTION}",
     tools=[],  # do NOT also bind tools here; the executor owns them.
     code_executor=executor,
+    generate_content_config=genai_types.GenerateContentConfig(
+        tool_config=genai_types.ToolConfig(
+            function_calling_config=genai_types.FunctionCallingConfig(mode="NONE"),
+        ),
+    ),
     before_model_callback=code_mode_before_model_callback(executor),
 )
 ```
@@ -153,10 +163,10 @@ Setting `ADK_CODE_MODE_CONTROL_HTTP=1` activates HTTP mode. The container:
 ```bash
 # Push the sandbox image to Artifact Registry
 gcloud auth configure-docker <region>-docker.pkg.dev
-docker pull ghcr.io/a2anet/adk-code-mode:latest
+docker pull --platform linux/amd64 ghcr.io/a2anet/adk-code-mode:latest
 docker tag  ghcr.io/a2anet/adk-code-mode:latest \
-    <region>-docker.pkg.dev/<project>/adk-code-mode/sandbox:latest
-docker push <region>-docker.pkg.dev/<project>/adk-code-mode/sandbox:latest
+    <region>-docker.pkg.dev/<project>/<repository>/adk-code-mode-sandbox:latest
+docker push <region>-docker.pkg.dev/<project>/<repository>/adk-code-mode-sandbox:latest
 
 # Create a VPC connector with no egress routes (blocks outbound network from sandbox)
 gcloud compute networks create adk-sandbox-vpc --subnet-mode=custom
@@ -176,16 +186,17 @@ gcloud compute networks vpc-access connectors create adk-sandbox-connector \
 
 # Deploy — note --concurrency 1 and --vpc-egress=all-traffic
 gcloud run deploy adk-code-mode-sandbox \
-    --image <region>-docker.pkg.dev/<project>/adk-code-mode/sandbox:latest \
+    --image <region>-docker.pkg.dev/<project>/<repository>/adk-code-mode-sandbox:latest \
     --region <region> \
     --port 8080 \
     --cpu 1 \
     --memory 1Gi \
     --concurrency 1 \
-    --no-allow-unauthenticated \
+    --allow-unauthenticated \
     --vpc-connector=adk-sandbox-connector \
     --vpc-egress=all-traffic \
-    --set-env-vars "ADK_CODE_MODE_CONTROL_HTTP=1,ADK_CODE_MODE_AUTH_TOKEN=<your-secret>"
+    --set-env-vars "ADK_CODE_MODE_CONTROL_HTTP=1" \
+    --set-secrets "ADK_CODE_MODE_AUTH_TOKEN=<your-secret-name>:latest"
 ```
 
 Then in your agent:
@@ -328,12 +339,41 @@ The only things crossing the boundary are: code, tool call arguments, tool retur
 
 ### What the model sees
 
-Your `instruction` (containing `CODE_MODE_SYSTEM_INSTRUCTION`) followed by a `<tools>` block appended by the callback:
+Your `instruction` (containing `CODE_MODE_SYSTEM_INSTRUCTION`) followed by a `<code-mode>` block appended by the callback:
 
 ```
 …your instruction…
 
-<tools>
+# How to execute code and use tools
+Code you write in a fenced Python block (i.e. ```python) will be executed in a sandbox.
+The Python Standard Library and a custom set of tools are available to you.
+To see the result of your code, you need to print it.
+
+For example, if you had the following tool:
+
+```
+from tools.slack import send_message
+
+def send_message(*, channel: str, text: str, thread_ts: str | None = ...) -> Any:
+    """Send a message to a Slack channel."""
+    ...
+```
+
+To call the tool, you should write:
+
+"""
+```python
+from tools.slack import send_message
+
+print(send_message(channel="C123", text="hi"))
+```
+"""
+
+# How to use files and variables in between executions
+Code is executed in a new environment each time.
+To list available Artifacts, use the `list_artifacts` tool. To save an Artifact, use the `save_artifact` tool, and to load an Artifact, use the `load_artifact` tool.
+
+<code-mode>
 
 # tools.slack
 
@@ -352,7 +392,20 @@ def send_message(*, channel: str, text: str, thread_ts: str | None = ...) -> Any
 from tools import save_artifact, load_artifact, list_artifacts
 …
 
-</tools>
+</code-mode>
+```
+
+When the rendered catalog exceeds `max_catalog_chars`, the per-tool sections are replaced with:
+
+```
+<code-mode>
+A `tools` package is available in the sandbox. List `/tools/` with
+`pathlib.Path('/tools').iterdir()`. Each entry is either a `.py` file
+(a top-level tool, importable as `from tools import <name>`) or a
+subdirectory (a namespace, with tools importable as
+`from tools.<namespace> import <name>`). To see a tool's signature and
+docstring, read its `.py` file with `open(...).read()`.
+</code-mode>
 ```
 
 Text and JSON-like MIME types travel as plain strings in artifact tools; binary content is base64-encoded. `load_artifact` returns `{"kind": "text" | "bytes", "data": str, "mime_type": str | None}`.

{adk_code_mode-0.2.0 → adk_code_mode-0.2.1}/README.md

@@ -51,12 +51,17 @@ Requires Python 3.10+. Local development requires [Docker](https://docs.docker.c
 
 ## 🚀 Usage
 
-Build a `CodeModeCodeExecutor`, wire `code_mode_before_model_callback` into the agent, and put `CODE_MODE_SYSTEM_INSTRUCTION` in the agent's `instruction`. The callback injects the tool catalog into the system prompt — skip it and the model has no idea what tools exist.
+Build a `CodeModeCodeExecutor`, then wire three things into the agent:
+
+- **`CODE_MODE_SYSTEM_INSTRUCTION`** — append to the agent's `instruction`. Teaches the model how to write code blocks and use artifacts.
+- **`code_mode_before_model_callback`** — set as `before_model_callback`. Injects the tool catalog (`<code-mode>` block) into the system prompt on every model turn.
+- **`generate_content_config`** with `function_calling_config.mode="NONE"` — disables native function calling so the model writes Python instead of attempting tool calls that fail with `MALFORMED_FUNCTION_CALL` (since `tools=[]`).
 
 ### Production (remote sandbox)
 
 ```python
 from google.adk.agents import LlmAgent
+from google.genai import types as genai_types
 from adk_code_mode import (
     CODE_MODE_SYSTEM_INSTRUCTION,
     CodeModeCodeExecutor,
@@ -78,6 +83,11 @@ root_agent = LlmAgent(
     instruction=f"You are a helpful assistant.\n\n{CODE_MODE_SYSTEM_INSTRUCTION}",
     tools=[],  # do NOT also bind tools here; the executor owns them.
     code_executor=executor,
+    generate_content_config=genai_types.GenerateContentConfig(
+        tool_config=genai_types.ToolConfig(
+            function_calling_config=genai_types.FunctionCallingConfig(mode="NONE"),
+        ),
+    ),
     before_model_callback=code_mode_before_model_callback(executor),
 )
 ```
@@ -126,10 +136,10 @@ Setting `ADK_CODE_MODE_CONTROL_HTTP=1` activates HTTP mode. The container:
 ```bash
 # Push the sandbox image to Artifact Registry
 gcloud auth configure-docker <region>-docker.pkg.dev
-docker pull ghcr.io/a2anet/adk-code-mode:latest
+docker pull --platform linux/amd64 ghcr.io/a2anet/adk-code-mode:latest
 docker tag  ghcr.io/a2anet/adk-code-mode:latest \
-    <region>-docker.pkg.dev/<project>/adk-code-mode/sandbox:latest
-docker push <region>-docker.pkg.dev/<project>/adk-code-mode/sandbox:latest
+    <region>-docker.pkg.dev/<project>/<repository>/adk-code-mode-sandbox:latest
+docker push <region>-docker.pkg.dev/<project>/<repository>/adk-code-mode-sandbox:latest
 
 # Create a VPC connector with no egress routes (blocks outbound network from sandbox)
 gcloud compute networks create adk-sandbox-vpc --subnet-mode=custom
@@ -149,16 +159,17 @@ gcloud compute networks vpc-access connectors create adk-sandbox-connector \
 
 # Deploy — note --concurrency 1 and --vpc-egress=all-traffic
 gcloud run deploy adk-code-mode-sandbox \
-    --image <region>-docker.pkg.dev/<project>/adk-code-mode/sandbox:latest \
+    --image <region>-docker.pkg.dev/<project>/<repository>/adk-code-mode-sandbox:latest \
     --region <region> \
     --port 8080 \
     --cpu 1 \
     --memory 1Gi \
     --concurrency 1 \
-    --no-allow-unauthenticated \
+    --allow-unauthenticated \
     --vpc-connector=adk-sandbox-connector \
     --vpc-egress=all-traffic \
-    --set-env-vars "ADK_CODE_MODE_CONTROL_HTTP=1,ADK_CODE_MODE_AUTH_TOKEN=<your-secret>"
+    --set-env-vars "ADK_CODE_MODE_CONTROL_HTTP=1" \
+    --set-secrets "ADK_CODE_MODE_AUTH_TOKEN=<your-secret-name>:latest"
 ```
 
 Then in your agent:
@@ -301,12 +312,41 @@ The only things crossing the boundary are: code, tool call arguments, tool retur
 
 ### What the model sees
 
-Your `instruction` (containing `CODE_MODE_SYSTEM_INSTRUCTION`) followed by a `<tools>` block appended by the callback:
+Your `instruction` (containing `CODE_MODE_SYSTEM_INSTRUCTION`) followed by a `<code-mode>` block appended by the callback:
 
 ```
 …your instruction…
 
-<tools>
+# How to execute code and use tools
+Code you write in a fenced Python block (i.e. ```python) will be executed in a sandbox.
+The Python Standard Library and a custom set of tools are available to you.
+To see the result of your code, you need to print it.
+
+For example, if you had the following tool:
+
+```
+from tools.slack import send_message
+
+def send_message(*, channel: str, text: str, thread_ts: str | None = ...) -> Any:
+    """Send a message to a Slack channel."""
+    ...
+```
+
+To call the tool, you should write:
+
+"""
+```python
+from tools.slack import send_message
+
+print(send_message(channel="C123", text="hi"))
+```
+"""
+
+# How to use files and variables in between executions
+Code is executed in a new environment each time.
+To list available Artifacts, use the `list_artifacts` tool. To save an Artifact, use the `save_artifact` tool, and to load an Artifact, use the `load_artifact` tool.
+
+<code-mode>
 
 # tools.slack
 
@@ -325,7 +365,20 @@ def send_message(*, channel: str, text: str, thread_ts: str | None = ...) -> Any
 from tools import save_artifact, load_artifact, list_artifacts
 …
 
-</tools>
+</code-mode>
+```
+
+When the rendered catalog exceeds `max_catalog_chars`, the per-tool sections are replaced with:
+
+```
+<code-mode>
+A `tools` package is available in the sandbox. List `/tools/` with
+`pathlib.Path('/tools').iterdir()`. Each entry is either a `.py` file
+(a top-level tool, importable as `from tools import <name>`) or a
+subdirectory (a namespace, with tools importable as
+`from tools.<namespace> import <name>`). To see a tool's signature and
+docstring, read its `.py` file with `open(...).read()`.
+</code-mode>
 ```
 
 Text and JSON-like MIME types travel as plain strings in artifact tools; binary content is base64-encoded. `load_artifact` returns `{"kind": "text" | "bytes", "data": str, "mime_type": str | None}`.

{adk_code_mode-0.2.0 → adk_code_mode-0.2.1}/sandbox-wheel/src/adk_code_mode_sandbox/__about__.py

@@ -1,4 +1,4 @@
 # SPDX-FileCopyrightText: 2025-present A2A Net <hello@a2anet.com>
 #
 # SPDX-License-Identifier: Apache-2.0
-__version__ = "0.2.0"  # x-release-please-version
+__version__ = "0.2.1"  # x-release-please-version

{adk_code_mode-0.2.0 → adk_code_mode-0.2.1}/src/adk_code_mode/__about__.py

@@ -1,4 +1,4 @@
 # SPDX-FileCopyrightText: 2025-present A2A Net <hello@a2anet.com>
 #
 # SPDX-License-Identifier: Apache-2.0
-__version__ = "0.2.0"  # x-release-please-version
+__version__ = "0.2.1"  # x-release-please-version

{adk_code_mode-0.2.0 → adk_code_mode-0.2.1}/src/adk_code_mode/callback.py

@@ -12,7 +12,7 @@ callback:
 2. Renders the catalog — signatures + docstrings for every tool —
    falling back to a short overflow message when the rendered catalog
    would exceed ``max_catalog_chars``.
-3. Appends ``\\n\\n<tools>\\n…\\n</tools>`` to
+3. Appends ``\\n\\n<code-mode>\\n…\\n</code-mode>`` to
    ``llm_request.config.system_instruction``.
 4. Caches the resolved tools on the executor so the follow-up
    ``execute_code`` call reuses them instead of re-resolving toolsets.
@@ -31,8 +31,8 @@ if TYPE_CHECKING:
 
 logger = logging.getLogger("adk_code_mode.callback")
 
-_TOOLS_OPEN = "<tools>"
-_TOOLS_CLOSE = "</tools>"
+_TOOLS_OPEN = "<code-mode>"
+_TOOLS_CLOSE = "</code-mode>"
 
 
 def code_mode_before_model_callback(

{adk_code_mode-0.2.0 → adk_code_mode-0.2.1}/src/adk_code_mode/executor.py

@@ -40,7 +40,7 @@ from pydantic import ConfigDict, Field, PrivateAttr
 
 from adk_code_mode._artifact_tools import ARTIFACT_TOOLS
 from adk_code_mode.output import truncate
-from adk_code_mode.runtime.base import SandboxResult, SandboxBackend, SandboxSession
+from adk_code_mode.runtime.base import SandboxBackend, SandboxResult, SandboxSession
 from adk_code_mode.runtime.protocol import (
     PROTOCOL_VERSION,
     DoneFrame,
@@ -68,10 +68,30 @@ CODE_MODE_SYSTEM_INSTRUCTION = """\
 # How to execute code and use tools
 Code you write in a fenced Python block (i.e. ```python) will be executed in a sandbox.
 The Python Standard Library and a custom set of tools are available to you.
-To see the result of your code, you need to print it. Don't make assumptions about the tool result format.
+To see the result of your code, you need to print it.
+
+For example, if you had the following tool:
+
+```
+from tools.slack import send_message
+
+def send_message(*, channel: str, text: str, thread_ts: str | None = ...) -> Any:
+    \"\"\"Send a message to a Slack channel.\"\"\"
+    ...
+```
+
+To call the tool, you should write:
+
+\"\"\"
+```python
+from tools.slack import send_message
+
+print(send_message(channel="C123", text="hi"))
+```
+\"\"\"
 
 # How to use files and variables in between executions
-Code is executed in a new environment each time. Tool results are automatically saved as Artifacts.
+Code is executed in a new environment each time.
 To list available Artifacts, use the `list_artifacts` tool. To save an Artifact, use the `save_artifact` tool, and to load an Artifact, use the `load_artifact` tool.
 """
 

{adk_code_mode-0.2.0 → adk_code_mode-0.2.1}/tests/test_agent_with_fake_llm.py

@@ -172,7 +172,7 @@ async def test_agent_runs_code_block_through_executor() -> None:
     else:
         rendered = "\n".join(p for p in system_instruction if isinstance(p, str))
     assert CODE_MODE_SYSTEM_INSTRUCTION.split("\n", 1)[0] in rendered
-    assert "<tools>" in rendered and "</tools>" in rendered
+    assert "<code-mode>" in rendered and "</code-mode>" in rendered
     assert "def echo" in rendered
 
 

{adk_code_mode-0.2.0 → adk_code_mode-0.2.1}/tests/test_callback.py

@@ -57,8 +57,8 @@ async def test_callback_appends_block_when_system_instruction_is_none() -> None:
 
     instruction = request.config.system_instruction
     assert isinstance(instruction, str)
-    assert instruction.startswith("<tools>")
-    assert instruction.rstrip().endswith("</tools>")
+    assert instruction.startswith("<code-mode>")
+    assert instruction.rstrip().endswith("</code-mode>")
     assert "def ping" in instruction
 
 
@@ -73,8 +73,8 @@ async def test_callback_appends_block_to_string_system_instruction() -> None:
     instruction = request.config.system_instruction
     assert isinstance(instruction, str)
     assert instruction.startswith("You are an assistant.")
-    assert "<tools>" in instruction
-    assert instruction.rstrip().endswith("</tools>")
+    assert "<code-mode>" in instruction
+    assert instruction.rstrip().endswith("</code-mode>")
 
 
 @pytest.mark.asyncio
@@ -88,8 +88,8 @@ async def test_callback_appends_block_to_list_system_instruction() -> None:
     instruction = request.config.system_instruction
     assert isinstance(instruction, list)
     assert instruction[:2] == ["First part.", "Second part."]
-    assert instruction[-1].startswith("<tools>")
-    assert instruction[-1].rstrip().endswith("</tools>")
+    assert instruction[-1].startswith("<code-mode>")
+    assert instruction[-1].rstrip().endswith("</code-mode>")
 
 
 @pytest.mark.asyncio

adk_code_mode-0.2.0/.release-please-manifest.json

@@ -1,3 +0,0 @@
-{
-    ".": "0.2.0"
-}