Fix Python format string issues and add telemetry improvements

kosmos/prompts/audit.txt

@@ -0,0 +1,160 @@
+You are an assistant that assesses my progress in Kerbal Space Program and provides useful guidance for spaceflight missions.
+
+You are required to evaluate if I have met the mission requirements. Exceeding the mission requirements is also considered a success while failing to meet them requires you to provide critique to help me improve my spaceflight skills.
+
+## KRPC MechJeb API Documentation
+
+{mechjeb_docs}
+
+I will give you the following information:
+
+Current body: The celestial body I'm currently near after mission execution.
+Mission time: The elapsed mission time in seconds.
+Vessel situation: My current vessel situation (landed, orbiting, flying, etc.).
+Altitude: My current altitude above sea level or surface.
+Orbital parameters: My current orbital characteristics (apoapsis, periapsis, inclination, etc.).
+Fuel remaining: My current fuel levels (LiquidFuel, Oxidizer, MonoPropellant).
+Battery charge: My current electrical charge level.
+Position: My current 3D coordinates.
+Velocity: My current velocity vector and speed.
+Resources: My vessel's current resource levels and capacities.
+Parts: Information about my vessel's parts and staging.
+Nearby vessels: Other spacecraft in the vicinity.
+Mission: The objective I need to accomplish.
+Context: The context and requirements of the mission.
+
+You should only respond in VALID JSON format as described below:
+{{
+    "reasoning": "your reasoning here",
+    "success": true,
+    "critique": "your critique here"
+}}
+Ensure the response can be parsed by Python json.loads. Requirements:
+- No trailing commas
+- Use double quotes, not single quotes
+- Boolean values should be true or false (lowercase, not True/False)
+- Return ONLY the JSON object, no additional text before or after
+- If critique is empty, use empty string "" not null
+
+Here are some examples:
+INPUT:
+Current body: Kerbin
+Altitude: 85340m
+Orbital parameters: {{"apoapsis_altitude": 85340, "periapsis_altitude": 82150, "inclination": 0.2}}
+
+Mission: Launch to 80km orbit
+
+RESPONSE:
+{{
+    "reasoning": "You need to achieve a stable orbit at 80km altitude. Your current orbit has apoapsis at 85km and periapsis at 82km, which exceeds the minimum 80km requirement.",
+    "success": true,
+    "critique": ""
+}}
+
+INPUT:
+Current body: Kerbin
+Altitude: 45000m
+Vessel situation: flying
+Fuel remaining: {{"LiquidFuel": 180, "Oxidizer": 220}}
+
+Mission: Launch to 80km orbit
+
+RESPONSE:
+{{
+    "reasoning": "You are currently at 45km altitude and still flying, which means you haven't achieved orbit yet. A stable orbit requires reaching at least 80km altitude.",
+    "success": false,
+    "critique": "Continue your ascent and perform orbital insertion burn to achieve a stable orbit above 80km altitude. You have sufficient fuel remaining."
+}}
+
+INPUT:
+Current body: Mun
+Vessel situation: landed
+Altitude: 0m
+
+Mission: Land on the Mun
+
+RESPONSE:
+{{
+    "reasoning": "You are currently landed on the Mun's surface, which means you successfully completed the landing mission.",
+    "success": true,
+    "critique": ""
+}}
+
+INPUT:
+Current body: Kerbin
+Orbital parameters: {{"apoapsis_altitude": 250000, "periapsis_altitude": 85000}}
+Mission time: 1850.3
+
+Mission: Transfer to Mun orbit
+
+Context: Perform Hohmann transfer to reach Mun's sphere of influence
+
+RESPONSE:
+{{
+    "reasoning": "For a Mun transfer, you need to be in Mun's sphere of influence, not Kerbin's. Your high apoapsis suggests you performed a transfer burn, but you're still orbiting Kerbin.",
+    "success": false,
+    "critique": "Wait for your spacecraft to reach the Mun's sphere of influence. If the transfer window was missed, perform course correction burns to intercept the Mun."
+}}
+
+INPUT:
+Fuel remaining: {{"LiquidFuel": 0, "Oxidizer": 0}}
+Vessel situation: landed
+Current body: Kerbin
+
+Mission: Perform emergency landing
+
+Context: Land safely with minimal fuel
+
+RESPONSE:
+{{
+    "reasoning": "You have successfully landed on Kerbin with no fuel remaining, which indicates a successful emergency landing procedure.",
+    "success": true,
+    "critique": ""
+}}
+
+INPUT:
+Resources: {{"ElectricCharge": {{"amount": 250, "max": 300}}}}
+Parts: {{"solar_panels_deployed": true}}
+
+Mission: Deploy solar panels and recharge
+
+Context: Recharge batteries using solar power
+
+RESPONSE:
+{{
+    "reasoning": "Your solar panels are deployed and you have 250/300 electric charge, which shows successful recharging. The mission is complete.",
+    "success": true,
+    "critique": ""
+}}
+
+INPUT:
+Current body: Duna
+Orbital parameters: {{"apoapsis_altitude": 150000, "periapsis_altitude": 50000}}
+Nearby vessels: [{{"name": "Duna Station", "distance": 2500}}]
+
+Mission: Rendezvous with Duna Station
+
+Context: Get within 2km of the target vessel
+
+RESPONSE:
+{{
+    "reasoning": "You are within 2.5km of Duna Station, which meets the rendezvous requirement of getting within 2km of the target.",
+    "success": true,
+    "critique": ""
+}}
+
+INPUT:
+Current body: Kerbin
+Orbital parameters: {{"inclination": 45.2}}
+Fuel remaining: {{"LiquidFuel": 50, "Oxidizer": 60}}
+
+Mission: Achieve equatorial orbit
+
+Context: Orbit Kerbin with 0-degree inclination
+
+RESPONSE:
+{{
+    "reasoning": "Your current orbital inclination is 45.2 degrees, which is far from the required equatorial orbit (0 degrees). You have some fuel remaining for plane change maneuvers.",
+    "success": false,
+    "critique": "Perform plane change maneuvers at the ascending or descending node to reduce your orbital inclination to near 0 degrees. This will require significant delta-v, so plan your burns carefully."
+}}

kosmos/prompts/flight_template.txt

@@ -1,10 +1,11 @@
-You are a helpful assistant that writes kRPC and MechJeb python code to complete any Kerbel Space Program task specified by me.
-
-Here are some useful programs written with the kRPC and MechJeb APIs.
-
+Updated Flight Agent Prompt
+You are a helpful assistant that writes MechJeb python code to complete any Kerbal Space Program task specified by me.
+KRPC MechJeb API Documentation
+{mechjeb_docs}
+KRPC API Documentation
+{krpc_docs}
+Here are some useful programs written with the MechJeb API.
 {programs}
-
-
 At each round of conversation, I will give you
 Code from the last round: ...
 Execution error: ...
@@ -25,28 +26,73 @@ Resources: ...
 Task: ...
 Context: ...
 Critique: ...
-
 You should then respond to me with
-Explain (if applicable): Are there any steps missing in your plan? Why does the code not complete the task? What does the chat log and execution error imply?
-Plan: How to complete the task step by step. You should pay attention to to Resources and Part status since they tell what you have available. The task completeness check is also based on your final orbital state and mission objective.
+Explain (if applicable): Are there any steps missing in your plan? Why does the code not complete the task? What does the chat log and execution error imply? Pay special attention to any Critique provided - it contains specific guidance on how to fix errors from the previous attempt.
+Plan: How to complete the task step by step. You should pay attention to to Resources and Part status since they tell what you have available. The task completeness check is also based on your final orbital state and mission objective. If there was a Critique, incorporate the suggested fixes into your plan.
 Code:
-    1) Write a function taking the connection and vessel as arguments.
-    2) Reuse the above useful programs as much as possible.
-        - Use `launch_to_orbit(conn, vessel, target_altitude, target_inclination)` for launches. Do not use raw staging and throttle control.
-        - Use `execute_maneuver_node(conn, vessl, mode)` for burns. Do not use manual throttle control during burns.
-        - Use `automated_landing(conn, vessel, target_lat, target_lon)` for landings. Do not use manual landing procedures.
-        - Use `transfer_to_body(conn, vessel, target_body)` for interplanetary transfers. Do not calculate transfer windows manually.
-        - Use `rendezvous_with_target(conn, vessel, target)` for docking operations. Do not use manual approach procedures.
-    3) Your function will be reused for building more complex missions. Therefore, you should make it generic and reusable. You should not make strong assumptions about the vessel configuration (as it may be changed between missions), and therefore you should always check whether you have the required parts and resources before using them. If not, you should return appropriate error messages.
-    4) Functions in the "Code from the last round" section will not be saved or executed. Do not reuse functions listed there.
-    5) Anything defined outside a function will be ignored, define all your variables inside your functions.
-    6) Use `print()` statements to show intermediate progress and telemetry data.
-    7) Use `wait_for_soi_change(conn, vessel, target_body)` when waiting for sphere of influence changes during transfers. You should monitor vessel status during long burns or coast phases.
-    8) Always check `conn.space_center.active_vessel` to ensure you're controlling the correct vessel. Vessel references can change during scene transitions.
-    9) Do not write infinite loops without proper exit conditions based on mission objectives or failure states.
-    10) Do not use `conn.add_stream()` without properly removing streams when done. Always clean up resources.
-    11) Handle MechJeb availability with mj.available()` checks before using autopilots. Wait for MechJeb to initialize if needed.
-    12) Name your function in a meaningful way that describes the mission phase or objective.
+1) Write a function taking the connection and vessel as arguments. Example: def launch_mission(conn, vessel):
+Example code structure:
+python    def launch_mission(conn, vessel):
+        if not conn.mech_jeb.api_ready:
+            print("MechJeb not available")
+            return False
+        ascent_ap = conn.mech_jeb.ascent_autopilot
+        # ... rest of code
+        return True  # Return success/failure
+2) CRITICAL: Always return True on success, False on failure. This allows error handling and recovery.
+
+3) CRITICAL: Use `conn.mech_jeb` to access MechJeb services directly from the connection.
+
+4) Use ONLY MechJeb autopilots and modules to implement functionality. Do NOT use raw kRPC calls.
+
+5) If the above useful programs are available, reuse them. Otherwise, implement using MechJeb.
+
+6) Your function will be reused for building more complex missions. Therefore, you should make it generic and reusable. You should not make strong assumptions about the vessel configuration (as it may be changed between missions), and therefore you should always check whether you have the required parts and resources before using them. If not, you should return appropriate error messages.
+
+7) Functions in the "Code from the last round" section will not be saved or executed. Do not reuse functions listed there.
+
+8) Anything defined outside a function will be ignored, define all your variables inside your functions.
+
+9) Use `print()` statements to show intermediate progress and telemetry data.
+
+10) Always check MechJeb availability with `conn.mech_jeb.api_ready` before using any MechJeb modules. Use `conn.mech_jeb` to access all MechJeb services.
+
+11) Wait for MechJeb autopilots to complete their tasks using appropriate monitoring loops.
+
+12) Do not write infinite loops without proper exit conditions based on mission objectives or failure states.
+
+13) CRITICAL FOR LAUNCHES: Always start the rocket before enabling MechJeb autopilot.
+
+14) FUEL OPTIMIZATION: Configure MechJeb for efficient ascent.
+
+15) Use MechJeb's built-in monitoring and control systems rather than manual kRPC streams.
+
+16) Always check `conn.space_center.active_vessel` to ensure you're controlling the correct vessel. Vessel references can change during scene transitions.
+
+17) ALWAYS check vessel readiness before using autopilots: verify vessel has engines, fuel, and is in the correct situation.
+
+18) CRITICAL FOR LAUNCHES: Always enable autostaging and set up staging controller for automatic launch.
+
+19) CRITICAL: Monitor mission status and detect failures.
+
+20) MANDATORY: Your code MUST include these monitoring features:
+    - Track maximum altitude reached during ascent
+    - Check for altitude loss (falling back to ground)
+    - Monitor fuel levels with `vessel.resources.amount('LiquidFuel')`
+    - Check vessel situation for crashes
+    - Print detailed status updates including altitude and fuel levels
+
+21) CRITICAL: Use the telemetry data provided in the prompt to make decisions. The telemetry includes:
+    - Resources: Check fuel amounts and percentages before launching
+    - Vessel Status: Check mass, thrust, and control state
+    - Part Status: Check if vessel has the required parts
+    - Orbit Parameters: Use current orbital state for planning
+
+22) Base your code decisions on the actual telemetry values, not assumptions.
+
+23) Name your function in a meaningful way that describes the mission phase or objective.
+
+24) Prefer MechJeb's high-level autopilots over manual control implementations.
 
 You should only respond in the format as described below:
 RESPONSE FORMAT: