summaryrefslogtreecommitdiff
path: root/gemfeed/2026-07-09-unveiling-hexai.gmi.tpl
diff options
context:
space:
mode:
Diffstat (limited to 'gemfeed/2026-07-09-unveiling-hexai.gmi.tpl')
-rw-r--r--gemfeed/2026-07-09-unveiling-hexai.gmi.tpl14
1 files changed, 7 insertions, 7 deletions
diff --git a/gemfeed/2026-07-09-unveiling-hexai.gmi.tpl b/gemfeed/2026-07-09-unveiling-hexai.gmi.tpl
index b3d68a34..d130aa1e 100644
--- a/gemfeed/2026-07-09-unveiling-hexai.gmi.tpl
+++ b/gemfeed/2026-07-09-unveiling-hexai.gmi.tpl
@@ -8,7 +8,7 @@ Hexai is an AI add-on for Helix. It speaks LSP, so it also works with other edit
Hexai has been an undercover pet project of mine since around mid-last year. As I write this it is at version `0.42.1`, so it has been quietly growing for a good while before this first proper write-up.
-=> https://codeberg.org/snonux/hexai Hexai source code
+=> https://github.com/snonux/hexai Hexai source code
=> https://helix-editor.com Helix editor
=> ./unveiling-hexai/01-logo.png Hexai logo
@@ -33,10 +33,10 @@ These are opinionated tools. They reflect how I work — Helix inside tmux, a te
The easiest way is to install the binaries with `go install`. Each binary is a separate `cmd/` package:
```sh
-go install codeberg.org/snonux/hexai/cmd/hexai@latest
-go install codeberg.org/snonux/hexai/cmd/hexai-lsp-server@latest
-go install codeberg.org/snonux/hexai/cmd/hexai-tmux-action@latest
-go install codeberg.org/snonux/hexai/cmd/ask@latest
+go install github.com/snonux/hexai/cmd/hexai@latest
+go install github.com/snonux/hexai/cmd/hexai-lsp-server@latest
+go install github.com/snonux/hexai/cmd/hexai-tmux-action@latest
+go install github.com/snonux/hexai/cmd/ask@latest
```
If you prefer to build from a checkout, Hexai uses Mage:
@@ -314,8 +314,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.
-=> https://codeberg.org/snonux/dotfiles/src/branch/master/prompts/skills/agent-task-management agent-task-management skill
-=> https://codeberg.org/snonux/dotfiles/src/branch/master/prompts/commands/work-on-tasks.md /work-on-tasks command
+=> https://github.com/snonux/dotfiles/src/branch/master/prompts/skills/agent-task-management agent-task-management skill
+=> https://github.com/snonux/dotfiles/src/branch/master/prompts/commands/work-on-tasks.md /work-on-tasks command
## Running multiple providers side by side