xonecas.io
5745
Sc

sacenox.github.io / commit 9393315

Add post: editor assist and Farol AI update

xonecas2026-05-24 93933159c7a13d9542c9707cfb41c8cbc666f4f6 parent 74eda76

1 file changed

_posts/2026-05-24-editor-assist-linux-desktop-use-and-farol-ai.md+125−0
@@ -0,0 +1,125 @@
1+---
2+layout: post
3+title: editor-assist-linux-desktop-use-and-farol-ai
4+description: Two tiny Pi-powered extensions landed, mini-coder got a lighter UI, and Farol AI lit up as a consulting project.
5+---
6+
7+# Editor Assist, Linux Desktop Use, and a Small Lighthouse for AI Consulting
8+
9+Last time, [cel-tui shipped and mini-coder got faster](/posts/cel-tui-shipped-and-mini-coder-got-faster/). Since then I did the obvious next thing: instead of leaving the agent safely inside one terminal app, I started poking holes into the rest of my tools.
10+
11+The result is two tiny extensions: one for **Neovim**, one for **Pi**. Both are intentionally small, slightly dangerous in the fun way, and built around the same idea: let the agent help exactly where I already am.
12+
13+## The scoreboard since May 12
14+
15+| Project | Commits | What changed |
16+| --- | ---: | --- |
17+| `mini-coder` | 6 | v0.6.3, lighter TUI state, better compaction boundaries, and cleaner git/session handling |
18+| `pi-linux-use` | 4 | New Pi extension for observe/action Linux desktop control |
19+| `vim-pi-complete` | 2 | New Neovim plugin for selection-based Pi edits |
20+| `farol-ai` | 6 | New Astro/Tailwind site for my AI consulting project |
21+| `cel-tui` | 0 | Quiet this round, which is what a UI foundation is allowed to be sometimes |
22+| **Total** | **18** | A totally normal amount of yak grooming |
23+
24+## vim-pi-complete: `:Pi` for selected text
25+
26+[`vim-pi-complete`](https://github.com/sacenox/vim-pi-complete) is a small Neovim plugin that copies the current visual selection, sends it to Pi in non-interactive mode, and replaces the selection with the model output.
27+
28+The workflow is deliberately simple:
29+
30+1. select some text in Neovim
31+2. run `:Pi make this clearer` or `:Pi refactor this`
32+3. wait while the editor briefly becomes a philosophical device
33+4. get the selection replaced
34+
35+There is no big UI yet, no continuation state, and no heroic abstraction layer. It passes file path, file name, the user prompt, and the selected text to `pi`, then tells the model to return only the exact replacement text.
36+
37+Tiny? Yes. Useful? Also yes. Dangerous? Only in the traditional "I let a robot rewrite my buffer" sense.
38+
39+## pi-linux-use: Pi can look at the desktop now
40+
41+[`pi-linux-use`](https://github.com/sacenox/pi-linux-use) is a proof-of-concept Pi extension for Linux desktop computer-use.
42+
43+It gives Pi two tools:
44+
45+- `desktop_observe` captures the visible desktop with KDE Spectacle and returns a screenshot image to vision-capable models
46+- `desktop_input` sends mouse and keyboard actions through `dotool`
47+
48+There is also a companion `linux-desktop-use` skill that teaches the agent the boring-but-important loop:
49+
50+```text
51+observe → act → observe → try not to click the wrong thing
52+```
53+
54+Coordinates are pixels in the latest screenshot, which keeps the first version very plain. It is currently KDE/Plasma Wayland-first, because that is the desktop in front of me and I enjoy finishing prototypes before turning them into portability conferences.
55+
56+The longer-term direction is still interesting: portal ScreenCast, PipeWire, better metadata, crop/zoom helpers, wait-for-change, maybe accessibility/OCR. But the first version is intentionally humble: screenshot plus input. A robot with eyes and a poking stick.
57+
58+## mini-coder v0.6.3: lighter UI, cleaner context
59+
60+[`mini-coder`](https://github.com/sacenox/mini-coder) kept moving and is now at **v0.6.3**.
61+
62+The main change is that the TUI display state is now separated from the model context. That lets the interface stay readable without treating every rendered detail as sacred prompt cargo. Tool calls can be displayed in a more compact way, thinking blocks can collapse into token estimates, and bash/read output does not need to turn the conversation pane into a landfill.
63+
64+A few other useful bits landed too:
65+
66+- compaction moved down into the agent core
67+- compacted messages are no longer saved back into session history
68+- git handling got consolidated, including the branch/dirty label
69+- the TUI got trimmed into a lighter conversation view
70+
71+This is the glamorous part of agent tooling where the product gets better because old tool output stops haunting the present. Very seasonal.
72+
73+## cel-tui: no drama is also a feature
74+
75+[`cel-tui`](https://github.com/sacenox/cel-tui) did not get new commits in this window. That is not a complaint.
76+
77+The useful update is indirect: mini-coder is now leaning on it harder, and the framework is staying out of the way. After the previous sprint of layout, rendering, components, docs, and package work, a quiet stretch where the app can build on top of it is exactly the kind of boring I like.
78+
79+The packages are still the foundation under this TUI pile, including `@cel-tui/core`, `@cel-tui/components`, and `@cel-tui/clew`.
80+
81+## Farol AI: lighting a consulting path
82+
83+I also started [`farol-ai`](https://github.com/sacenox/farol-ai), a small site for my new AI consulting project.
84+
85+It is built with Astro and Tailwind, with a straightforward Portuguese landing page around AI strategy, agents and automation, prototyping, and production architecture. I also added a design system pass, contact CTAs, and PostHog analytics so the site can be more than a decorative lighthouse JPEG in project form.
86+
87+This one is less about a package release and more about making the consulting work explicit: helping teams turn fuzzy AI ideas into scoped, buildable, production-minded systems.
88+
89+## Try the tiny things
90+
91+For the Neovim plugin:
92+
93+```bash
94+cd ~/.config/nvim/pack/local/start
95+git clone https://github.com/sacenox/vim-pi-complete.git
96+```
97+
98+Then restart Neovim, visually select text, and run:
99+
100+```vim
101+:Pi rewrite this with fewer weasel words
102+```
103+
104+For the Linux desktop Pi extension:
105+
106+```bash
107+git clone https://github.com/sacenox/pi-linux-use.git
108+cd pi-linux-use
109+pi
110+```
111+
112+You will need `spectacle` and `dotool` installed, then ask Pi to look at the desktop. If it clicks the wrong thing, naturally that is research.
113+
114+And the usual suspects:
115+
116+```bash
117+bun add -g mini-coder
118+mc
119+```
120+
121+- [`mini-coder`](https://github.com/sacenox/mini-coder)
122+- [`cel-tui`](https://github.com/sacenox/cel-tui)
123+- [`Farol AI`](https://github.com/sacenox/farol-ai)
124+
125+Next up: make the tiny integrations less tiny, keep mini-coder's context under control, and see how far the desktop-use loop can go before it starts demanding a clipboard budget.