summaryrefslogtreecommitdiff
path: root/gemfeed/2026-07-09-unveiling-hexai.html
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2026-07-08 17:26:52 +0300
committerPaul Buetow <paul@buetow.org>2026-07-08 17:26:52 +0300
commitbd5739c1af3cb9a01063bbb94ec7fc278ee3aa5c (patch)
tree57bd8bd78b7fd75e5e24d8833d63e910bc6ad032 /gemfeed/2026-07-09-unveiling-hexai.html
parent299b76764642626394aa1a369a1ef1d5de4e37db (diff)
Update content for html
Diffstat (limited to 'gemfeed/2026-07-09-unveiling-hexai.html')
-rw-r--r--gemfeed/2026-07-09-unveiling-hexai.html5
1 files changed, 5 insertions, 0 deletions
diff --git a/gemfeed/2026-07-09-unveiling-hexai.html b/gemfeed/2026-07-09-unveiling-hexai.html
index 7a80391a..ddf76ec0 100644
--- a/gemfeed/2026-07-09-unveiling-hexai.html
+++ b/gemfeed/2026-07-09-unveiling-hexai.html
@@ -366,6 +366,11 @@ Urgency: 7.8
Tags: agent
</pre>
<br />
+<span>This is where it becomes useful for agentic coding. There is an agent skill and a slash command built on top of <span class='inlinecode'>ask</span>: the <span class='inlinecode'>agent-task-management</span> skill knows how to read and update the <span class='inlinecode'>ask</span> task list, and the <span class='inlinecode'>/work-on-tasks</span> command uses that skill to work through a whole backlog on its own — pick the next actionable task, hand it to a fresh sub-agent, mark it done, and continue until nothing actionable is left. That is pretty useful after a planning session where you created a bunch of tasks with their proper dependencies set: point the agent at the project, run <span class='inlinecode'>/work-on-tasks</span>, and it chews through the queue one task at a time.</span><br />
+<br />
+<a class='textlink' href='https://codeberg.org/snonux/dotfiles/src/branch/master/prompts/skills/agent-task-management'>agent-task-management skill</a><br />
+<a class='textlink' href='https://codeberg.org/snonux/dotfiles/src/branch/master/prompts/commands/work-on-tasks.md'>/work-on-tasks command</a><br />
+<br />
<h2 style='display: inline' id='running-multiple-providers-side-by-side'>Running multiple providers side by side</h2><br />
<br />
<span>One feature I use more than I expected: per-surface model lists. In <span class='inlinecode'>config.toml</span> you can configure several providers or models for the same entry point, and Hexai fans the request out to all of them in parallel.</span><br />