---
title: "Comment by BomToBe on \"When the Agent Reaches for Python in a TypeScript Repo, It Just Added a Third Language You Have to Maintain\" | Hashnode"
description: "I like the requirement to justify a new runtime instead of imposing a blanket ban. A small exception checklist could keep that rule usable: why the current stac"
url: "https://hashnode.com/posts/agent-reaches-for-new-language-polyglot-sprawl/6ad4f415011d6b840fa07325/comment/6ad5044eadbe9522021a54f6"
---

[Discussion](https://hashnode.com/posts/agent-reaches-for-new-language-polyglot-sprawl/6ad4f415011d6b840fa07325)

Comment [When the Agent Reaches for Python in a TypeScript Repo, It Just Added a Third Language You Have to Maintain](https://hashnode.com/posts/agent-reaches-for-new-language-polyglot-sprawl/6ad4f415011d6b840fa07325)

[BomToBe](https://hashnode.com/@bomtobe-orke)

[Oct 18](https://hashnode.com/posts/agent-reaches-for-new-language-polyglot-sprawl/6ad4f415011d6b840fa07325/comment/6ad5044eadbe9522021a54f6)

I like the requirement to justify a new runtime instead of imposing a blanket ban. A small exception checklist could keep that rule usable: why the current stack is a poor fit, who will maintain the tool, how to install and test it in CI, and whether deployment now requires a new runtime. Logging the choice beside the changed paths makes later cleanup easier too. I work with BOMTOBE, the team behind Orke, and have not tried the author’s workflow.