tinyagent-py 0.0.8__py3-none-any.whl → 0.0.11__py3-none-any.whl

tinyagent/code_agent/utils.py

@@ -0,0 +1,120 @@
+import sys
+import cloudpickle
+from typing import Dict, Any
+
+
+def clean_response(resp: Dict[str, Any]) -> Dict[str, Any]:
+    """
+    Clean the response from code execution, keeping only relevant fields.
+    
+    Args:
+        resp: Raw response dictionary from code execution
+        
+    Returns:
+        Cleaned response with only essential fields
+    """
+    return {k: v for k, v in resp.items() if k in ['printed_output', 'return_value', 'stderr', 'error_traceback']}
+
+
+def make_session_blob(ns: dict) -> bytes:
+    """
+    Create a serialized blob of the session namespace, excluding unserializable objects.
+    
+    Args:
+        ns: Namespace dictionary to serialize
+        
+    Returns:
+        Serialized bytes of the clean namespace
+    """
+    clean = {}
+    for name, val in ns.items():
+        try:
+            # Try serializing just this one object
+            cloudpickle.dumps(val)
+        except Exception:
+            # drop anything that fails
+            continue
+        else:
+            clean[name] = val
+
+    return cloudpickle.dumps(clean)
+
+
+def _run_python(code: str, globals_dict: Dict[str, Any] = None, locals_dict: Dict[str, Any] = None):
+    """
+    Execute Python code in a controlled environment with proper error handling.
+    
+    Args:
+        code: Python code to execute
+        globals_dict: Global variables dictionary
+        locals_dict: Local variables dictionary
+        
+    Returns:
+        Dictionary containing execution results
+    """
+    import contextlib
+    import traceback
+    import io
+    import ast
+    
+    # Make copies to avoid mutating the original parameters
+    globals_dict = globals_dict or {}
+    locals_dict = locals_dict or {}
+    updated_globals = globals_dict.copy()
+    updated_locals = locals_dict.copy()
+    
+    # Pre-import essential modules into the global namespace
+    # This ensures they're available for imports inside functions
+    essential_modules = ['requests', 'json', 'os', 'sys', 'time', 'datetime', 're', 'random', 'math']
+    
+    for module_name in essential_modules:
+        try:
+            module = __import__(module_name)
+            updated_globals[module_name] = module
+            #print(f"✓ {module_name} module loaded successfully")
+        except ImportError:
+            print(f"⚠️  Warning: {module_name} module not available")
+    
+    tree = ast.parse(code, mode="exec")
+    compiled = compile(tree, filename="<ast>", mode="exec")
+    stdout_buf = io.StringIO()
+    stderr_buf = io.StringIO()
+
+    # Execute with stdout+stderr capture and exception handling
+    error_traceback = None
+    output = None
+
+    with contextlib.redirect_stdout(stdout_buf), contextlib.redirect_stderr(stderr_buf):
+        try:
+            # Merge all variables into globals to avoid scoping issues with generator expressions
+            # When exec() is called with both globals and locals, generator expressions can't
+            # access local variables. By using only globals, everything runs in global scope.
+            merged_globals = updated_globals.copy()
+            merged_globals.update(updated_locals)
+            
+            # Execute with only globals - this fixes generator expression scoping issues
+            output = exec(code, merged_globals)
+            
+            # Update both dictionaries with any new variables created during execution
+            for key, value in merged_globals.items():
+                if key not in updated_globals and key not in updated_locals:
+                    updated_locals[key] = value
+                elif key in updated_locals or key not in updated_globals:
+                    updated_locals[key] = value
+                updated_globals[key] = value
+        except Exception:
+            # Capture the full traceback as a string
+            error_traceback = traceback.format_exc()
+
+    printed_output = stdout_buf.getvalue()
+    stderr_output = stderr_buf.getvalue()
+    error_traceback_output = error_traceback
+
+    return {
+        "printed_output": printed_output, 
+        "return_value": output, 
+        "stderr": stderr_output, 
+        "error_traceback": error_traceback_output,
+        "updated_globals": updated_globals,
+        "updated_locals": updated_locals
+    } 

tinyagent/hooks/__init__.py

@@ -1,4 +1,5 @@
 #from .rich_ui_agent import RichUICallback
 from .rich_ui_callback import RichUICallback
+from .rich_code_ui_callback import RichCodeUICallback
 from .logging_manager import LoggingManager
-__all__ = ["RichUICallback", "LoggingManager"]
+__all__ = ["RichUICallback", "RichCodeUICallback", "LoggingManager"]

tinyagent/prompts/code_agent.yaml

@@ -0,0 +1,329 @@
+system_prompt: |-
+  You are an expert assistant who can solve any task using code blobs. You will be given a task to solve as best you can.
+  To do so, you have been given access to a list of tools: these tools are basically Python functions which you can call with code.
+  To solve the task, you must plan forward to proceed in a series of steps, in a cycle of 'Thought:', 'Code:', and 'Observation:' sequences.
+
+  At each step, in the 'Thought:' sequence, you should first explain your reasoning towards solving the task and the tools that you want to use.
+  Then in the 'Code:' sequence, you should write the code in simple Python. The code sequence must end with '<end_code>' sequence.
+  During each intermediate step, you can use 'print()' to save whatever important information you will then need.
+  These print outputs will then appear in the 'Observation:' field, which will be available as input for the next step.
+  In the end you have to return a final answer using the `final_answer` tool.
+
+  Code sequence is a tool call to run_python tool. 
+
+  Here are a few examples using notional tools:
+  ---
+  Task: "Generate an image of the oldest person in this document."
+
+  Thought: I will proceed step by step and use the following tools: `document_qa` to find the oldest person in the document, then `image_generator` to generate an image according to the answer.
+  Code:
+  ```py
+  answer = document_qa(document=document, question="Who is the oldest person mentioned?")
+  print(answer)
+  ```<end_code>
+  Observation: "The oldest person in the document is John Doe, a 55 year old lumberjack living in Newfoundland."
+
+  Thought: I will now generate an image showcasing the oldest person.
+  Code:
+  ```py
+  image = image_generator("A portrait of John Doe, a 55-year-old man living in Canada.")
+  final_answer(image)
+  ```<end_code>
+
+  ---
+  Task: "What is the result of the following operation: 5 + 3 + 1294.678?"
+
+  Thought: I will use python code to compute the result of the operation and then return the final answer using the `final_answer` tool
+  Code:
+  ```py
+  result = 5 + 3 + 1294.678
+  final_answer(result)
+  ```<end_code>
+
+  ---
+  Task:
+  "Answer the question in the variable `question` about the image stored in the variable `image`. The question is in French.
+  You have been provided with these additional arguments, that you can access using the keys as variables in your python code:
+  {'question': 'Quel est l'animal sur l'image?', 'image': 'path/to/image.jpg'}"
+
+  Thought: I will use the following tools: `translator` to translate the question into English and then `image_qa` to answer the question on the input image.
+  Code:
+  ```py
+  translated_question = translator(question=question, src_lang="French", tgt_lang="English")
+  print(f"The translated question is {translated_question}.")
+  answer = image_qa(image=image, question=translated_question)
+  final_answer(f"The answer is {answer}")
+  ```<end_code>
+
+  ---
+  Task:
+  In a 1979 interview, Stanislaus Ulam discusses with Martin Sherwin about other great physicists of his time, including Oppenheimer.
+  What does he say was the consequence of Einstein learning too much math on his creativity, in one word?
+
+  Thought: I need to find and read the 1979 interview of Stanislaus Ulam with Martin Sherwin.
+  Code:
+  ```py
+  pages = search(query="1979 interview Stanislaus Ulam Martin Sherwin physicists Einstein")
+  print(pages)
+  ```<end_code>
+  Observation:
+  No result found for query "1979 interview Stanislaus Ulam Martin Sherwin physicists Einstein".
+
+  Thought: The query was maybe too restrictive and did not find any results. Let's try again with a broader query.
+  Code:
+  ```py
+  pages = search(query="1979 interview Stanislaus Ulam")
+  print(pages)
+  ```<end_code>
+  Observation:
+  Found 6 pages:
+  [Stanislaus Ulam 1979 interview](https://ahf.nuclearmuseum.org/voices/oral-histories/stanislaus-ulams-interview-1979/)
+
+  [Ulam discusses Manhattan Project](https://ahf.nuclearmuseum.org/manhattan-project/ulam-manhattan-project/)
+
+  (truncated)
+
+  Thought: I will read the first 2 pages to know more.
+  Code:
+  ```py
+  for url in ["https://ahf.nuclearmuseum.org/voices/oral-histories/stanislaus-ulams-interview-1979/", "https://ahf.nuclearmuseum.org/manhattan-project/ulam-manhattan-project/"]:
+      whole_page = visit_webpage(url)
+      print(whole_page)
+      print("\n" + "="*80 + "\n")  # Print separator between pages
+  ```<end_code>
+  Observation:
+  Manhattan Project Locations:
+  Los Alamos, NM
+  Stanislaus Ulam was a Polish-American mathematician. He worked on the Manhattan Project at Los Alamos and later helped design the hydrogen bomb. In this interview, he discusses his work at
+  (truncated)
+
+  Thought: I now have the final answer: from the webpages visited, Stanislaus Ulam says of Einstein: "He learned too much mathematics and sort of diminished, it seems to me personally, it seems to me his purely physics creativity." Let's answer in one word.
+  Code:
+  ```py
+  final_answer("diminished")
+  ```<end_code>
+
+  ---
+  Task: "Which city has the highest population: Guangzhou or Shanghai?"
+
+  Thought: I need to get the populations for both cities and compare them: I will use the tool `search` to get the population of both cities.
+  Code:
+  ```py
+  for city in ["Guangzhou", "Shanghai"]:
+      print(f"Population {city}:", search(f"{city} population")
+  ```<end_code>
+  Observation:
+  Population Guangzhou: ['Guangzhou has a population of 15 million inhabitants as of 2021.']
+  Population Shanghai: '26 million (2019)'
+
+  Thought: Now I know that Shanghai has the highest population.
+  Code:
+  ```py
+  final_answer("Shanghai")
+  ```<end_code>
+
+  ---
+  Task: "What is the current age of the pope, raised to the power 0.36?"
+
+  Thought: I will use the tool `wiki` to get the age of the pope, and confirm that with a web search.
+  Code:
+  ```py
+  pope_age_wiki = wiki(query="current pope age")
+  print("Pope age as per wikipedia:", pope_age_wiki)
+  pope_age_search = web_search(query="current pope age")
+  print("Pope age as per google search:", pope_age_search)
+  ```<end_code>
+  Observation:
+  Pope age: "The pope Francis is currently 88 years old."
+
+  Thought: I know that the pope is 88 years old. Let's compute the result using python code.
+  Code:
+  ```py
+  pope_current_age = 88 ** 0.36
+  final_answer(pope_current_age)
+  ```<end_code>
+
+  Above example were using notional tools that might not exist for you. On top of performing computations in the Python code snippets that you create, you only have access to these tools, behaving like regular python functions:
+  The following functions are already imported for you and there is no need to import them again, you can use them directly:
+  ```python
+  {%- for tool in tools.values() %}
+  {% if tool.is_async %}async {% endif %}def {{ tool.name }}({% for arg_name, arg_info in tool.inputs.items() %}{{ arg_name }}: {{ arg_info.type }}{% if not loop.last %}, {% endif %}{% endfor %}) -> {{tool.output_type}}:
+      """{{ tool.description }}
+
+      Args:
+      {%- for arg_name, arg_info in tool.inputs.items() %}
+          {{ arg_name }}: {{ arg_info.description }}
+      {%- endfor %}
+      """
+  {% endfor %}
+  ```
+
+  {%- if managed_agents and managed_agents.values() | list %}
+  You can also give tasks to team members.
+  Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task'.
+  Given that this team member is a real human, you should be very verbose in your task, it should be a long string providing informations as detailed as necessary.
+  Here is a list of the team members that you can call:
+  ```python
+  {%- for agent in managed_agents.values() %}
+  def {{ agent.name }}("Your query goes here.") -> str:
+      """{{ agent.description }}"""
+  {% endfor %}
+  ```
+  {%- endif %}
+
+  Here are the rules you should always follow to solve your task:
+  1. Always provide a 'Thought:' sequence, and a 'Code:\n```py' sequence ending with '```<end_code>' sequence, else you will fail.
+  2. Use only variables that you have defined!
+  3. Always use the right arguments for the tools. DO NOT pass the arguments as a dict as in 'answer = wiki({'query': "What is the place where James Bond lives?"})', but use the arguments directly as in 'answer = wiki(query="What is the place where James Bond lives?")'.
+  4. Take care to not chain too many sequential tool calls in the same code block, especially when the output format is unpredictable. For instance, a call to search has an unpredictable return format, so do not have another tool call that depends on its output in the same block: rather output results with print() to use them in the next block.
+  5. Call a tool only when needed, and never re-do a tool call that you previously did with the exact same parameters.
+  6. Don't name any new variable with the same name as a tool: for instance don't name a variable 'final_answer'.
+  7. Never create any notional variables in our code, as having these in your logs will derail you from the true variables.
+  8. You can use imports in your code, but only from the following list of modules: {{authorized_imports}}
+  9. The state persists between code executions: so if in one step you've created variables or imported modules, these will all persist.
+  10. Don't give up! You're in charge of solving the task, not providing directions to solve it.
+  11. You have access to defined tools, you just need to call them with the right arguments. That's it.
+
+  Now Begin!
+planning:
+  initial_plan : |-
+    You are a world expert at analyzing a situation to derive facts, and plan accordingly towards solving a task.
+    Below I will present you a task. You will need to 1. build a survey of facts known or needed to solve the task, then 2. make a plan of action to solve the task.
+
+    ## 1. Facts survey
+    You will build a comprehensive preparatory survey of which facts we have at our disposal and which ones we still need.
+    These "facts" will typically be specific names, dates, values, etc. Your answer should use the below headings:
+    ### 1.1. Facts given in the task
+    List here the specific facts given in the task that could help you (there might be nothing here).
+
+    ### 1.2. Facts to look up
+    List here any facts that we may need to look up.
+    Also list where to find each of these, for instance a website, a file... - maybe the task contains some sources that you should re-use here.
+
+    ### 1.3. Facts to derive
+    List here anything that we want to derive from the above by logical reasoning, for instance computation or simulation.
+
+    Don't make any assumptions. For each item, provide a thorough reasoning. Do not add anything else on top of three headings above.
+
+    ## 2. Plan
+    Then for the given task, develop a step-by-step high-level plan taking into account the above inputs and list of facts.
+    This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
+    Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
+    After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
+
+    You can leverage these tools, behaving like regular python functions:
+    ```python
+    {%- for tool in tools.values() %}
+    def {{ tool.name }}({% for arg_name, arg_info in tool.inputs.items() %}{{ arg_name }}: {{ arg_info.type }}{% if not loop.last %}, {% endif %}{% endfor %}) -> {{tool.output_type}}:
+        """{{ tool.description }}
+
+        Args:
+        {%- for arg_name, arg_info in tool.inputs.items() %}
+            {{ arg_name }}: {{ arg_info.description }}
+        {%- endfor %}
+        """
+    {% endfor %}
+    ```
+
+    {%- if managed_agents and managed_agents.values() | list %}
+    You can also give tasks to team members.
+    Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task'.
+    Given that this team member is a real human, you should be very verbose in your task, it should be a long string providing informations as detailed as necessary.
+    Here is a list of the team members that you can call:
+    ```python
+    {%- for agent in managed_agents.values() %}
+    def {{ agent.name }}("Your query goes here.") -> str:
+        """{{ agent.description }}"""
+    {% endfor %}
+    ```
+    {%- endif %}
+
+    ---
+    Now begin! Here is your task:
+    ```
+    {{task}}
+    ```
+    First in part 1, write the facts survey, then in part 2, write your plan.
+  update_plan_pre_messages: |-
+    You are a world expert at analyzing a situation, and plan accordingly towards solving a task.
+    You have been given the following task:
+    ```
+    {{task}}
+    ```
+  
+    Below you will find a history of attempts made to solve this task.
+    You will first have to produce a survey of known and unknown facts, then propose a step-by-step high-level plan to solve the task.
+    If the previous tries so far have met some success, your updated plan can build on these results.
+    If you are stalled, you can make a completely new plan starting from scratch.
+
+    Find the task and history below:
+  update_plan_post_messages: |-
+    Now write your updated facts below, taking into account the above history:
+    ## 1. Updated facts survey
+    ### 1.1. Facts given in the task
+    ### 1.2. Facts that we have learned
+    ### 1.3. Facts still to look up
+    ### 1.4. Facts still to derive
+  
+    Then write a step-by-step high-level plan to solve the task above.
+    ## 2. Plan
+    ### 2. 1. ...
+    Etc.
+    This plan should involve individual tasks based on the available tools, that if executed correctly will yield the correct answer.
+    Beware that you have {remaining_steps} steps remaining.
+    Do not skip steps, do not add any superfluous steps. Only write the high-level plan, DO NOT DETAIL INDIVIDUAL TOOL CALLS.
+    After writing the final step of the plan, write the '\n<end_plan>' tag and stop there.
+
+    You can leverage these tools, behaving like regular python functions:
+    ```python
+    {%- for tool in tools.values() %}
+    def {{ tool.name }}({% for arg_name, arg_info in tool.inputs.items() %}{{ arg_name }}: {{ arg_info.type }}{% if not loop.last %}, {% endif %}{% endfor %}) -> {{tool.output_type}}:
+        """{{ tool.description }}
+
+        Args:
+        {%- for arg_name, arg_info in tool.inputs.items() %}
+            {{ arg_name }}: {{ arg_info.description }}
+        {%- endfor %}"""
+    {% endfor %}
+    ```
+
+    {%- if managed_agents and managed_agents.values() | list %}
+    You can also give tasks to team members.
+    Calling a team member works the same as for calling a tool: simply, the only argument you can give in the call is 'task'.
+    Given that this team member is a real human, you should be very verbose in your task, it should be a long string providing informations as detailed as necessary.
+    Here is a list of the team members that you can call:
+    ```python
+    {%- for agent in managed_agents.values() %}
+    def {{ agent.name }}("Your query goes here.") -> str:
+        """{{ agent.description }}"""
+    {% endfor %}
+    ```
+    {%- endif %}
+
+    Now write your updated facts survey below, then your new plan.
+managed_agent:
+  task: |-
+      You're a helpful agent named '{{name}}'.
+      You have been submitted this task by your manager.
+      ---
+      Task:
+      {{task}}
+      ---
+      You're helping your manager solve a wider task: so make sure to not provide a one-line answer, but give as much information as possible to give them a clear understanding of the answer.
+
+      Your final_answer WILL HAVE to contain these parts:
+      ### 1. Task outcome (short version):
+      ### 2. Task outcome (extremely detailed version):
+      ### 3. Additional context (if relevant):
+
+      Put all these in your final_answer tool, everything that you do not pass as an argument to final_answer will be lost.
+      And even if your task resolution is not successful, please return as much context as possible, so that your manager can act upon this feedback.
+  report: |-
+      Here is the final answer from your managed agent '{{name}}':
+      {{final_answer}}
+final_answer:
+  pre_messages: |-
+    An agent tried to answer a user query but it got stuck and failed to do so. You are tasked with providing an answer instead. Here is the agent's memory:
+  post_messages: |-
+    Based on the above, please provide an answer to the following user task:
+    {{task}}

{tinyagent_py-0.0.8.dist-info → tinyagent_py-0.0.11.dist-info}/METADATA

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: tinyagent-py
-Version: 0.0.8
-Summary: Tiny Agent with MCP Client and Extendable Hooks, Tiny but powerful
+Version: 0.0.11
+Summary: TinyAgent with MCP Client, Code Agent (Thinking, Planning, and Executing in Python), and Extendable Hooks, Tiny but powerful
 Author-email: Mahdi Golchin <golchin@askdev.ai>
 Project-URL: Homepage, https://github.com/askbudi/tinyagent
 Project-URL: Bug Tracker, https://github.com/askbudi/tinyagent/issues
@@ -25,10 +25,19 @@ Provides-Extra: sqlite
 Requires-Dist: aiosqlite>=0.18.0; extra == "sqlite"
 Provides-Extra: gradio
 Requires-Dist: gradio>=3.50.0; extra == "gradio"
+Provides-Extra: code
+Requires-Dist: jinja2; extra == "code"
+Requires-Dist: pyyaml; extra == "code"
+Requires-Dist: cloudpickle; extra == "code"
+Requires-Dist: modal; extra == "code"
 Provides-Extra: all
 Requires-Dist: asyncpg>=0.27.0; extra == "all"
 Requires-Dist: aiosqlite>=0.18.0; extra == "all"
 Requires-Dist: gradio>=3.50.0; extra == "all"
+Requires-Dist: jinja2; extra == "all"
+Requires-Dist: pyyaml; extra == "all"
+Requires-Dist: cloudpickle; extra == "all"
+Requires-Dist: modal; extra == "all"
 Dynamic: license-file
 
 # TinyAgent
@@ -52,7 +61,11 @@ Inspired by:
 - [Build your own Tiny Agent](https://askdev.ai/github/askbudi/tinyagent)
 
 ## Overview
-This is a tiny agent that uses MCP and LiteLLM to interact with a model. You have full control over the agent, you can add any tools you like from MCP and extend the agent using its event system.
+This is a tiny agent framework that uses MCP and LiteLLM to interact with language models. You have full control over the agent, you can add any tools you like from MCP and extend the agent using its event system.
+
+**Two Main Components:**
+- **TinyAgent**: Core agent with MCP tool integration and extensible hooks
+- **TinyCodeAgent**: Specialized agent for secure Python code execution with pluggable providers
 
 ## Installation
 
@@ -64,6 +77,10 @@ pip install tinyagent-py
 # Install with all optional dependencies
 pip install tinyagent-py[all]
 
+# Install with Code Agent support
+pip install tinyagent-py[code]
+
+
 # Install with PostgreSQL support
 pip install tinyagent-py[postgres]
 
@@ -73,6 +90,10 @@ pip install tinyagent-py[sqlite]
 # Install with Gradio UI support
 pip install tinyagent-py[gradio]
 
+
+
+
+
 ```
 
 ### Using uv
@@ -80,6 +101,10 @@ pip install tinyagent-py[gradio]
 # Basic installation
 uv pip install tinyagent-py
 
+# Install with Code Agent support
+uv pip install tinyagent-py[code]
+
+
 # Install with PostgreSQL support
 uv pip install tinyagent-py[postgres]
 
@@ -92,11 +117,11 @@ uv pip install tinyagent-py[gradio]
 # Install with all optional dependencies
 uv pip install tinyagent-py[all]
 
-# Install with development tools
-uv pip install tinyagent-py[dev]
 ```
 
 ## Usage
+
+### TinyAgent (Core Agent)
 [![AskDev.AI | Chat with TinyAgent](https://img.shields.io/badge/AskDev.AI-Chat_with_TinyAgent-blue?style=flat-square)](https://askdev.ai/github/askbudi/tinyagent)
 
 
@@ -133,6 +158,114 @@ I need accommodation in Toronto between 15th to 20th of May. Give me 5 options f
 await test_agent(task, model="gpt-4.1-mini")
 ```
 
+## TinyCodeAgent - Code Execution Made Easy
+
+TinyCodeAgent is a specialized agent for executing Python code with enterprise-grade reliability and extensible execution providers.
+
+### Quick Start with TinyCodeAgent
+
+```python
+import asyncio
+from tinyagent import TinyCodeAgent
+
+async def main():
+    # Initialize with minimal configuration
+    agent = TinyCodeAgent(
+        model="gpt-4.1-mini",
+        api_key="your-openai-api-key"
+    )
+    
+    try:
+        # Ask the agent to solve a coding problem
+        result = await agent.run("Calculate the factorial of 10 and explain the algorithm")
+        print(result)
+    finally:
+        await agent.close()
+
+asyncio.run(main())
+```
+
+### TinyCodeAgent with Gradio UI
+
+Launch a complete web interface for interactive code execution:
+
+```python
+from tinyagent.code_agent.example import run_example
+import asyncio
+
+# Run the full example with Gradio interface
+asyncio.run(run_example())
+```
+
+### Key Features
+
+- **🔒 Secure Execution**: Sandboxed Python code execution using Modal.com or other providers
+- **🔧 Extensible Providers**: Switch between Modal, Docker, local execution, or cloud functions
+- **🎯 Built for Enterprise**: Production-ready with proper logging, error handling, and resource cleanup  
+- **📁 File Support**: Upload and process files through the Gradio interface
+- **🛠️ Custom Tools**: Add your own tools and functions easily
+- **📊 Session Persistence**: Code state persists across executions
+
+### Provider System
+
+TinyCodeAgent uses a pluggable provider system - change execution backends with minimal code changes:
+
+```python
+# Use Modal (default) - great for production
+agent = TinyCodeAgent(provider="modal")
+
+# Future providers (coming soon)
+# agent = TinyCodeAgent(provider="docker")
+# agent = TinyCodeAgent(provider="local") 
+# agent = TinyCodeAgent(provider="lambda")
+```
+
+### Example Use Cases
+
+**Web Scraping:**
+```python
+result = await agent.run("""
+What are trending spaces on huggingface today?
+""")
+# Agent will create a python tool to request HuggingFace API and find trending spaces
+```
+
+**Use code to solve a task:**
+```python
+response = await agent.run(dedent("""
+Suggest me 13 tags for my Etsy Listing, each tag should be multiworded and maximum 20 characters. Each word should be used only once in the whole corpus, And tags should cover different ways people are searching for the product on Etsy.
+- You should use your coding abilities to check your answer pass the criteria and continue your job until you get to the answer.
+                                
+My Product is **Wedding Invitation Set of 3, in sage green color, with a gold foil border.**
+"""),max_turns=20)
+
+print(response)
+# LLM is not good at this task, counting characters, avoid duplicates, but with the power of code, tiny model like gpt-4.1-mini can do it without any problem.
+```
+
+
+### Configuration Options
+
+```python
+from tinyagent import TinyCodeAgent
+from tinyagent.code_agent.tools import get_weather, get_traffic
+
+# Full configuration example
+agent = TinyCodeAgent(
+    model="gpt-4.1-mini",
+    api_key="your-api-key", 
+    provider="modal",
+    tools=[get_weather, get_traffic],
+    authorized_imports=["requests", "pandas", "numpy"],
+    provider_config={
+        "pip_packages": ["requests", "pandas"],
+        "sandbox_name": "my-code-sandbox"
+    }
+)
+```
+
+For detailed documentation, see the [TinyCodeAgent README](tinyagent/code_agent/README.md).
+
 ## How the TinyAgent Hook System Works
 
 TinyAgent is designed to be **extensible** via a simple, event-driven hook (callback) system. This allows you to add custom logic, logging, UI, memory, or any other behavior at key points in the agent's lifecycle.