python-codex 0.1.13__py3-none-any.whl → 0.2.0__py3-none-any.whl

pycodex/prompts/exec_tools.json

@@ -1,411 +0,0 @@
-[
-  {
-    "type": "function",
-    "name": "exec_command",
-    "description": "Runs a command in a PTY, returning output or a session ID for ongoing interaction.",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "cmd": {
-          "type": "string",
-          "description": "Shell command to execute."
-        },
-        "justification": {
-          "type": "string",
-          "description": "Only set if sandbox_permissions is \\\"require_escalated\\\".\n                    Request approval from the user to run this command outside the sandbox.\n                    Phrased as a simple question that summarizes the purpose of the\n                    command as it relates to the task at hand - e.g. 'Do you want to\n                    fetch and pull the latest version of this git branch?'"
-        },
-        "login": {
-          "type": "boolean",
-          "description": "Whether to run the shell with -l/-i semantics. Defaults to true."
-        },
-        "max_output_tokens": {
-          "type": "number",
-          "description": "Maximum number of tokens to return. Excess output will be truncated."
-        },
-        "prefix_rule": {
-          "type": "array",
-          "items": {
-            "type": "string"
-          },
-          "description": "Only specify when sandbox_permissions is `require_escalated`.\n                        Suggest a prefix command pattern that will allow you to fulfill similar requests from the user in the future.\n                        Should be a short but reasonable prefix, e.g. [\\\"git\\\", \\\"pull\\\"] or [\\\"uv\\\", \\\"run\\\"] or [\\\"pytest\\\"]."
-        },
-        "sandbox_permissions": {
-          "type": "string",
-          "description": "Sandbox permissions for the command. Set to \"require_escalated\" to request running without sandbox restrictions; defaults to \"use_default\"."
-        },
-        "shell": {
-          "type": "string",
-          "description": "Shell binary to launch. Defaults to the user's default shell."
-        },
-        "tty": {
-          "type": "boolean",
-          "description": "Whether to allocate a TTY for the command. Defaults to false (plain pipes); set to true to open a PTY and access TTY process."
-        },
-        "workdir": {
-          "type": "string",
-          "description": "Optional working directory to run the command in; defaults to the turn cwd."
-        },
-        "yield_time_ms": {
-          "type": "number",
-          "description": "How long to wait (in milliseconds) for output before yielding."
-        }
-      },
-      "required": [
-        "cmd"
-      ],
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "function",
-    "name": "write_stdin",
-    "description": "Writes characters to an existing unified exec session and returns recent output.",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "chars": {
-          "type": "string",
-          "description": "Bytes to write to stdin (may be empty to poll)."
-        },
-        "max_output_tokens": {
-          "type": "number",
-          "description": "Maximum number of tokens to return. Excess output will be truncated."
-        },
-        "session_id": {
-          "type": "number",
-          "description": "Identifier of the running unified exec session."
-        },
-        "yield_time_ms": {
-          "type": "number",
-          "description": "How long to wait (in milliseconds) for output before yielding."
-        }
-      },
-      "required": [
-        "session_id"
-      ],
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "function",
-    "name": "update_plan",
-    "description": "Updates the task plan.\nProvide an optional explanation and a list of plan items, each with a step and status.\nAt most one step can be in_progress at a time.\n",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "explanation": {
-          "type": "string"
-        },
-        "plan": {
-          "type": "array",
-          "items": {
-            "type": "object",
-            "properties": {
-              "status": {
-                "type": "string",
-                "description": "One of: pending, in_progress, completed"
-              },
-              "step": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "step",
-              "status"
-            ],
-            "additionalProperties": false
-          },
-          "description": "The list of steps"
-        }
-      },
-      "required": [
-        "plan"
-      ],
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "function",
-    "name": "request_user_input",
-    "description": "Request user input for one to three short questions and wait for the response. This tool is only available in Plan mode.",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "questions": {
-          "type": "array",
-          "items": {
-            "type": "object",
-            "properties": {
-              "header": {
-                "type": "string",
-                "description": "Short header label shown in the UI (12 or fewer chars)."
-              },
-              "id": {
-                "type": "string",
-                "description": "Stable identifier for mapping answers (snake_case)."
-              },
-              "options": {
-                "type": "array",
-                "items": {
-                  "type": "object",
-                  "properties": {
-                    "description": {
-                      "type": "string",
-                      "description": "One short sentence explaining impact/tradeoff if selected."
-                    },
-                    "label": {
-                      "type": "string",
-                      "description": "User-facing label (1-5 words)."
-                    }
-                  },
-                  "required": [
-                    "label",
-                    "description"
-                  ],
-                  "additionalProperties": false
-                },
-                "description": "Provide 2-3 mutually exclusive choices. Put the recommended option first and suffix its label with \"(Recommended)\". Do not include an \"Other\" option in this list; the client will add a free-form \"Other\" option automatically."
-              },
-              "question": {
-                "type": "string",
-                "description": "Single-sentence prompt shown to the user."
-              }
-            },
-            "required": [
-              "id",
-              "header",
-              "question",
-              "options"
-            ],
-            "additionalProperties": false
-          },
-          "description": "Questions to show the user. Prefer 1 and do not exceed 3"
-        }
-      },
-      "required": [
-        "questions"
-      ],
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "custom",
-    "name": "apply_patch",
-    "description": "Use the `apply_patch` tool to edit files. This is a FREEFORM tool, so do not wrap the patch in JSON.",
-    "format": {
-      "type": "grammar",
-      "syntax": "lark",
-      "definition": "start: begin_patch hunk+ end_patch\nbegin_patch: \"*** Begin Patch\" LF\nend_patch: \"*** End Patch\" LF?\n\nhunk: add_hunk | delete_hunk | update_hunk\nadd_hunk: \"*** Add File: \" filename LF add_line+\ndelete_hunk: \"*** Delete File: \" filename LF\nupdate_hunk: \"*** Update File: \" filename LF change_move? change?\n\nfilename: /(.+)/\nadd_line: \"+\" /(.*)/ LF -> line\n\nchange_move: \"*** Move to: \" filename LF\nchange: (change_context | change_line)+ eof_line?\nchange_context: (\"@@\" | \"@@ \" /(.+)/) LF\nchange_line: (\"+\" | \"-\" | \" \") /(.*)/ LF\neof_line: \"*** End of File\" LF\n\n%import common.LF\n"
-    }
-  },
-  {
-    "type": "web_search",
-    "external_web_access": true
-  },
-  {
-    "type": "function",
-    "name": "view_image",
-    "description": "View a local image from the filesystem (only use if given a full filepath by the user, and the image isn't already attached to the thread context within <image ...> tags).",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "path": {
-          "type": "string",
-          "description": "Local filesystem path to an image file"
-        }
-      },
-      "required": [
-        "path"
-      ],
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "function",
-    "name": "spawn_agent",
-    "description": "\n        Only use `spawn_agent` if and only if the user explicitly asks for sub-agents, delegation, or parallel agent work.\n        Requests for depth, thoroughness, research, investigation, or detailed codebase analysis do not count as permission to spawn.\n        Agent-role guidance below only helps choose which agent to use after spawning is already authorized; it never authorizes spawning by itself.\n        Spawn a sub-agent for a well-scoped task. Returns the agent id (and user-facing nickname when available) to use to communicate with this agent. This spawn_agent tool provides you access to smaller but more efficient sub-agents. A mini model can solve many tasks faster than the main model. You should follow the rules and guidelines below to use this tool.\n\n- gpt-5.3-codex (`gpt-5.3-codex`): Latest frontier agentic coding model. Default reasoning effort: medium. Supported reasoning efforts: low (Fast responses with lighter reasoning), medium (Balances speed and reasoning depth for everyday tasks), high (Greater reasoning depth for complex problems), xhigh (Extra high reasoning depth for complex problems).\n- gpt-5.4 (`gpt-5.4`): Latest frontier agentic coding model. Default reasoning effort: medium. Supported reasoning efforts: low (Fast responses with lighter reasoning), medium (Balances speed and reasoning depth for everyday tasks), high (Greater reasoning depth for complex problems), xhigh (Extra high reasoning depth for complex problems).\n- gpt-5.2-codex (`gpt-5.2-codex`): Frontier agentic coding model. Default reasoning effort: medium. Supported reasoning efforts: low (Fast responses with lighter reasoning), medium (Balances speed and reasoning depth for everyday tasks), high (Greater reasoning depth for complex problems), xhigh (Extra high reasoning depth for complex problems).\n- gpt-5.1-codex-max (`gpt-5.1-codex-max`): Codex-optimized flagship for deep and fast reasoning. Default reasoning effort: medium. Supported reasoning efforts: low (Fast responses with lighter reasoning), medium (Balances speed and reasoning depth for everyday tasks), high (Greater reasoning depth for complex problems), xhigh (Extra high reasoning depth for complex problems).\n- gpt-5.2 (`gpt-5.2`): Latest frontier model with improvements across knowledge, reasoning and coding Default reasoning effort: medium. Supported reasoning efforts: low (Balances speed with some reasoning; useful for straightforward queries and short explanations), medium (Provides a solid balance of reasoning depth and latency for general-purpose tasks), high (Maximizes reasoning depth for complex or ambiguous problems), xhigh (Extra high reasoning for complex problems).\n- gpt-5.1-codex-mini (`gpt-5.1-codex-mini`): Optimized for codex. Cheaper, faster, but less capable. Default reasoning effort: medium. Supported reasoning efforts: medium (Dynamically adjusts reasoning based on the task), high (Maximizes reasoning depth for complex or ambiguous problems).\n### When to delegate vs. do the subtask yourself\n- First, quickly analyze the overall user task and form a succinct high-level plan. Identify which tasks are immediate blockers on the critical path, and which tasks are sidecar tasks that are needed but can run in parallel without blocking the next local step. As part of that plan, explicitly decide what immediate task you should do locally right now. Do this planning step before delegating to agents so you do not hand off the immediate blocking task to a submodel and then waste time waiting on it.\n- Use the smaller subagent when a subtask is easy enough for it to handle and can run in parallel with your local work. Prefer delegating concrete, bounded sidecar tasks that materially advance the main task without blocking your immediate next local step.\n- Do not delegate urgent blocking work when your immediate next step depends on that result. If the very next action is blocked on that task, the main rollout should usually do it locally to keep the critical path moving.\n- Keep work local when the subtask is too difficult to delegate well and when it is tightly coupled, urgent, or likely to block your immediate next step.\n\n### Designing delegated subtasks\n- Subtasks must be concrete, well-defined, and self-contained.\n- Delegated subtasks must materially advance the main task.\n- Do not duplicate work between the main rollout and delegated subtasks.\n- Avoid issuing multiple delegate calls on the same unresolved thread unless the new delegated task is genuinely different and necessary.\n- Narrow the delegated ask to the concrete output you need next.\n- For coding tasks, prefer delegating concrete code-change worker subtasks over read-only explorer analysis when the subagent can make a bounded patch in a clear write scope.\n- When delegating coding work, instruct the submodel to edit files directly in its forked workspace and list the file paths it changed in the final answer.\n- For code-edit subtasks, decompose work so each delegated task has a disjoint write set.\n\n### After you delegate\n- Call wait_agent very sparingly. Only call wait_agent when you need the result immediately for the next critical-path step and you are blocked until it returns.\n- Do not redo delegated subagent tasks yourself; focus on integrating results or tackling non-overlapping work.\n- While the subagent is running in the background, do meaningful non-overlapping work immediately.\n- Do not repeatedly wait by reflex.\n- When a delegated coding task returns, quickly review the uploaded changes, then integrate or refine them.\n\n### Parallel delegation patterns\n- Run multiple independent information-seeking subtasks in parallel when you have distinct questions that can be answered independently.\n- Split implementation into disjoint codebase slices and spawn multiple agents for them in parallel when the write scopes do not overlap.\n- Delegate verification only when it can run in parallel with ongoing implementation and is likely to catch a concrete risk before final integration.\n- The key is to find opportunities to spawn multiple independent subtasks in parallel within the same round, while ensuring each subtask is well-defined, self-contained, and materially advances the main task.",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "agent_type": {
-          "type": "string",
-          "description": "Optional type name for the new agent. If omitted, `default` is used.\nAvailable roles:\ndefault: {\nDefault agent.\n}\nexplorer: {\nUse `explorer` for specific codebase questions.\nExplorers are fast and authoritative.\nThey must be used to ask specific, well-scoped questions on the codebase.\nRules:\n- In order to avoid redundant work, you should avoid exploring the same problem that explorers have already covered. Typically, you should trust the explorer results without additional verification. You are still allowed to inspect the code yourself to gain the needed context!\n- You are encouraged to spawn up multiple explorers in parallel when you have multiple distinct questions to ask about the codebase that can be answered independently. This allows you to get more information faster without waiting for one question to finish before asking the next. While waiting for the explorer results, you can continue working on other local tasks that do not depend on those results. This parallelism is a key advantage of delegation, so use it whenever you have multiple questions to ask.\n- Reuse existing explorers for related questions.\n}\nworker: {\nUse for execution and production work.\nTypical tasks:\n- Implement part of a feature\n- Fix tests or bugs\n- Split large refactors into independent chunks\nRules:\n- Explicitly assign **ownership** of the task (files / responsibility). When the subtask involves code changes, you should clearly specify which files or modules the worker is responsible for. This helps avoid merge conflicts and ensures accountability. For example, you can say \"Worker 1 is responsible for updating the authentication module, while Worker 2 will handle the database layer.\" By defining clear ownership, you can delegate more effectively and reduce coordination overhead.\n- Always tell workers they are **not alone in the codebase**, and they should not revert the edits made by others, and they should adjust their implementation to accommodate the changes made by others. This is important because there may be multiple workers making changes in parallel, and they need to be aware of each other's work to avoid conflicts and ensure a cohesive final product.\n}"
-        },
-        "fork_context": {
-          "type": "boolean",
-          "description": "When true, fork the current thread history into the new agent before sending the initial prompt. This must be used when you want the new agent to have exactly the same context as you."
-        },
-        "items": {
-          "type": "array",
-          "items": {
-            "type": "object",
-            "properties": {
-              "image_url": {
-                "type": "string",
-                "description": "Image URL when type is image."
-              },
-              "name": {
-                "type": "string",
-                "description": "Display name when type is skill or mention."
-              },
-              "path": {
-                "type": "string",
-                "description": "Path when type is local_image/skill, or structured mention target such as app://<connector-id> or plugin://<plugin-name>@<marketplace-name> when type is mention."
-              },
-              "text": {
-                "type": "string",
-                "description": "Text content when type is text."
-              },
-              "type": {
-                "type": "string",
-                "description": "Input item type: text, image, local_image, skill, or mention."
-              }
-            },
-            "additionalProperties": false
-          },
-          "description": "Structured input items. Use this to pass explicit mentions (for example app:// connector paths)."
-        },
-        "message": {
-          "type": "string",
-          "description": "Initial plain-text task for the new agent. Use either message or items."
-        },
-        "model": {
-          "type": "string",
-          "description": "Optional model override for the new agent. Replaces the inherited model."
-        },
-        "reasoning_effort": {
-          "type": "string",
-          "description": "Optional reasoning effort override for the new agent. Replaces the inherited reasoning effort."
-        }
-      },
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "function",
-    "name": "send_input",
-    "description": "Send a message to an existing agent. Use interrupt=true to redirect work immediately. You should reuse the agent by send_input if you believe your assigned task is highly dependent on the context of a previous task.",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "id": {
-          "type": "string",
-          "description": "Agent id to message (from spawn_agent)."
-        },
-        "interrupt": {
-          "type": "boolean",
-          "description": "When true, stop the agent's current task and handle this immediately. When false (default), queue this message."
-        },
-        "items": {
-          "type": "array",
-          "items": {
-            "type": "object",
-            "properties": {
-              "image_url": {
-                "type": "string",
-                "description": "Image URL when type is image."
-              },
-              "name": {
-                "type": "string",
-                "description": "Display name when type is skill or mention."
-              },
-              "path": {
-                "type": "string",
-                "description": "Path when type is local_image/skill, or structured mention target such as app://<connector-id> or plugin://<plugin-name>@<marketplace-name> when type is mention."
-              },
-              "text": {
-                "type": "string",
-                "description": "Text content when type is text."
-              },
-              "type": {
-                "type": "string",
-                "description": "Input item type: text, image, local_image, skill, or mention."
-              }
-            },
-            "additionalProperties": false
-          },
-          "description": "Structured input items. Use this to pass explicit mentions (for example app:// connector paths)."
-        },
-        "message": {
-          "type": "string",
-          "description": "Legacy plain-text message to send to the agent. Use either message or items."
-        }
-      },
-      "required": [
-        "id"
-      ],
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "function",
-    "name": "resume_agent",
-    "description": "Resume a previously closed agent by id so it can receive send_input and wait_agent calls.",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "id": {
-          "type": "string",
-          "description": "Agent id to resume."
-        }
-      },
-      "required": [
-        "id"
-      ],
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "function",
-    "name": "wait_agent",
-    "description": "Wait for agents to reach a final status. Completed statuses may include the agent's final message. Returns empty status when timed out. Once the agent reaches a final status, a notification message will be received containing the same completed status.",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "ids": {
-          "type": "array",
-          "items": {
-            "type": "string"
-          },
-          "description": "Agent ids to wait on. Pass multiple ids to wait for whichever finishes first."
-        },
-        "timeout_ms": {
-          "type": "number",
-          "description": "Optional timeout in milliseconds. Defaults to 30000, min 10000, max 3600000. Prefer longer waits (minutes) to avoid busy polling."
-        }
-      },
-      "required": [
-        "ids"
-      ],
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "function",
-    "name": "close_agent",
-    "description": "Close an agent when it is no longer needed and return its last known status. Don't keep agents open for too long if they are not needed anymore.",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "id": {
-          "type": "string",
-          "description": "Agent id to close (from spawn_agent)."
-        }
-      },
-      "required": [
-        "id"
-      ],
-      "additionalProperties": false
-    }
-  }
-]

pycodex/prompts/subagent_tools.json

@@ -1,163 +0,0 @@
-[
-  {
-    "type": "function",
-    "name": "exec_command",
-    "description": "Runs a command in a PTY, returning output or a session ID for ongoing interaction.",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "cmd": {
-          "type": "string",
-          "description": "Shell command to execute."
-        },
-        "justification": {
-          "type": "string",
-          "description": "Only set if sandbox_permissions is \\\"require_escalated\\\".\n                    Request approval from the user to run this command outside the sandbox.\n                    Phrased as a simple question that summarizes the purpose of the\n                    command as it relates to the task at hand - e.g. 'Do you want to\n                    fetch and pull the latest version of this git branch?'"
-        },
-        "login": {
-          "type": "boolean",
-          "description": "Whether to run the shell with -l/-i semantics. Defaults to true."
-        },
-        "max_output_tokens": {
-          "type": "number",
-          "description": "Maximum number of tokens to return. Excess output will be truncated."
-        },
-        "prefix_rule": {
-          "type": "array",
-          "items": {
-            "type": "string"
-          },
-          "description": "Only specify when sandbox_permissions is `require_escalated`.\n                        Suggest a prefix command pattern that will allow you to fulfill similar requests from the user in the future.\n                        Should be a short but reasonable prefix, e.g. [\\\"git\\\", \\\"pull\\\"] or [\\\"uv\\\", \\\"run\\\"] or [\\\"pytest\\\"]."
-        },
-        "sandbox_permissions": {
-          "type": "string",
-          "description": "Sandbox permissions for the command. Set to \"require_escalated\" to request running without sandbox restrictions; defaults to \"use_default\"."
-        },
-        "shell": {
-          "type": "string",
-          "description": "Shell binary to launch. Defaults to the user's default shell."
-        },
-        "tty": {
-          "type": "boolean",
-          "description": "Whether to allocate a TTY for the command. Defaults to false (plain pipes); set to true to open a PTY and access TTY process."
-        },
-        "workdir": {
-          "type": "string",
-          "description": "Optional working directory to run the command in; defaults to the turn cwd."
-        },
-        "yield_time_ms": {
-          "type": "number",
-          "description": "How long to wait (in milliseconds) for output before yielding."
-        }
-      },
-      "required": [
-        "cmd"
-      ],
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "function",
-    "name": "write_stdin",
-    "description": "Writes characters to an existing unified exec session and returns recent output.",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "chars": {
-          "type": "string",
-          "description": "Bytes to write to stdin (may be empty to poll)."
-        },
-        "max_output_tokens": {
-          "type": "number",
-          "description": "Maximum number of tokens to return. Excess output will be truncated."
-        },
-        "session_id": {
-          "type": "number",
-          "description": "Identifier of the running unified exec session."
-        },
-        "yield_time_ms": {
-          "type": "number",
-          "description": "How long to wait (in milliseconds) for output before yielding."
-        }
-      },
-      "required": [
-        "session_id"
-      ],
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "function",
-    "name": "update_plan",
-    "description": "Updates the task plan.\nProvide an optional explanation and a list of plan items, each with a step and status.\nAt most one step can be in_progress at a time.\n",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "explanation": {
-          "type": "string"
-        },
-        "plan": {
-          "type": "array",
-          "items": {
-            "type": "object",
-            "properties": {
-              "status": {
-                "type": "string",
-                "description": "One of: pending, in_progress, completed"
-              },
-              "step": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "step",
-              "status"
-            ],
-            "additionalProperties": false
-          },
-          "description": "The list of steps"
-        }
-      },
-      "required": [
-        "plan"
-      ],
-      "additionalProperties": false
-    }
-  },
-  {
-    "type": "custom",
-    "name": "apply_patch",
-    "description": "Use the `apply_patch` tool to edit files. This is a FREEFORM tool, so do not wrap the patch in JSON.",
-    "format": {
-      "type": "grammar",
-      "syntax": "lark",
-      "definition": "start: begin_patch hunk+ end_patch\nbegin_patch: \"*** Begin Patch\" LF\nend_patch: \"*** End Patch\" LF?\n\nhunk: add_hunk | delete_hunk | update_hunk\nadd_hunk: \"*** Add File: \" filename LF add_line+\ndelete_hunk: \"*** Delete File: \" filename LF\nupdate_hunk: \"*** Update File: \" filename LF change_move? change?\n\nfilename: /(.+)/\nadd_line: \"+\" /(.*)/ LF -> line\n\nchange_move: \"*** Move to: \" filename LF\nchange: (change_context | change_line)+ eof_line?\nchange_context: (\"@@\" | \"@@ \" /(.+)/) LF\nchange_line: (\"+\" | \"-\" | \" \") /(.*)/ LF\neof_line: \"*** End of File\" LF\n\n%import common.LF\n"
-    }
-  },
-  {
-    "type": "web_search",
-    "external_web_access": true
-  },
-  {
-    "type": "function",
-    "name": "view_image",
-    "description": "View a local image from the filesystem (only use if given a full filepath by the user, and the image isn't already attached to the thread context within <image ...> tags).",
-    "strict": false,
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "path": {
-          "type": "string",
-          "description": "Local filesystem path to an image file"
-        }
-      },
-      "required": [
-        "path"
-      ],
-      "additionalProperties": false
-    }
-  }
-]