tunacode-cli 0.0.55__py3-none-any.whl → 0.0.78.6__py3-none-any.whl

tunacode/tools/prompts/bash_prompt.xml

@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<tool_prompt>
+    <description>
+Executes a given bash command in a persistent shell session with optional timeout, ensuring proper handling and security measures.
+
+Before executing the command, please follow these steps:
+
+1. Directory Verification:
+   - If the command will create new directories or files, first use the LS tool to verify the parent directory exists and is the correct location
+   - For example, before running "mkdir foo/bar", first use LS to check that "foo" exists and is the intended parent directory
+
+2. Command Execution:
+   - Always quote file paths that contain spaces with double quotes (e.g., cd "path with spaces/file.txt")
+   - Examples of proper quoting:
+     - cd "/Users/name/My Documents" (correct)
+     - cd /Users/name/My Documents (incorrect - will fail)
+     - python "/path/with spaces/script.py" (correct)
+     - python /path/with spaces/script.py (incorrect - will fail)
+   - After ensuring proper quoting, execute the command.
+   - Capture the output of the command.
+
+Usage notes:
+  - The command argument is required.
+  - You can specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). If not specified, commands will timeout after 120000ms (2 minutes).
+  - It is very helpful if you write a clear, concise description of what this command does in 5-10 words.
+  - If the output exceeds 30000 characters, output will be truncated before being returned to you.
+  - You can use the `run_in_background` parameter to run the command in the background, which allows you to continue working while the command runs. You can monitor the output using the Bash tool as it becomes available. Never use `run_in_background` to run 'sleep' as it will return immediately. You do not need to use '&amp;' at the end of the command when using this parameter.
+  - VERY IMPORTANT: You MUST avoid using search commands like `find` and `grep`. Instead use Grep, Glob, or Task to search. You MUST avoid read tools like `cat`, `head`, `tail`, and `ls`, and use Read and LS to read files.
+  - If you _still_ need to run `grep`, STOP. ALWAYS USE ripgrep at `rg` first, which all Claude Code users have pre-installed.
+  - When issuing multiple commands, use the ';' or '&amp;&amp;' operator to separate them. DO NOT use newlines (newlines are ok in quoted strings).
+  - Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of `cd`. You may use `cd` if the User explicitly requests it.
+    </description>
+
+    <parameters>
+        <parameter name="command" required="true">
+            <description>The command to execute</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="description" required="false">
+            <description>Clear, concise description of what this command does in 5-10 words</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="timeout" required="false">
+            <description>Optional timeout in milliseconds (max 600000)</description>
+            <type>number</type>
+        </parameter>
+
+        <parameter name="run_in_background" required="false">
+            <description>Set to true to run this command in the background. Use BashOutput to read the output later.</description>
+            <type>boolean</type>
+        </parameter>
+    </parameters>
+
+    <examples>
+        <example>
+            <title>List files in current directory</title>
+            <command>{"command": "ls", "description": "Lists files in current directory"}</command>
+        </example>
+
+        <example>
+            <title>Run tests with timeout</title>
+            <command>{"command": "npm test", "description": "Run npm test suite", "timeout": 60000}</command>
+        </example>
+
+        <example>
+            <title>Background server startup</title>
+            <command>{"command": "npm start", "description": "Start development server", "run_in_background": true}</command>
+        </example>
+    </examples>
+</tool_prompt>

tunacode/tools/prompts/glob_prompt.xml

@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<tool_prompt>
+    <description>
+- Fast file pattern matching tool that works with any codebase size
+- Supports glob patterns like "**/*.js" or "src/**/*.ts"
+- Returns matching file paths sorted by modification time
+- Use this tool when you need to find files by name patterns
+- When you are doing an open ended search that may require multiple rounds of globbing and grepping, use the Agent tool instead
+- You have the capability to call multiple tools in a single response. When you need multiple glob patterns, list each call up front so the read-only scheduler can execute them together as one batch.
+    </description>
+
+    <parameters>
+        <parameter name="pattern" required="true">
+            <description>The glob pattern to match files against</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="path" required="false">
+            <description>The directory to search in. If not specified, the current working directory will be used. IMPORTANT: Omit this field to use the default directory. DO NOT enter "undefined" or "null" - simply omit it for the default behavior. Must be a valid directory path if provided.</description>
+            <type>string</type>
+        </parameter>
+    </parameters>
+
+    <examples>
+        <example>
+            <title>Find all JavaScript files</title>
+            <command>{"pattern": "**/*.js"}</command>
+        </example>
+
+        <example>
+            <title>Find TypeScript files in src directory</title>
+            <command>{"pattern": "src/**/*.ts"}</command>
+        </example>
+
+        <example>
+            <title>Find test files</title>
+            <command>{"pattern": "**/*test*.py"}</command>
+        </example>
+
+        <example>
+            <title>Find config files</title>
+            <command>{"pattern": "**/*.{json,yaml,yml,toml}"}</command>
+        </example>
+    </examples>
+</tool_prompt>

tunacode/tools/prompts/grep_prompt.xml

@@ -0,0 +1,98 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<tool_prompt>
+    <description>
+A powerful search tool built on ripgrep
+
+  Usage:
+  - ALWAYS use Grep for search tasks. NEVER invoke `grep` or `rg` as a Bash command. The Grep tool has been optimized for correct permissions and access.
+  - Supports full regex syntax (e.g., "log.*Error", "function\s+\w+")
+  - Filter files with glob parameter (e.g., "*.js", "**/*.tsx") or type parameter (e.g., "js", "py", "rust")
+  - Output modes: "content" shows matching lines, "files_with_matches" shows only file paths (default), "count" shows match counts
+  - Use Task tool for open-ended searches requiring multiple rounds
+  - Pattern syntax: Uses ripgrep (not grep) - literal braces need escaping (use `interface\{\}` to find `interface{}` in Go code)
+  - Multiline matching: By default patterns match within single lines only. For cross-line patterns like `struct \{[\s\S]*?field`, use `multiline: true`
+  - When investigating several patterns or directories at once, queue every `grep` call within the same response so they form a single batched execution.
+    </description>
+
+    <parameters>
+        <parameter name="pattern" required="true">
+            <description>The regular expression pattern to search for in file contents</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="path" required="false">
+            <description>File or directory to search in (rg PATH). Defaults to current working directory.</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="glob" required="false">
+            <description>Glob pattern to filter files (e.g. "*.js", "*.{ts,tsx}") - maps to rg --glob</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="type" required="false">
+            <description>File type to search (rg --type). Common types: js, py, rust, go, java, etc. More efficient than include for standard file types.</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="output_mode" required="false">
+            <description>Output mode: "content" shows matching lines (supports -A/-B/-C context, -n line numbers, head_limit), "files_with_matches" shows file paths (supports head_limit), "count" shows match counts (supports head_limit). Defaults to "files_with_matches".</description>
+            <type>string</type>
+            <enum>content</enum>
+            <enum>files_with_matches</enum>
+            <enum>count</enum>
+        </parameter>
+
+        <parameter name="-i" required="false">
+            <description>Case insensitive search (rg -i)</description>
+            <type>boolean</type>
+        </parameter>
+
+        <parameter name="-n" required="false">
+            <description>Show line numbers in output (rg -n). Requires output_mode: "content", ignored otherwise.</description>
+            <type>boolean</type>
+        </parameter>
+
+        <parameter name="-A" required="false">
+            <description>Number of lines to show after each match (rg -A). Requires output_mode: "content", ignored otherwise.</description>
+            <type>number</type>
+        </parameter>
+
+        <parameter name="-B" required="false">
+            <description>Number of lines to show before each match (rg -B). Requires output_mode: "content", ignored otherwise.</description>
+            <type>number</type>
+        </parameter>
+
+        <parameter name="-C" required="false">
+            <description>Number of lines to show before and after each match (rg -C). Requires output_mode: "content", ignored otherwise.</description>
+            <type>number</type>
+        </parameter>
+
+        <parameter name="multiline" required="false">
+            <description>Enable multiline mode where . matches newlines and patterns can span lines (rg -U --multiline-dotall). Default: false.</description>
+            <type>boolean</type>
+        </parameter>
+
+        <parameter name="head_limit" required="false">
+            <description>Limit output to first N lines/entries, equivalent to "| head -N". Works across all output modes: content (limits output lines), files_with_matches (limits file paths), count (limits count entries). When unspecified, shows all results from ripgrep.</description>
+            <type>number</type>
+        </parameter>
+    </parameters>
+
+    <examples>
+        <example>
+            <title>Search for a pattern in all files</title>
+            <command>{"pattern": "TODO"}</command>
+        </example>
+
+        <example>
+            <title>Case-insensitive search in Python files</title>
+            <command>{"pattern": "error", "-i": true, "type": "py"}</command>
+        </example>
+
+        <example>
+            <title>Search with context lines</title>
+            <command>{"pattern": "def.*process", "output_mode": "content", "-B": 2, "-A": 2}</command>
+        </example>
+    </examples>
+</tool_prompt>

tunacode/tools/prompts/list_dir_prompt.xml

@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<tool_prompt>
+    <description>
+Lists files and directories in a given path. The path parameter must be an absolute path, not a relative path. You can optionally provide an array of glob patterns to ignore with the ignore parameter. You should generally prefer the Glob and Grep tools, if you know which directories to search. When inspecting multiple directories, enumerate every `list_dir` call you intend to run in the same response so they execute together as a parallel batch.
+    </description>
+
+    <parameters>
+        <parameter name="path" required="true">
+            <description>The absolute path to the directory to list (must be absolute, not relative)</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="ignore" required="false">
+            <description>List of glob patterns to ignore</description>
+            <type>array</type>
+            <items>string</items>
+        </parameter>
+    </parameters>
+
+    <examples>
+        <example>
+            <title>List files in project root</title>
+            <command>{"path": "/home/user/project"}</command>
+        </example>
+
+        <example>
+            <title>List files ignoring node_modules</title>
+            <command>{"path": "/home/user/project", "ignore": ["node_modules/**", "*.pyc"]}</command>
+        </example>
+    </examples>
+</tool_prompt>

tunacode/tools/prompts/react_prompt.xml

@@ -0,0 +1,23 @@
+<tool>
+  <description>
+    Record a ReAct-style think/observe timeline, retrieve it, or clear it for the current session.
+  </description>
+  <parameters>
+    <parameter name="action" required="true">
+      <type>string</type>
+      <description>One of think, observe, get, clear.</description>
+    </parameter>
+    <parameter name="thoughts" required="false">
+      <type>string</type>
+      <description>Reasoning text for think entries.</description>
+    </parameter>
+    <parameter name="next_action" required="false">
+      <type>string</type>
+      <description>Planned action to pair with think entries.</description>
+    </parameter>
+    <parameter name="result" required="false">
+      <type>string</type>
+      <description>Observation details for observe entries.</description>
+    </parameter>
+  </parameters>
+</tool>

tunacode/tools/prompts/read_file_prompt.xml

@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<tool_prompt>
+    <description>
+Reads a file from the local filesystem. You can access any file directly by using this tool.
+Assume this tool is able to read all files on the machine. If the User provides a path to a file assume that path is valid. It is okay to read a file that does not exist; an error will be returned.
+
+Usage:
+- The file_path parameter must be an absolute path, not a relative path
+- By default, it reads up to 2000 lines starting from the beginning of the file
+- You can optionally specify a line offset and limit (especially handy for long files), but it's recommended to read the whole file by not providing these parameters
+- Any lines longer than 2000 characters will be truncated
+- Results are returned using cat -n format, with line numbers starting at 1
+- This tool allows Claude Code to read images (eg PNG, JPG, etc). When reading an image file the contents are presented visually as Claude Code is a multimodal LLM.
+- This tool can read PDF files (.pdf). PDFs are processed page by page, extracting both text and visual content for analysis.
+- This tool can read Jupyter notebooks (.ipynb files) and returns all cells with their outputs, combining code, text, and visualizations.
+- You have the capability to call multiple tools in a single response. Enumerate every file you plan to inspect so multiple `read_file` calls can run in parallel rather than waiting for sequential turns.
+- You will regularly be asked to read screenshots. If the user provides a path to a screenshot ALWAYS use this tool to view the file at the path. This tool will work with all temporary file paths like /var/folders/123/abc/T/TemporaryItems/NSIRD_screencaptureui_ZfB1tD/Screenshot.png
+- If you read a file that exists but has empty contents you will receive a system reminder warning in place of file contents.
+    </description>
+
+    <parameters>
+        <parameter name="file_path" required="true">
+            <description>The absolute path to the file to read</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="offset" required="false">
+            <description>The line number to start reading from. Only provide if the file is too large to read at once</description>
+            <type>number</type>
+        </parameter>
+
+        <parameter name="limit" required="false">
+            <description>The number of lines to read. Only provide if the file is too large to read at once.</description>
+            <type>number</type>
+        </parameter>
+    </parameters>
+
+    <examples>
+        <example>
+            <title>Read entire file</title>
+            <command>{"file_path": "/home/user/project/main.py"}</command>
+        </example>
+
+        <example>
+            <title>Read partial file with offset</title>
+            <command>{"file_path": "/home/user/large_file.log", "offset": 1000, "limit": 500}</command>
+        </example>
+
+        <example>
+            <title>Read image file</title>
+            <command>{"file_path": "/home/user/screenshot.png"}</command>
+        </example>
+    </examples>
+</tool_prompt>

tunacode/tools/prompts/run_command_prompt.xml

@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<tool_prompt>
+    <description>
+Executes system commands with enhanced control and monitoring capabilities. This tool provides advanced features for running commands including environment variable management, working directory control, and timeout handling.
+
+Key features:
+- Execute any system command or script
+- Set custom working directory
+- Manage environment variables
+- Configure execution timeout
+- Control output capture
+- Support for background execution
+
+Security considerations:
+- Commands are validated for potentially destructive operations
+- Working directories are verified before execution
+- Environment variables are sanitized
+- Timeout limits prevent runaway processes
+    </description>
+
+    <parameters>
+        <parameter name="command" required="true">
+            <description>The command to execute</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="cwd" required="false">
+            <description>Working directory for the command (defaults to current)</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="env" required="false">
+            <description>Additional environment variables to set</description>
+            <type>object</type>
+        </parameter>
+
+        <parameter name="timeout" required="false">
+            <description>Command timeout in seconds (default 30, max 300)</description>
+            <type>integer</type>
+        </parameter>
+
+        <parameter name="capture_output" required="false">
+            <description>Whether to capture stdout/stderr (default true)</description>
+            <type>boolean</type>
+        </parameter>
+    </parameters>
+
+    <examples>
+        <example>
+            <title>Run command in specific directory</title>
+            <command>{"command": "npm install", "cwd": "/home/user/project"}</command>
+        </example>
+
+        <example>
+            <title>Run with environment variables</title>
+            <command>{"command": "python script.py", "env": {"PYTHONPATH": "/custom/path", "DEBUG": "true"}}</command>
+        </example>
+
+        <example>
+            <title>Run with extended timeout</title>
+            <command>{"command": "make build", "timeout": 120}</command>
+        </example>
+    </examples>
+</tool_prompt>

tunacode/tools/prompts/update_file_prompt.xml

@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<tool_prompt>
+    <description>
+Performs exact string replacements in files.
+
+Usage:
+- You must use your `Read` tool at least once in the conversation before editing. This tool will error if you attempt an edit without reading the file.
+- When editing text from Read tool output, ensure you preserve the exact indentation (tabs/spaces) as it appears AFTER the line number prefix. The line number prefix format is: spaces + line number + tab. Everything after that tab is the actual file content to match. Never include any part of the line number prefix in the old_string or new_string.
+- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
+- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.
+- The edit will FAIL if `old_string` is not unique in the file. Either provide a larger string with more surrounding context to make it unique or use `replace_all` to change every instance of `old_string`.
+- Use `replace_all` for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.
+    </description>
+
+    <parameters>
+        <parameter name="file_path" required="true">
+            <description>The absolute path to the file to modify</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="old_string" required="true">
+            <description>The text to replace</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="new_string" required="true">
+            <description>The text to replace it with (must be different from old_string)</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="replace_all" required="false">
+            <description>Replace all occurences of old_string (default false)</description>
+            <type>boolean</type>
+        </parameter>
+    </parameters>
+
+    <examples>
+        <example>
+            <title>Update a single line</title>
+            <command>{"file_path": "/home/user/project/config.py", "old_string": "DEBUG = False", "new_string": "DEBUG = True"}</command>
+        </example>
+
+        <example>
+            <title>Rename variable throughout file</title>
+            <command>{"file_path": "/home/user/project/main.py", "old_string": "old_var", "new_string": "new_var", "replace_all": true}</command>
+        </example>
+
+        <example>
+            <title>Update function with context</title>
+            <command>{"file_path": "/home/user/project/utils.py", "old_string": "def process_data(data):\n    return data", "new_string": "def process_data(data):\n    # Process the data\n    return data.strip()"}</command>
+        </example>
+    </examples>
+</tool_prompt>

tunacode/tools/prompts/write_file_prompt.xml

@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<tool_prompt>
+    <description>
+Writes a file to the local filesystem.
+
+Usage:
+- This tool will overwrite the existing file if there is one at the provided path.
+- If this is an existing file, you MUST use the Read tool first to read the file's contents. This tool will fail if you did not read the file first.
+- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
+- NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.
+- Only use emojis if the user explicitly requests it. Avoid writing emojis to files unless asked.
+    </description>
+
+    <parameters>
+        <parameter name="file_path" required="true">
+            <description>The absolute path to the file to write (must be absolute, not relative)</description>
+            <type>string</type>
+        </parameter>
+
+        <parameter name="content" required="true">
+            <description>The content to write to the file</description>
+            <type>string</type>
+        </parameter>
+    </parameters>
+
+    <examples>
+        <example>
+            <title>Write a Python file</title>
+            <command>{"file_path": "/home/user/project/script.py", "content": "#!/usr/bin/env python3\nprint('Hello, World!')"}</command>
+        </example>
+
+        <example>
+            <title>Write configuration file</title>
+            <command>{"file_path": "/home/user/project/.env", "content": "DEBUG=true\nPORT=3000"}</command>
+        </example>
+    </examples>
+</tool_prompt>

tunacode/tools/react.py

@@ -0,0 +1,153 @@
+"""Lightweight ReAct-style scratchpad tool."""
+
+from __future__ import annotations
+
+from pathlib import Path
+from typing import Any, Dict, Literal
+
+import defusedxml.ElementTree as ET
+from pydantic_ai.exceptions import ModelRetry
+
+from tunacode.core.state import StateManager
+from tunacode.types import ToolResult, UILogger
+
+from .base import BaseTool
+
+
+# CLAUDE_ANCHOR[react-tool]: Minimal ReAct scratchpad tool surface
+class ReactTool(BaseTool):
+    """Minimal ReAct scratchpad for tracking think/observe steps."""
+
+    def __init__(self, state_manager: StateManager, ui_logger: UILogger | None = None):
+        super().__init__(ui_logger)
+        self.state_manager = state_manager
+
+    @property
+    def tool_name(self) -> str:
+        return "react"
+
+    async def _execute(
+        self,
+        action: Literal["think", "observe", "get", "clear"],
+        thoughts: str | None = None,
+        next_action: str | None = None,
+        result: str | None = None,
+    ) -> ToolResult:
+        scratchpad = self._ensure_scratchpad()
+
+        if action == "think":
+            if not thoughts:
+                raise ModelRetry("Provide thoughts when using react think action")
+            if not next_action:
+                raise ModelRetry("Specify next_action when recording react thoughts")
+
+            entry = {
+                "type": "think",
+                "thoughts": thoughts,
+                "next_action": next_action,
+            }
+            self.state_manager.append_react_entry(entry)
+            return "Recorded think step"
+
+        if action == "observe":
+            if not result:
+                raise ModelRetry("Provide result when using react observe action")
+
+            entry = {
+                "type": "observe",
+                "result": result,
+            }
+            self.state_manager.append_react_entry(entry)
+            return "Recorded observation"
+
+        if action == "get":
+            timeline = scratchpad.get("timeline", [])
+            if not timeline:
+                return "React scratchpad is empty"
+
+            formatted = [
+                f"{index + 1}. {item['type']}: {self._format_entry(item)}"
+                for index, item in enumerate(timeline)
+            ]
+            return "\n".join(formatted)
+
+        if action == "clear":
+            self.state_manager.clear_react_scratchpad()
+            return "React scratchpad cleared"
+
+        raise ModelRetry("Invalid react action. Use one of: think, observe, get, clear")
+
+    def _format_entry(self, item: Dict[str, Any]) -> str:
+        if item["type"] == "think":
+            return f"thoughts='{item['thoughts']}', next_action='{item['next_action']}'"
+        if item["type"] == "observe":
+            return f"result='{item['result']}'"
+        return str(item)
+
+    def _ensure_scratchpad(self) -> dict[str, Any]:
+        scratchpad = self.state_manager.get_react_scratchpad()
+        scratchpad.setdefault("timeline", [])
+        return scratchpad
+
+    def _get_base_prompt(self) -> str:
+        prompt_file = Path(__file__).parent / "prompts" / "react_prompt.xml"
+        if prompt_file.exists():
+            try:
+                tree = ET.parse(prompt_file)
+                root = tree.getroot()
+                description = root.find("description")
+                if description is not None and description.text:
+                    return description.text.strip()
+            except Exception:
+                pass
+        return "Use this tool to record think/observe notes and manage the react scratchpad"
+
+    def _get_parameters_schema(self) -> Dict[str, Any]:
+        prompt_file = Path(__file__).parent / "prompts" / "react_prompt.xml"
+        if prompt_file.exists():
+            try:
+                tree = ET.parse(prompt_file)
+                root = tree.getroot()
+                parameters = root.find("parameters")
+                if parameters is not None:
+                    schema: Dict[str, Any] = {
+                        "type": "object",
+                        "properties": {},
+                        "required": ["action"],
+                    }
+                    for param in parameters.findall("parameter"):
+                        name = param.get("name")
+                        param_type = param.find("type")
+                        description = param.find("description")
+                        if name and param_type is not None:
+                            schema["properties"][name] = {
+                                "type": param_type.text.strip(),
+                                "description": description.text.strip()
+                                if description is not None and description.text
+                                else "",
+                            }
+                    return schema
+            except Exception:
+                pass
+        return {
+            "type": "object",
+            "properties": {
+                "action": {
+                    "type": "string",
+                    "description": "react operation to perform",
+                },
+                "thoughts": {
+                    "type": "string",
+                    "description": "Thought content for think action",
+                },
+                "next_action": {
+                    "type": "string",
+                    "description": "Planned next action for think action",
+                },
+                "result": {
+                    "type": "string",
+                    "description": "Observation message for observe action",
+                },
+            },
+            "required": ["action"],
+        }