Fix action parser for nested bash ticks

[callmephilip]

The current action parser incorrectly parses actions that include nested bash commands in heredocs. Here's an example of this happening in the wild. This is problematic for documentation generation and probably some other spicy use cases.

This is an attempt at fixing this

[klieret]

Ah I see, yeah that's a bit problematic.
I appreciate you raising this and adding the PR!

However, my viewpoint is that the current implementation is correct, in that the model is told exactly what it has to expect and should realize itself what the problem is. It can still effectively do these edits in two steps (e.g., first inserting TRIPLEBACKTICKSbash and then following up with another sed command to turn them into real triple backticks).
Admittedly, that's not the most efficient way.

But I think this issue really points more towards maybe using a custom XML tag that is extremely unlikely to appear outside of this codebase.

[callmephilip]

yeah, this sounds reasonable. i'll take a newer version for a spin to see if the new prompt works

[doehyunbaek]

Just in case anyone needs it, this is the only code you need to support custom xml based action parsing (with config change of format_error_template). It's a single line change of regex.

class DefaultAgentXML(DefaultAgent):
    def parse_action(self, response: dict) -> dict:
        """Parse the action from the message. Returns the action."""
        actions = re.findall(r"<mini_swe_agent_bash>\n(.*?)\n</mini_swe_agent_bash>", response["content"], re.DOTALL)
        if len(actions) == 1:
            return {"action": actions[0].strip(), **response}
        raise FormatError(self.render_template(self.config.format_error_template, actions=actions))