From bd5739c1af3cb9a01063bbb94ec7fc278ee3aa5c Mon Sep 17 00:00:00 2001
From: Paul Buetow
Date: Wed, 8 Jul 2026 17:26:52 +0300
Subject: Update content for html
---
gemfeed/2026-07-09-unveiling-hexai.html | 5 +++++
gemfeed/atom.xml | 7 ++++++-
index.html | 2 +-
uptime-stats.html | 24 ++++++++++++------------
4 files changed, 24 insertions(+), 14 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
+This is where it becomes useful for agentic coding. There is an agent skill and a slash command built on top of ask: the agent-task-management skill knows how to read and update the ask task list, and the /work-on-tasks 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 /work-on-tasks, and it chews through the queue one task at a time.
+
+agent-task-management skill
+/work-on-tasks command
+
Running multiple providers side by side
One feature I use more than I expected: per-surface model lists. In config.toml you can configure several providers or models for the same entry point, and Hexai fans the request out to all of them in parallel.
diff --git a/gemfeed/atom.xml b/gemfeed/atom.xml
index 64703cae..566ba90d 100644
--- a/gemfeed/atom.xml
+++ b/gemfeed/atom.xml
@@ -1,6 +1,6 @@
- 2026-07-08T17:18:58+03:00
+ 2026-07-08T17:26:44+03:00foo.zone feedTo be in the .zone!
@@ -373,6 +373,11 @@ Urgency: 7.8
Tags: agent
+This is where it becomes useful for agentic coding. There is an agent skill and a slash command built on top of ask: the agent-task-management skill knows how to read and update the ask task list, and the /work-on-tasks 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 /work-on-tasks, and it chews through the queue one task at a time.
+
+agent-task-management skill
+/work-on-tasks command
+
Running multiple providers side by side
One feature I use more than I expected: per-surface model lists. In config.toml you can configure several providers or models for the same entry point, and Hexai fans the request out to all of them in parallel.
diff --git a/index.html b/index.html
index 512e2e5e..344a2cce 100644
--- a/index.html
+++ b/index.html
@@ -13,7 +13,7 @@
Hello!
-This site was generated at 2026-07-08T17:19:04+03:00 by Gemtexter
+This site was generated at 2026-07-08T17:26:50+03:00 by Gemtexter
-This site was last updated at 2026-07-08T17:19:04+03:00
+This site was last updated at 2026-07-08T17:26:49+03:00
The following stats were collected via uptimed on all of my personal computers over many years and the output was generated by goprecords, the global uptime records stats analyser of mine.