https://arran4.github.io/blog/tags/issue-management/Recent content in issue-management on Arrans Technical blogHugo -- gohugo.ioentechnicalblog123@arran4.com (Arran Ubels)technicalblog123@arran4.com (Arran Ubels)Arran Ubels. This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.Wed, 09 Sep 2026 12:26:55 +1000https://arran4.github.io/blog/post/2026/044-jules-management/Wed, 09 Sep 2026 12:26:55 +1000technicalblog123@arran4.com (Arran Ubels)https://arran4.github.io/blog/post/2026/044-jules-management/I use Jules as an asynchronous implementation worker, but the useful workflow is larger than Jules itself. The part that makes it practical is a separate management LLM that sits between me, GitHub, the implementation agent, and the durable issue history. This post describes how I currently work, why it works for me, where the human attention cost comes from, and how I want a management LLM to behave when it is dropped into a fresh environment with little or no prior conversational context.