summaryrefslogtreecommitdiff
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
parent299b76764642626394aa1a369a1ef1d5de4e37db (diff)
Update content for html
-rw-r--r--gemfeed/2026-07-09-unveiling-hexai.html5
-rw-r--r--gemfeed/atom.xml7
-rw-r--r--index.html2
-rw-r--r--uptime-stats.html24
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
</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 />
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 @@
<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
- <updated>2026-07-08T17:18:58+03:00</updated>
+ <updated>2026-07-08T17:26:44+03:00</updated>
<title>foo.zone feed</title>
<subtitle>To be in the .zone!</subtitle>
<link href="https://foo.zone/gemfeed/atom.xml" rel="self" />
@@ -373,6 +373,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 />
diff --git a/index.html b/index.html
index 512e2e5e..344a2cce 100644
--- a/index.html
+++ b/index.html
@@ -13,7 +13,7 @@
</p>
<h1 style='display: inline' id='hello'>Hello!</h1><br />
<br />
-<span class='quote'>This site was generated at 2026-07-08T17:19:04+03:00 by <span class='inlinecode'>Gemtexter</span></span><br />
+<span class='quote'>This site was generated at 2026-07-08T17:26:50+03:00 by <span class='inlinecode'>Gemtexter</span></span><br />
<br />
<span>Welcome to the foo.zone!</span><br />
<br />
diff --git a/uptime-stats.html b/uptime-stats.html
index 1d73e843..fc86798f 100644
--- a/uptime-stats.html
+++ b/uptime-stats.html
@@ -13,7 +13,7 @@
</p>
<h1 style='display: inline' id='my-machine-uptime-stats'>My machine uptime stats</h1><br />
<br />
-<span class='quote'>This site was last updated at 2026-07-08T17:19:04+03:00</span><br />
+<span class='quote'>This site was last updated at 2026-07-08T17:26:49+03:00</span><br />
<br />
<span>The following stats were collected via <span class='inlinecode'>uptimed</span> on all of my personal computers over many years and the output was generated by <span class='inlinecode'>goprecords</span>, the global uptime records stats analyser of mine.</span><br />
<br />
@@ -26,7 +26,7 @@
<br />
<a class='textlink' href='./gemfeed/2023-05-01-unveiling-guprecords:-uptime-records-with-raku.html'>Unveiling <span class='inlinecode'>guprecords.raku</span>: Uptime records with Raku (and also there is a version in Go now)</a><br />
<br />
-<span class='quote'>Uptime stats were last updated Wed 8 Jul 17:19:04 EEST 2026</span><br />
+<span class='quote'>Uptime stats were last updated Wed 8 Jul 17:26:50 EEST 2026</span><br />
<br />
<h2 style='display: inline' id='top-20-uptime-s-by-host'>Top 20 Uptime&#39;s by Host</h2><br />
<br />
@@ -141,10 +141,10 @@
| 10. | makemake | 81 | Linux 6.9.9-200.fc40.x86_64 | 2025-11-16 13:55 |
| 11. | uranus | 59 | NetBSD 10.1 | 2025-05-06 15:38 |
| 12. | pluto | 51 | Linux 3.2.0-4-amd64 | 2023-02-18 10:13 |
-| 13. | *fishfinger | 50 | OpenBSD 7.8 | 2026-07-07 23:34 |
-| 14. | mega15289 | 50 | Darwin 23.4.0 | 2024-05-28 18:14 |
-| 15. | *mega-m3-pro | 50 | Darwin 25.5.0 | 2026-07-08 14:04 |
-| 16. | *blowfish | 50 | OpenBSD 7.8 | 2026-07-07 23:31 |
+| 13. | mega15289 | 50 | Darwin 23.4.0 | 2024-05-28 18:14 |
+| 14. | *fishfinger | 50 | OpenBSD 7.8 | 2026-07-07 23:34 |
+| 15. | *blowfish | 50 | OpenBSD 7.8 | 2026-07-07 23:31 |
+| 16. | *mega-m3-pro | 50 | Darwin 25.5.0 | 2026-07-08 14:04 |
| 17. | t450 | 46 | FreeBSD 14.2-RELEASE | 2026-01-02 08:37 |
| 18. | phobos | 40 | Linux 3.4.0-CM-g1dd7cdf | 2023-02-18 10:13 |
| 19. | mega8477 | 40 | Darwin 13.4.0 | 2023-02-18 10:12 |
@@ -179,7 +179,7 @@
| 17. | tauceti-f | 108 | Linux 3.2.0-3-amd64 | 2021-07-26 16:48 |
| 18. | tauceti-e | 96 | Linux 3.2.0-4-amd64 | 2021-07-26 16:48 |
| 19. | callisto | 86 | Linux 4.0.4-303.fc22.x86_64 | 2021-07-26 16:48 |
-| 20. | *f0 | 85 | FreeBSD 15.1-RELEASE | 2026-07-08 14:00 |
+| 20. | *f1 | 85 | FreeBSD 15.1-RELEASE | 2026-07-08 14:00 |
+-----+----------------+-------+-----------------------------------+------------------+
</pre>
<br />
@@ -203,14 +203,14 @@
| 10. | *OpenBSD 7... | 110 |
| 11. | Darwin 13... | 40 |
| 12. | FreeBSD 5... | 25 |
-| 13. | Linux 2... | 22 |
-| 14. | Darwin 23... | 22 |
+| 13. | Darwin 23... | 22 |
+| 14. | Linux 2... | 22 |
| 15. | Darwin 24... | 22 |
| 16. | Darwin 21... | 17 |
| 17. | Darwin 15... | 15 |
| 18. | Darwin 22... | 12 |
-| 19. | *Darwin 25... | 11 |
-| 20. | Darwin 18... | 11 |
+| 19. | Darwin 18... | 11 |
+| 20. | *Darwin 25... | 11 |
+-----+----------------+-------+
</pre>
<br />
@@ -272,7 +272,7 @@
| 17. | Darwin 18... | 32 |
| 18. | Darwin 22... | 30 |
| 19. | Darwin 15... | 29 |
-| 20. | FreeBSD 13... | 25 |
+| 20. | FreeBSD 5... | 25 |
+-----+----------------+-------+
</pre>
<br />