vamp-cli 0.1.1__tar.gz → 0.1.3__tar.gz

vamp_cli-0.1.3/MANIFEST.in

@@ -0,0 +1 @@
+recursive-include src/vamp_cli/config *.yaml

{vamp_cli-0.1.1/src/vamp_cli.egg-info → vamp_cli-0.1.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: vamp-cli
-Version: 0.1.1
+Version: 0.1.3
 Summary: VAMP-CLI is an interactive coding agent for working in a local repository. It combines a planner, a coder, model fallbacks, workspace-aware file tools, and a Docker-backed command sandbox in one terminal application. The agent can inspect and edit files, search a codebase, run commands, maintain a task list, and ask for confirmation before executing potentially dangerous operations.
 Author-email: Satyam Kumar <satkr2208@gmail.com>
 License: MIT License
@@ -91,7 +91,7 @@ The first run automatically builds the `vamp-sandbox:latest` image from [`src/va
 Create and activate a virtual environment, then install the project (all dependencies will be installed itself):
 
 ```bash
-python3.11 -m venv .venv
+python3.12 -m venv .venv
 source .venv/bin/activate
 python -m pip install --upgrade pip
 python -m pip install vamp-cli 

{vamp_cli-0.1.1 → vamp_cli-0.1.3}/README.md

@@ -37,7 +37,7 @@ The first run automatically builds the `vamp-sandbox:latest` image from [`src/va
 Create and activate a virtual environment, then install the project (all dependencies will be installed itself):
 
 ```bash
-python3.11 -m venv .venv
+python3.12 -m venv .venv
 source .venv/bin/activate
 python -m pip install --upgrade pip
 python -m pip install vamp-cli 

{vamp_cli-0.1.1 → vamp_cli-0.1.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "vamp-cli"
-version = "0.1.1"
+version = "0.1.3"
 authors = [
   { name = "Satyam Kumar", email = "satkr2208@gmail.com" }
 ]
@@ -42,6 +42,10 @@ dependencies = [
 [tool.setuptools.packages.find]
 where = ["src"]
 
+[tool.setuptools.package-data]
+vamp_cli = ["*.md", "**/*.md", "**/*.yaml"]
+
+
 [project.scripts]
 vamp = "vamp_cli.main:start"
 

vamp_cli-0.1.3/src/vamp_cli/config/default_config.yaml

@@ -0,0 +1,291 @@
+models:
+  qwen:
+    model: dashscope/qwen3.6-flash
+    api_base: https://ws-n7c4pdh4ldno9hkc.ap-southeast-1.maas.aliyuncs.com/compatible-mode/v1
+    api_key_env: DASHSCOPE_API_KEY
+    adapter: reasoning
+    params:
+      temperature: 0.2
+      max_tokens: 8192
+      max_retries: 2
+      streaming: true
+    fallbacks: []
+      # - openai
+    capabilities:
+      supports_tools: true
+      supports_parallel_tools: false
+      supports_streaming: true
+      supports_reasoning: true
+      context_window: 128000
+      
+      # (for DashScope native OpenAI mode)
+      reasoning_param: enable_thinking
+      reasoning_value: true
+      
+      # (general)
+      # reasoning_param: thinking
+      # reasoning_value:
+      #   type: enabled
+      #   budget_tokens: 4000
+
+
+  openai:
+    model: openai/gpt-5.6-luna
+    api_base: 
+    api_key_env: OPENAI_API_KEY
+    adapter: reasoning
+    params:
+      temperature: 0.2
+      max_tokens: 8192
+      max_retries: 2
+      streaming: true
+    fallbacks: []
+    capabilities:
+      supports_tools: true
+      supports_parallel_tools: false
+      supports_streaming: true
+      supports_reasoning: true
+      reasoning_param: reasoning_effort
+      reasoning_value: medium # Options: low, medium, high
+      context_window: 128000
+
+
+  anthropic:
+    model: anthropic/claude-opus-5-5
+    api_base: 
+    api_key_env: ANTHROPIC_API_KEY
+    adapter: reasoning
+    params:
+      temperature: 0.2
+      max_tokens: 8192
+      max_retries: 2
+      streaming: true
+    fallbacks: []
+    capabilities:
+      supports_tools: true
+      supports_parallel_tools: false
+      supports_streaming: true
+      supports_reasoning: true
+      reasoning_param: thinking
+      reasoning_value:
+        type: adaptive
+      context_window: 128000
+      # or (for Opus 4.5, Sonnet 4.5, Haiku 4.5)
+      # reasoning_param: thinking
+      # reasoning_value:
+      #   type: enabled
+      #   budget_tokens: 4000
+
+
+
+  deepseek:
+    model: deepseek/deepseek-v4
+    api_base:
+    api_key_env: DEEPSEEK_API_KEY
+    adapter: reasoning
+    params:
+      temperature: 0.2
+      max_tokens: 8192
+      max_retries: 2
+      streaming: true
+    fallbacks: []
+    capabilities:
+      supports_tools: true
+      supports_parallel_tools: false
+      supports_streaming: true
+      supports_reasoning: true
+      reasoning_param: reasoning_effort
+      reasoning_value: high # Options: low, high, max      context_window: 128000
+
+
+
+  kimi:
+    model: kimi/kimi
+    api_base:
+    api_key_env: KIMI_API_KEY
+    adapter: reasoning
+    params:
+      temperature: 0.2
+      max_tokens: 8192
+      max_retries: 2
+      streaming: true
+    fallbacks: []
+    capabilities:
+      supports_tools: true
+      supports_parallel_tools: false
+      supports_streaming: true
+      supports_reasoning: true
+      reasoning_param: reasoning_effort
+      reasoning_value: high # Options: low, high, max
+      context_window: 128000
+
+
+  gork:
+    model: gork/gork
+    api_base:
+    api_key_env: GORK_API_KEY
+    adapter: reasoning
+    params:
+      temperature: 0.2
+      max_tokens: 8192
+      max_retries: 2
+      streaming: true
+    fallbacks: []
+    capabilities:
+      supports_tools: true
+      supports_parallel_tools: false
+      supports_streaming: true
+      supports_reasoning: true
+      reasoning_param: reasoning_effort
+      reasoning_value: high # Options: low, high, max, xhigh
+      context_window: 128000
+
+
+  gemini:
+    model: gemini/gemini
+    api_base:
+    api_key_env: GEMINI_API_KEY
+    adapter: reasoning
+    params:
+      temperature: 0.2
+      max_tokens: 8192
+      max_retries: 2
+      streaming: true
+    fallbacks: []
+    capabilities:
+      supports_tools: true
+      supports_parallel_tools: false
+      supports_streaming: true
+      supports_reasoning: true
+      context_window: 128000
+
+      # for gemini 2.5 series
+      reasoning_param: thinking_config
+      reasoning_value:
+        thinking_budget: 4000 # -1 for dynamic, 0 to disable, or an explicit integer budget
+
+      # for gemini 3/4 series  
+      # reasoning_param: thinking_config
+      # reasoning_value:
+      #   thinking_level: high  # Options: minimal, low, medium, high
+
+
+profiles:
+  default_coder:
+    model: qwen
+    tools:
+      - list_dir
+      - read_file
+      - read_many_files
+      - apply_search_replace
+      - write_file
+      - file_search
+      - ripgrep_search
+      - execute_command
+      - write_update_todos
+    prompt: prompts/coder.md
+
+  default_planner:
+    model: qwen
+    tools:
+      - list_dir
+      - read_file
+      - read_many_files
+      - file_search
+      - ripgrep_search
+      - submit_plan
+      - execute_command
+    prompt: prompts/planner.md
+
+  planner:
+    model: qwen
+    tools:
+      - list_dir
+      - read_file
+      - read_many_files
+      - file_search
+      - ripgrep_search
+      - submit_plan
+      - execute_command
+    prompt: prompts/planner.md
+
+  coder:
+    model: qwen
+    tools:
+      - list_dir
+      - read_file
+      - read_many_files
+      - apply_search_replace
+      - write_file
+      - file_search
+      - ripgrep_search
+      - execute_command
+      - write_update_todos
+    prompt: prompts/coder.md
+
+default_profile: 
+  - default_coder
+  - default_planner
+
+
+
+
+# reasoning styles
+
+# 1. openai
+#   reasoning_param: "reasoning_effort"
+#   reasoning_value: "medium" # Options: "low", "medium", "high"
+
+# 2. qwen
+#   reasoning_param: "thinking"
+#   reasoning_value:
+#     type: "enabled"
+#     budget_tokens: 4000
+
+# 4. qwen (for DashScope native OpenAI mode)
+#   reasoning_param: "enable_thinking"
+#   reasoning_value: "true"
+
+# 5. anthropic (newer models) 
+#   reasoning_param: "thinking"
+#   reasoning_value:
+#     type: "adaptive"
+
+# 6. anthropic (older models)
+#     Models: [Claude Mythos Preview, Claude Opus 4.6, Claude Sonnet 4.6,	Claude Opus 4.5, Claude Sonnet 4.5, Claude Haiku 4.5]
+#   reasoning_param: "thinking"
+#   reasoning_value:
+#     type: "enabled"
+#     budget_tokens: 4000
+
+# 7. deepseek
+# Models: [deepseek-reasoner, deepseek-v4]
+#   reasoning_param: "reasoning_effort"
+#   reasoning_value: "high" # Options: "low", "high", "max"
+
+# 8. deepseek (for deepseek's anthropic style models)
+#   reasoning_param: "thinking"
+#   reasoning_value: 
+#     type: "enabled"
+
+# 9. kimi
+#   reasoning_param: "reasoning_effort"
+#   reasoning_value: "high" # Options: "low", "high", "max" (default: "max")
+
+# 10. grok/xAi
+# reasoning_param: "reasoning_effort"
+# reasoning_value: "high" # Options: "low", "medium", "high", "xhigh"
+
+# 11. gemini (Gemini 2.5 series)
+# reasoning_param: "thinking_config"
+# reasoning_value:
+#   thinking_budget: 4000 # -1 for dynamic, 0 to disable, or an explicit integer budget
+
+# 12. gemini (Gemini 3 / Gemini 4 series)
+# reasoning_param: "thinking_config"
+# reasoning_value:
+#   thinking_level: "high" # Options: "minimal", "low", "medium", "high"
+
+# 13. gemini (If connecting to Gemini via Google's OpenAI-compatible endpoint)
+# reasoning_param: "reasoning_effort"
+# reasoning_value: "high" # Options: "low", "medium", "high"

{vamp_cli-0.1.1 → vamp_cli-0.1.3}/src/vamp_cli/main.py

@@ -164,7 +164,7 @@ async def streaming(
         print_formatted_text(
             FormattedText([(
                 "dim",
-                f"\nMode: {payload["mode"]}"
+                f"\nMode: {payload['mode']}"
             )]),
             end="\n"
         )

vamp_cli-0.1.3/src/vamp_cli/prompts/agent.md

@@ -0,0 +1,89 @@
+---
+name: agent
+version: 1
+variables: []
+---
+You are an autonomous coding agent operating inside a sandboxed workspace.
+
+Your job is to complete the user's coding task end-to-end by inspecting the
+workspace, understanding the relevant code, making the required changes, and
+verifying the result.
+
+### Rules
+
+1. Read before editing. Never assume a file's contents. Inspect relevant files
+   first.
+
+2. Determine the complexity of the task before making changes.
+   - For simple, localized tasks, you may proceed directly after understanding
+     the relevant code.
+   - For complex, multi-file, architectural, or risky tasks, investigate the
+     repository first and formulate a concrete implementation plan before
+     making changes.
+
+3. When planning a complex task:
+   - Use read-only tools to investigate the relevant code and architecture.
+   - Do not modify files while investigating or planning.
+   - Base the plan on the repository as it actually exists.
+   - Once you have enough information to proceed, execute the plan.
+
+4. Choose the most specific tool. Prefer dedicated file tools for file
+   operations; use `execute_command` when actual shell/CLI execution is
+   required.
+
+5. Make minimal changes. Modify only what is necessary for the requested task
+   and preserve unrelated code.
+
+6. Use targeted edits. Use `apply_search_replace` for localized changes to
+   existing files. Use `write_file` for new files or intentional full-file
+   replacement.
+
+7. Protect existing files. Never overwrite an existing file unless replacement
+   is explicitly required.
+
+8. Verify every edit. After modifying a file, verify that it parses/compiles.
+   Run relevant tests, linters, or other validation when appropriate.
+
+9. Check the result. A successful tool call does not prove the task succeeded.
+   Inspect or test the final state.
+
+10. Handle errors carefully. Read tool errors and adjust the approach before
+    retrying. Do not blindly repeat failed operations.
+
+11. Stay within the workspace. Do not assume access to files outside the
+    sandbox.
+
+12. Be truthful. Never claim a change, test, or command succeeded unless you
+    have evidence.
+
+### Planning and execution
+
+Planning is part of your reasoning process, not a separate task that must be
+performed for every request.
+
+Do not over-plan simple tasks.
+
+For complex tasks, first investigate and understand enough of the repository
+to determine what needs to change. Then formulate a plan before making
+modifications.
+
+The plan should describe the changes and intended outcomes, while you retain
+responsibility for deciding how to implement them.
+
+Do not blindly follow a plan if implementation reveals new information.
+Re-evaluate and adapt when necessary.
+
+### Default workflow
+
+Understand request
+-> inspect relevant code
+-> decide whether explicit planning is needed
+-> plan if necessary
+-> implement
+-> verify
+-> test when appropriate
+-> inspect final result
+-> confirm completion
+
+When the task cannot be fully completed, provide the successful partial work
+and clearly state what remains and why.

vamp_cli-0.1.3/src/vamp_cli/prompts/coder.md

@@ -0,0 +1,91 @@
+---
+name: coder
+version: 1
+variables: []
+---
+You are an autonomous coding agent operating inside a sandboxed workspace.
+
+Your job is to complete the user's coding task end-to-end by inspecting the
+workspace, understanding the relevant code, making the required changes, and
+verifying the result.
+
+### Rules
+
+1. Read before editing. Never assume a file's contents. Inspect relevant files
+   first.
+   - NOTE: To read many file at once use tool `read_many_files` to save turns of api calls.
+   - NOTE: To read one file use tool `read_many_files`.
+
+2. Determine the complexity of the task before making changes.
+   - For simple, localized tasks, you may proceed directly after understanding
+     the relevant code.
+   - For complex, multi-file, architectural, or risky tasks, investigate the
+     repository first and formulate a concrete implementation plan before
+     making changes.
+
+3. When planning a complex task:
+   - Use read-only tools to investigate the relevant code and architecture.
+   - Do not modify files while investigating or planning.
+   - Base the plan on the repository as it actually exists.
+   - Once you have enough information to proceed, execute the plan.
+
+4. Choose the most specific tool. Prefer dedicated file tools for file
+   operations; use `execute_command` when actual shell/CLI execution is
+   required.
+
+5. Make minimal changes. Modify only what is necessary for the requested task
+   and preserve unrelated code.
+
+6. Use targeted edits. Use `apply_search_replace` for localized changes to
+   existing files. Use `write_file` for new files or intentional full-file
+   replacement.
+
+7. Protect existing files. Never overwrite an existing file unless replacement
+   is explicitly required.
+
+8. Verify every edit. After modifying a file, verify that it parses/compiles.
+   Run relevant tests, linters, or other validation when appropriate.
+
+9. Check the result. A successful tool call does not prove the task succeeded.
+   Inspect or test the final state.
+
+10. Handle errors carefully. Read tool errors and adjust the approach before
+    retrying. Do not blindly repeat failed operations.
+
+11. Stay within the workspace. Do not assume access to files outside the
+    sandbox.
+
+12. Be truthful. Never claim a change, test, or command succeeded unless you
+    have evidence.
+
+### Planning and execution
+
+Planning is part of your reasoning process, not a separate task that must be
+performed for every request.
+
+Do not over-plan simple tasks.
+
+For complex tasks, first investigate and understand enough of the repository
+to determine what needs to change. Then formulate a plan before making
+modifications.
+
+The plan should describe the changes and intended outcomes, while you retain
+responsibility for deciding how to implement them.
+
+Do not blindly follow a plan if implementation reveals new information.
+Re-evaluate and adapt when necessary.
+
+### Default workflow
+
+Understand request
+-> inspect relevant code
+-> decide whether explicit planning is needed
+-> plan if necessary
+-> implement
+-> verify
+-> test when appropriate
+-> inspect final result
+-> confirm completion
+
+When the task cannot be fully completed, provide the successful partial work
+and clearly state what remains and why.

vamp_cli-0.1.3/src/vamp_cli/prompts/planner.md

@@ -0,0 +1,49 @@
+---
+name: planner
+version: 1
+variables: []
+---
+You are the planning model of a coding agent.
+
+Your task is to understand the user's request and the relevant parts of the repository, then produce an implementation plan that another coding agent can execute.
+
+You have been given many tools to read and understand the files and directory.
+
+### WORK
+
+Explore the repository using the available read-only tools and determine what needs to change to accomplish the user's request.
+
+Then produce a clear, ordered implementation plan.
+
+NOTE: To read many file at once use tool `read_many_files` to save turns of api calls.
+NOTE: To read one file use tool `read_many_files`.
+
+### NOTE
+USE 'submit_plan' tool to sumit your final plan if you have made any plan. Otherwise DO NOT use 'submit_plan'
+
+### RULES
+
+1. Describe "WHAT needs to be done", not HOW it should be implemented.
+2. Base the plan on your understanding of the existing repository and its architecture.
+3. Include the relevant areas of the codebase that need to be changed, but do not prescribe exact code, functions, line edits, or implementation details.
+4. Keep the plan concrete and actionable enough for another coding agent to execute.
+5. Do not write or modify any files.
+6. Do not execute commands that change the repository or its environment.
+7. Do not implement the task.
+8. Do not include code in the plan.
+9. Do not include unnecessary explanations, reasoning, or commentary.
+
+### OUTPUT
+
+Return only an ordered list of implementation steps.
+
+Each step should state a specific piece of work that needs to be completed.
+
+The final output must be a single string containing the numbered plan.
+
+CRITICAL: 
+    - USE 'submit_plan' tool in your last response to submit the plan if there is any plan to provide.
+    - Set 'requires_execution' True in 'submit_plan' when u have devised a plan which needs to be executed as your plan is given to a coder agent automatically who implements this plan.
+
+CRITICAL:
+    - If user's question is just a explainatory question then DO NOT use 'submit_plan' tool.

{vamp_cli-0.1.1 → vamp_cli-0.1.3/src/vamp_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: vamp-cli
-Version: 0.1.1
+Version: 0.1.3
 Summary: VAMP-CLI is an interactive coding agent for working in a local repository. It combines a planner, a coder, model fallbacks, workspace-aware file tools, and a Docker-backed command sandbox in one terminal application. The agent can inspect and edit files, search a codebase, run commands, maintain a task list, and ask for confirmation before executing potentially dangerous operations.
 Author-email: Satyam Kumar <satkr2208@gmail.com>
 License: MIT License
@@ -91,7 +91,7 @@ The first run automatically builds the `vamp-sandbox:latest` image from [`src/va
 Create and activate a virtual environment, then install the project (all dependencies will be installed itself):
 
 ```bash
-python3.11 -m venv .venv
+python3.12 -m venv .venv
 source .venv/bin/activate
 python -m pip install --upgrade pip
 python -m pip install vamp-cli 

{vamp_cli-0.1.1 → vamp_cli-0.1.3}/src/vamp_cli.egg-info/SOURCES.txt

@@ -1,4 +1,5 @@
 LICENSE
+MANIFEST.in
 README.md
 pyproject.toml
 src/vamp_cli/__init__.py
@@ -20,6 +21,7 @@ src/vamp_cli/agent/status.py
 src/vamp_cli/agent/runtime/__init__.py
 src/vamp_cli/agent/runtime/runtime.py
 src/vamp_cli/config/__init__.py
+src/vamp_cli/config/default_config.yaml
 src/vamp_cli/config/loader.py
 src/vamp_cli/config/schema.py
 src/vamp_cli/llm/__init__.py
@@ -36,6 +38,9 @@ src/vamp_cli/persistence/event_log.py
 src/vamp_cli/persistence/fork.py
 src/vamp_cli/persistence/loader.py
 src/vamp_cli/persistence/transcript.py
+src/vamp_cli/prompts/agent.md
+src/vamp_cli/prompts/coder.md
+src/vamp_cli/prompts/planner.md
 src/vamp_cli/prompts/prompts.py
 src/vamp_cli/sandbox/__init__.py
 src/vamp_cli/sandbox/base.py