mito-ai 0.1.38__py3-none-any.whl → 0.1.40__py3-none-any.whl

mito_ai/__init__.py

@@ -14,6 +14,14 @@ from mito_ai.settings.urls import get_settings_urls
 from mito_ai.rules.urls import get_rules_urls
 from mito_ai.auth.urls import get_auth_urls
 from mito_ai.streamlit_preview.urls import get_streamlit_preview_urls
+
+# Sometimes matplotlib figures do not show up in the notebook with this warning: 
+# UserWarning: FigureCanvasAgg is non-interactive, and thus cannot be shown
+# I believe that streamlit is reconfiguring the matplotlib settings and this is happening as a result.
+# For now, we just set the backend to inline, so that the figures show up again
+import os
+os.environ['MPLBACKEND'] = 'inline'
+
 try:
     from _version import __version__
 except ImportError:

mito_ai/_version.py

@@ -1,4 +1,4 @@
 # This file is auto-generated by Hatchling. As such, do not:
 #   - modify
 #   - track in version control e.g. be sure to add to .gitignore
-__version__ = VERSION = '0.1.38'
+__version__ = VERSION = '0.1.40'

mito_ai/app_builder/handlers.py

@@ -4,7 +4,7 @@
 import os
 import time
 import logging
-from typing import Any, Union
+from typing import Any, Union, Optional
 import zipfile
 import tempfile
 from mito_ai.utils.create import initialize_user
@@ -147,11 +147,16 @@ class AppBuilderHandler(BaseWebSocketHandler):
             self.log.info("JWT token validation successful")
             
         try:
-
             notebook_path = str(notebook_path) if notebook_path else ""
-            success_flag, app_path, result_message = await streamlit_handler(notebook_path)
-            if not success_flag or app_path is None:
-                raise Exception(result_message)
+
+            app_directory = os.path.dirname(notebook_path)
+            app_path = os.path.join(app_directory, "app.py")
+
+            if not os.path.exists(app_path):
+                success_flag, app_path_result, result_message = await streamlit_handler(notebook_path)
+                if not success_flag or app_path_result is None:
+                    raise Exception(result_message)
+                app_path = app_path_result
 
             deploy_url = await self._deploy_app(app_path, jwt_token)
 
@@ -271,15 +276,15 @@ class AppBuilderHandler(BaseWebSocketHandler):
         except requests.exceptions.RequestException as e:
             self.log.error(f"Error during API request: {e}")
             if hasattr(e, 'response') and e.response is not None:
-                try:
-                    error_detail = e.response.json()
-                    self.log.error(f"Server error details: {error_detail}")
-                except:
-                    self.log.error(f"Server response: {e.response.text}")
-            raise Exception(f"Deployment failed: {str(e)}")
+                error_detail = e.response.json()
+                self.log.error(f"Server error details: {error_detail}")
+                if 'error' in error_detail:
+                    raise Exception(error_detail['error'])
+                raise
         except Exception as e:
             self.log.error(f"Error during deployment: {str(e)}")
             raise
+        raise RuntimeError("Unexpected error in _deploy_app")
 
     async def _upload_app_to_s3(self, app_path: str, presigned_url: str) -> requests.Response:
         """Upload the app to S3 using the presigned URL."""

mito_ai/completions/handlers.py

@@ -46,7 +46,7 @@ from mito_ai.completions.completion_handlers.agent_execution_handler import get_
 from mito_ai.completions.completion_handlers.agent_auto_error_fixup_handler import get_agent_auto_error_fixup_completion
 from mito_ai.utils.telemetry_utils import identify
 
-FALLBACK_MODEL = "gpt-4.1"  # Default model to use for safety
+FALLBACK_MODEL = "gpt-5"  # Default model to use for safety
 
 # The GlobalMessageHistory is responsible for updating the message histories stored in the .mito/ai-chats directory.
 # We create one GlobalMessageHistory per backend server instance instead of one per websocket connection so that the

mito_ai/completions/prompt_builders/agent_system_message.py

@@ -52,9 +52,6 @@ Format:
         code_summary: str
         cell_type: 'code' | 'markdown'
     }}
-    get_cell_output_cell_id: None,
-    next_steps: None,
-    analysis_assumptions: None
 }}
 
 Important information:
@@ -64,7 +61,7 @@ Important information:
 4. The code_summary must be a very short phrase (1–5 words maximum) that begins with a verb ending in "-ing" (e.g., "Loading data", "Filtering rows", "Calculating average", "Plotting revenue"). Avoid full sentences or explanations—this should read like a quick commit message or code label, not a description.
 5. Important: Only use the CELL_UPDATE tool if you want to add/modify a notebook cell in response to the user's request. If the user is just sending you a friendly greeting or asking you a question about yourself, you SHOULD NOT USE A CELL_UPDATE tool because it does not require modifying the notebook. Instead, just use the FINISHED_TASK response.
 6. The assumptions is an optional list of critical assumptions that you made about the data or analysis approach. The assumptions you list here will be displayed to the user so that they can confirm or correct the assumptions. For example: ["NaN values in the impressions column represent 0 impressions", "Only crashes with pedestrian or cyclist fatalities are considered fatal crashes", "Intervention priority combines both volume and severity to identify maximum impact opportunities"].
-7. Only include important data and analytical assumptions that if incorrect would fundamentally change your analysis conclusions. These should be data handling decisions, methodological choices, and definitional boundaries. Do not include: obvious statements ("Each record is counted once"), result interpretation guidance ("Gaps in the plot represent zero values"), display choices ("Data is sorted for clarity"), internal reasoning ("Bar chart is better than line plot"), or environment assumptions ("Library X is installed"). Prioritize quality over quantity - include only the most critical assumptions or None if there are no critical assumptions made in this step that have not already be shared with the user. If you ever doubt whether an assumption is critical enough to be shared with the user as an assumption, don't include it. Most messages should not include an assumption. 
+7. Only include important data and analytical assumptions that if incorrect would fundamentally change your analysis conclusions. These should be data handling decisions, methodological choices, and definitional boundaries. Do not include: obvious statements ("Each record is counted once"), result interpretation guidance ("Gaps in the plot represent zero values"), display choices ("Data is sorted for clarity"), internal reasoning ("Bar chart is better than line plot"), or environment assumptions ("Library X is installed"). Prioritize quality over quantity - include only the most critical assumptions or omit the field entirely if there are no critical assumptions made in this step that have not already be shared with the user. If you ever doubt whether an assumption is critical enough to be shared with the user as an assumption, don't include it. Most messages should not include an assumption. 
 8. Do not include the same assumption or variations of the same assumption multiple times in the same conversation. Once you have presented the assumption to the user, they will already have the opportunity to confirm or correct it so do not include it again.
 
 #### Cell Addition:
@@ -81,9 +78,6 @@ Format:
         code_summary: str
         cell_type: 'code' | 'markdown'
     }}
-    get_cell_output_cell_id: None,
-    next_steps: None,
-    analysis_assumptions: None
 }}
 
 Important information:
@@ -93,7 +87,7 @@ Important information:
 4. code_summary must be a very short phrase (1–5 words maximum) that begins with a verb ending in "-ing" (e.g., "Loading data", "Filtering rows", "Calculating average", "Plotting revenue"). Avoid full sentences or explanations—this should read like a quick commit message or code label, not a description.
 5. The cell_type should only be 'markdown' if there is no code to add. There may be times where the code has comments. These are still code cells and should have the cell_type 'code'. Any cells that are labeled 'markdown' will be converted to markdown cells by the user.
 6. The assumptions is an optional list of critical assumptions that you made about the data or analysis approach. The assumptions you list here will be displayed to the user so that they can confirm or correct the assumptions. For example: ["NaN values in the impressions column represent 0 impressions", "Only crashes with pedestrian or cyclist fatalities are considered fatal crashes", "Intervention priority combines both volume and severity to identify maximum impact opportunities"].
-7. Only include important data and analytical assumptions that if incorrect would fundamentally change your analysis conclusions. These should be data handling decisions, methodological choices, and definitional boundaries. Do not include: obvious statements ("Each record is counted once"), result interpretation guidance ("Gaps in the plot represent zero values"), display choices ("Data is sorted for clarity"), internal reasoning ("Bar chart is better than line plot"), or environment assumptions ("Library X is installed"). Prioritize quality over quantity - include only the most critical assumptions or None if there are no critical assumptions made in this step that have not already be shared with the user. If you ever doubt whether an assumption is critical enough to be shared with the user as an assumption, don't include it. Most messages should not include an assumption. 
+7. Only include important data and analytical assumptions that if incorrect would fundamentally change your analysis conclusions. These should be data handling decisions, methodological choices, and definitional boundaries. Do not include: obvious statements ("Each record is counted once"), result interpretation guidance ("Gaps in the plot represent zero values"), display choices ("Data is sorted for clarity"), internal reasoning ("Bar chart is better than line plot"), or environment assumptions ("Library X is installed"). Prioritize quality over quantity - include only the most critical assumptions or omit the field entirely if there are no critical assumptions made in this step that have not already be shared with the user. If you ever doubt whether an assumption is critical enough to be shared with the user as an assumption, don't include it. Most messages should not include an assumption. 
 8. Do not include the same assumption or variations of the same assumption multiple times in the same conversation. Once you have presented the assumption to the user, they will already have the opportunity to confirm or correct it so do not include it again.
 
 <Cell Modification Example>
@@ -133,17 +127,14 @@ Convert the transaction_date column to datetime and then multiply the total_pric
 Output:
 {{
     type: 'cell_update',
-    cell_type: 'code',
+    message: "I'll convert the transaction_date column to datetime and multiply total_price by the multiplier.",
     cell_update: {{
-        type: 'modification'
+        type: 'modification',
         id: 'c68fdf19-db8c-46dd-926f-d90ad35bb3bc',
         code: "import pandas as pd\\nsales_df = pd.read_csv('./sales.csv')\\nloan_multiplier = 1.5\\nsales_df['transaction_date'] = pd.to_datetime(sales_df['transaction_date'])\\nsales_df['total_price'] = sales_df['total_price'] * sales_multiplier",
         code_summary: "Converting the transaction_date column",
         cell_type: 'code'
-    }},
-    get_cell_output_cell_id: None,
-    next_steps: None,
-    analysis_assumptions: None
+    }}
 }}
 
 </Cell Modification Example>
@@ -184,17 +175,14 @@ Graph the total_price for each sale
 Output:
 {{
     type: 'cell_update',
-    message: "I'll create a graph with using matplotlib with sale `index` on the x axis and `total_price` on the y axis.",
+    message: "I'll create a graph using matplotlib with sale index on the x axis and total_price on the y axis.",
     cell_update: {{
-        type: 'add'
-        index: 2
-        code: "import matplotlib.pyplot as plt\n\nplt.bar(sales_df.index, sales_df['total_price'])\nplt.title('Total Price per Sale')\nplt.xlabel('Transaction Number')\nplt.ylabel('Sales Price ($)')\nplt.show()"
+        type: 'new',
+        index: 2,
+        code: "import matplotlib.pyplot as plt\n\nplt.bar(sales_df.index, sales_df['total_price'])\nplt.title('Total Price per Sale')\nplt.xlabel('Transaction Number')\nplt.ylabel('Sales Price ($)')\nplt.show()",
         code_summary: "Plotting total_price",
-        code_summary: "Plotting total_price"
-    }},
-    get_cell_output_cell_id: None,
-    next_steps: None,
-    analysis_assumptions: None
+        cell_type: 'code'
+    }}
 }}
 
 </Cell Addition Example>
@@ -208,10 +196,7 @@ When you want to get a base64 encoded version of a cell's output, respond with t
 {{
     type: 'get_cell_output',
     message: str,
-    get_cell_output_cell_id: str,
-    cell_update: None,
-    next_steps: Optional[List[str]],
-    analysis_assumptions: Optional[List[str]]
+    get_cell_output_cell_id: str
 }}
 
 Important information:
@@ -228,10 +213,7 @@ When you have completed the user's task, respond with a message in this format:
 {{
     type: 'finished_task',
     message: str,
-    get_cell_output_cell_id: None,
-    cell_update: None,
-    next_steps: Optional[List[str]],
-    analysis_assumptions: None
+    next_steps: Optional[List[str]]
 }}
 
 Important information:
@@ -249,8 +231,6 @@ Important information:
 {{
     type: 'finished_task',
     message: "Revenue analysis complete: total sales reached $2.3M with 34% growth in Q4[MITO_CITATION:abc123:2-3], while premium products generated 67% of profit margins[MITO_CITATION:xyz456:5]. The customer segmentation workflow identified three distinct buying patterns driving conversion rates[MITO_CITATION:def456:8-12].",
-    get_cell_output_cell_id: None,
-    cell_update: None,
     next_steps: ["Graph sales by product category", "Identify seasonal patterns in data", "Find the top 3 performing products"]
 }}
 
@@ -263,11 +243,7 @@ User message: "Hi"
 Output:
 {{
     type: 'finished_task',
-    message: "Hey there! I'm Mito AI. How can I help you today?",
-    get_cell_output_cell_id: None,
-    cell_update: None,
-    next_steps: None,
-    analysis_assumptions: None
+    message: "Hey there! I'm Mito AI. How can I help you today?"
 }}
 
 </Finished Task Example 2>
@@ -327,12 +303,11 @@ Output:
     type: 'cell_update',
     message: "I'll calculate two new variables all_time_high_date and all_time_high_price.",
     cell_update: {{
-        type: 'add'
-        index: 2
-        code: "all_time_high_row_idx = tesla_stock_prices_df['closing_price'].idxmax()\nall_time_high_date = tesla_stock_prices_df.at[all_time_high_row_idx, 'Date']\nall_time_high_price = tesla_stock_prices_df.at[all_time_high_row_idx, 'closing_price']"
+        type: 'new',
+        index: 2,
+        code: "all_time_high_row_idx = tesla_stock_prices_df['closing_price'].idxmax()\nall_time_high_date = tesla_stock_prices_df.at[all_time_high_row_idx, 'Date']\nall_time_high_price = tesla_stock_prices_df.at[all_time_high_row_idx, 'closing_price']",
         code_summary: "Calculating all time high"
-    }},
-    get_cell_output_cell_id: None
+    }}
 }}
 
 ### User Message 2
@@ -379,8 +354,6 @@ Output:
 {{
     type: 'finished_task', 
     message: "The all time high tesla stock closing price was $265.91 [MITO_CITATION:9c0d5fda-2b16-4f52-a1c5-a48892f3e2e8:2] on 2025-03-16 [MITO_CITATION:9c0d5fda-2b16-4f52-a1c5-a48892f3e2e8:1]",
-    get_cell_output_cell_id: None,
-    cell_update: None,
     next_steps: ["Create a visualization of Tesla's stock price over time", "Calculate the percentage change from the lowest to highest price", "Analyze the volatility of Tesla's stock"]
 }}
 

mito_ai/completions/prompt_builders/chat_name_prompt.py

@@ -3,13 +3,13 @@
 
 def create_chat_name_prompt(user_message: str, assistant_message: str) -> str:
     prompt = f"""Create a short name for the chat thread based on the first user message
-    and the first LLM response. Reply ONLY with the short title (max 40 chars). Don't add any extra text.
-    
-    Don't include that its a Python project in the chat.
+and the first LLM response. Reply ONLY with the short title (max 40 chars). Don't add any extra text.
+
+Don't include that its a Python project in the chat.
 
-    User Message: {user_message}
+User Message: {user_message}
 
-    Assistant Message: {assistant_message}
-    """
+Assistant Message: {assistant_message}
+"""
     
     return prompt

mito_ai/openai_client.py

@@ -35,7 +35,7 @@ from mito_ai.utils.telemetry_utils import (
     USER_KEY,
 )
 
-OPENAI_MODEL_FALLBACK = "gpt-4.1"
+OPENAI_MODEL_FALLBACK = "gpt-5"
 
 class OpenAIClient(LoggingConfigurable):
     """Provide AI feature through OpenAI services."""

mito_ai/streamlit_conversion/agent_utils.py

@@ -0,0 +1,116 @@
+# Copyright (c) Saga Inc.
+# Distributed under the terms of the GNU Affero General Public License v3.0 License.
+
+from typing import List
+import re
+from unidiff import PatchSet
+from mito_ai.streamlit_conversion.prompts.prompt_constants import MITO_TODO_PLACEHOLDER
+
+def extract_todo_placeholders(agent_response: str) -> List[str]:
+    """Extract TODO placeholders from the agent's response"""
+    return [line.strip() for line in agent_response.split('\n') if MITO_TODO_PLACEHOLDER in line]
+
+
+def apply_patch_to_text(text: str, diff: str) -> str:
+    """
+    Apply a *unified-diff* (git-style) patch to the given text and return
+    the updated contents.
+
+    Parameters
+    ----------
+    text : str
+        The original file contents.
+    diff : str
+        A unified diff that transforms *text* into the desired output.
+        The diff must reference exactly one file (the Streamlit app).
+
+    Returns
+    -------
+    str
+        The patched contents.
+
+    Raises
+    ------
+    ValueError
+        If the patch cannot be applied or references more than one file.
+    """
+    # Nothing to do
+    if not diff.strip():
+        return text
+
+    # Parse the patch
+    patch = PatchSet(diff.splitlines(keepends=True))
+
+    # We expect a single-file patch (what the prompt asks the model to emit)
+    if len(patch) != 1:
+        raise ValueError(
+            f"Expected a patch for exactly one file, got {len(patch)} files."
+        )
+
+    file_patch = patch[0]
+
+    original_lines = text.splitlines(keepends=True)
+    result_lines: List[str] = []
+
+    cursor = 0  # index in original_lines (0-based)
+
+    for hunk in file_patch:
+        # Copy unchanged lines before this hunk
+        while cursor < hunk.source_start - 1:
+            result_lines.append(original_lines[cursor])
+            cursor += 1
+
+        # Apply hunk line-by-line
+        for line in hunk:
+            if line.is_context:
+                result_lines.append(original_lines[cursor])
+                cursor += 1
+            elif line.is_removed:
+                cursor += 1  # Skip this line from the original
+            elif line.is_added:
+                # Ensure added line ends with newline for consistency
+                val = line.value
+                if not val.endswith("\n"):
+                    val += "\n"
+                result_lines.append(val)
+
+    # Copy any remaining lines after the last hunk
+    result_lines.extend(original_lines[cursor:])
+
+    return "".join(result_lines)
+
+
+def fix_diff_headers(diff: str) -> str:
+    """
+    The AI is generally not very good at counting the number of lines in the diff. If the hunk header has
+    an incorrect count, then the patch will fail. So instead we just calculate the counts ourselves, its deterministic.
+    """
+    lines = diff.split('\n')
+    
+    for i, line in enumerate(lines):
+        if line.startswith('@@'):
+            # Extract the starting line numbers
+            match = re.match(r'@@ -(\d+),\d+ \+(\d+),\d+ @@', line)
+            if match:
+                old_start = match.group(1)
+                new_start = match.group(2)
+                
+                # Count lines in this hunk
+                old_count = 0
+                new_count = 0
+                
+                for j in range(i + 1, len(lines)):
+                    next_line = lines[j]
+                    if next_line.startswith('@@') or next_line.startswith('---'):
+                        break
+                    if next_line.startswith(' ') or next_line.startswith('-'):
+                        old_count += 1
+                    if next_line.startswith(' ') or next_line.startswith('+'):
+                        new_count += 1
+                
+                # Replace the header with correct counts
+                lines[i] = f"@@ -{old_start},{old_count} +{new_start},{new_count} @@"
+    
+    return '\n'.join(lines)
+
+

mito_ai/streamlit_conversion/prompts/prompt_constants.py

@@ -0,0 +1,59 @@
+# Copyright (c) Saga Inc.
+# Distributed under the terms of the GNU Affero General Public License v3.0 License.
+
+MITO_TODO_PLACEHOLDER = "# MITO_TODO_PLACEHOLDER"
+
+unified_diff_instrucrions = f"""
+RESPONSE FORMAT: Return the changes you want to make to the streamlit app as a **unified diff (git-style patch)**:
+- Begin with a ````unified_diff` header and a ```` end header.
+- Then, include the standard header lines `--- a/app.py` and `+++ b/app.py`.
+- Show only the modified hunks; each hunk must start with an `@@` header with line numbers.
+- Within each hunk:
+  * Unchanged context lines start with a single space.
+  * Removed lines start with `-`.
+  * Added lines start with `+`.
+- If there are **no changes**, return an empty string.
+- Do not include the line numbers in your response.
+
+**IMPORTANT: For the hunk header, use `@@ -START_LINE,1 +START_LINE,1 @@` where we always use 1 as the count value. In a later step, the system will automatically calculate the correct counts.**
+
+<Example Response>
+
+In the example below, assume that the line of code `data_list = [` is on line 57 of the existing streamlit app.
+
+```unified_diff
+--- a/app.py
++++ b/app.py
+@@ -57,1 +57,1 @@
+ data_list = [
+     {{'id': 1, 'name': 'Item A', 'category': 'Type 1', 'value': 100}},
+     {{'id': 2, 'name': 'Item B', 'category': 'Type 2', 'value': 200}},
+-    {MITO_TODO_PLACEHOLDER}: Add remaining entries from notebook
++    {{'id': 3, 'name': 'Item C', 'category': 'Type 3', 'value': 300}},
++    {{'id': 4, 'name': 'Item D', 'category': 'Type 4', 'value': 400}},
++    {{'id': 5, 'name': 'Item E', 'category': 'Type 5', 'value': 500}},
++    {{'id': 6, 'name': 'Item F', 'category': 'Type 6', 'value': 600}},
++    {{'id': 7, 'name': 'Item G', 'category': 'Type 7', 'value': 700}},
++    {{'id': 8, 'name': 'Item H', 'category': 'Type 8', 'value': 800}},
++    {{'id': 9, 'name': 'Item I', 'category': 'Type 9', 'value': 900}},
++    {{'id': 10, 'name': 'Item J', 'category': 'Type 10', 'value': 1000}},
++    {{'id': 11, 'name': 'Item K', 'category': 'Type 11', 'value': 1100}},
++    {{'id': 12, 'name': 'Item L', 'category': 'Type 12', 'value': 1200}},
++    {{'id': 13, 'name': 'Item M', 'category': 'Type 13', 'value': 1300}},
++    {{'id': 14, 'name': 'Item N', 'category': 'Type 14', 'value': 1400}},
++    {{'id': 15, 'name': 'Item O', 'category': 'Type 15', 'value': 1500}},
++    {{'id': 16, 'name': 'Item P', 'category': 'Type 16', 'value': 1600}},
++    {{'id': 17, 'name': 'Item Q', 'category': 'Type 17', 'value': 1700}},
++    {{'id': 18, 'name': 'Item R', 'category': 'Type 18', 'value': 1800}},
++    {{'id': 19, 'name': 'Item S', 'category': 'Type 19', 'value': 1900}},
++    {{'id': 20, 'name': 'Item T', 'category': 'Type 20', 'value': 2000}},
++    {{'id': 21, 'name': 'Item U', 'category': 'Type 21', 'value': 2100}},
++    {{'id': 22, 'name': 'Item V', 'category': 'Type 22', 'value': 2200}},
++    {{'id': 23, 'name': 'Item W', 'category': 'Type 23', 'value': 2300}},
++    {{'id': 24, 'name': 'Item X', 'category': 'Type 24', 'value': 2400}},
++    {{'id': 25, 'name': 'Item Y', 'category': 'Type 25', 'value': 2500}}
+```
+</Example Response>
+
+Your response must consist **only** of valid unified-diff block.
+"""

mito_ai/streamlit_conversion/prompts/prompt_utils.py

@@ -0,0 +1,10 @@
+# Copyright (c) Saga Inc.
+# Distributed under the terms of the GNU Affero General Public License v3.0 License.
+
+def add_line_numbers_to_code(code: str) -> str:
+    """Add line numbers to the code"""
+    code_with_line_numbers = ""
+    for i, line in enumerate(code.split('\n'), 1):
+        code_with_line_numbers += f"{i:3d}: {line}\n"
+        
+    return code_with_line_numbers

mito_ai/streamlit_conversion/prompts/streamlit_app_creation_prompt.py

@@ -0,0 +1,45 @@
+# Copyright (c) Saga Inc.
+# Distributed under the terms of the GNU Affero General Public License v3.0 License.
+
+from mito_ai.streamlit_conversion.prompts.prompt_constants import MITO_TODO_PLACEHOLDER
+
+def get_streamlit_app_creation_prompt(notebook: dict) -> str:
+    """
+    This prompt is used to create a streamlit app from a notebook.
+    """
+    return f"""Convert the following Jupyter notebook into a Streamlit application.
+
+GOAL: Create a complete, runnable Streamlit app that accurately represents the notebook. It must completely convert the notebook. 
+
+TODO PLACEHOLDER RULES:
+If you decide to leave any TODOs, you must mark them with {MITO_TODO_PLACEHOLDER}. You should use {MITO_TODO_PLACEHOLDER} instead of comments like the following: 
+- # ... (include all mappings from the notebook)
+- # ... (include all violation codes from the notebook)
+- # Fill in the rest of the code here
+- # TODO: Add more code here
+- # TODO: Add the visualization code here
+
+For each TODO, use this exact format:
+{MITO_TODO_PLACEHOLDER}: <specific description of what needs to be added>
+
+IMPORTANT:
+- The app must still be RUNNABLE even with placeholders
+- Include enough sample data to show the structure
+- Do NOT use placeholders for small/medium content - include it directly
+- Do NOT use placeholders for file paths, imports, or core logic
+- Only use placeholders when absolutely necessary. Add all of the content directly as much as possible.
+
+<Example>
+If the notebook has a list of dictionaries with 50 entries, you would write:
+
+data = [
+    {{'id': 1, 'name': 'Item A', 'category': 'Type 1', 'value': 100}},
+    {{'id': 2, 'name': 'Item B', 'category': 'Type 2', 'value': 200}},
+    {MITO_TODO_PLACEHOLDER}: Add remaining entries from the data list
+]
+</Example>
+
+Notebook to convert:
+
+{notebook}
+"""

mito_ai/streamlit_conversion/prompts/streamlit_error_correction_prompt.py

@@ -0,0 +1,28 @@
+# Copyright (c) Saga Inc.
+# Distributed under the terms of the GNU Affero General Public License v3.0 License.
+
+from mito_ai.streamlit_conversion.prompts.prompt_constants import unified_diff_instrucrions
+from mito_ai.streamlit_conversion.prompts.prompt_utils import add_line_numbers_to_code
+
+def get_streamlit_error_correction_prompt(error: str, streamlit_app_code: str) -> str:
+    
+    existing_streamlit_app_code_with_line_numbers = add_line_numbers_to_code(streamlit_app_code)
+    
+    return f"""You've created a Streamlit app, but it has an error in it when you try to run it.
+
+Your job is to fix the error now. Only fix the specific error that you are instructed to fix now. Do not fix other error that that you anticipate. You will be asked to fix other errors later.
+
+{unified_diff_instrucrions}
+
+===============================================
+
+EXISTING STREAMLIT APP:
+{existing_streamlit_app_code_with_line_numbers}
+
+===============================================
+
+Please create a unified diff that corrects this error. Please keep your fix concise:
+{error}
+
+"""
+

mito_ai/streamlit_conversion/prompts/streamlit_finish_todo_prompt.py

@@ -0,0 +1,44 @@
+# Copyright (c) Saga Inc.
+# Distributed under the terms of the GNU Affero General Public License v3.0 License.
+
+from mito_ai.streamlit_conversion.prompts.prompt_constants import MITO_TODO_PLACEHOLDER, unified_diff_instrucrions
+from mito_ai.streamlit_conversion.prompts.prompt_utils import add_line_numbers_to_code
+
+def get_finish_todo_prompt(notebook: dict, existing_streamlit_app_code: str, todo_placeholder: str) -> str:
+  
+    existing_streamlit_app_code_with_line_numbers = add_line_numbers_to_code(existing_streamlit_app_code)
+    
+    return f"""You've already created the first draft of a Streamlit app representation of a Jupyter notebook, but you left yourself some TODOs marked as `{MITO_TODO_PLACEHOLDER}`. 
+
+**CRITICAL COMPLETION REQUIREMENT:**
+You have ONE and ONLY ONE opportunity to complete this TODO. If you do not finish the entire task completely, the application will be broken and unusable. This is your final chance to get it right.
+
+**COMPLETION RULES:**
+1. **NEVER leave partial work** - If the TODO asks for a list with 100 items, provide ALL 100 items
+2. **NEVER use placeholders** - This is your only opportunity to fulfill this TODO, so do not leave yourself another TODO.
+3. **NEVER assume "good enough"** - Complete the task to 100% satisfaction
+4. **If the task seems large, that's exactly why it needs to be done now** - This is your only chance
+
+**HOW TO DETERMINE IF TASK IS COMPLETE:**
+- If building a list/dictionary: Include ALL items that should be in the final data structure
+- If creating functions: Implement ALL required functionality
+- If converting a visualization: Copy over ALL of the visualization code from the notebook, including all styling and formatting.
+
+{unified_diff_instrucrions}
+
+===============================================
+
+Input Notebook that you are converting into the Streamlit app:
+{notebook}
+
+===============================================
+
+EXISTING STREAMLIT APP:
+{existing_streamlit_app_code_with_line_numbers}
+
+===============================================
+
+Please make the changes for this TODO. Only focus on this one TODO right now. You will be asked to fix others later:
+{todo_placeholder}
+
+"""