Built with ratatui + crossterm on top of a full async tokio event loop. Modal editing (Normal/Insert/Visual) with Spacemacs-style SPC leader keys, LSP support via rust-analyzer, syntax highlighting through syntect, and a streaming
Copilot agent panel that can read and edit files in your project.
The agent is sandboxed to your project root and all network calls go exclusively
to GitHub's Copilot endpoints — no telemetry, no analytics. CI runs cargo-audit,
cargo-deny, and GitHub code scanning on every push. Full network call inventory
is in SECURITY.md.
Largely AI-assisted build (Claude). Curious whether others have shipped
production tools this way and what the maintenance story looks like longer term.
MIT. Builds with a single `cargo build --release`.
I pasted by hand. Not sure why the hate. I solved a problem for myself that I failed to get right in Emacs or Neovim. It was a joy. Be kind man, the world needs love, I'm not selling you anything.
1. Posting content with obvious mistakes is low quality. Have you recognized it yet? It's clear you didn't read the Ai output before posting.
2. Primarily using HN for self promotion breaks the HN rules, as evidenced by your submission and comment history. Please review the Guidelines and FAQ linked at the bottom of most pages.
This is good. Thanks for feedback. I wasnt promoting myself, but a learning and amazement at the art of the possible with AI and some engineering. I thought this could help others. I did read it before, a few times.
Do you have any submissions that are not your stuff?
"promotion" is loosely interpreted on HN
You might also consider how your post history and other public content appears within the larger context of the claw spam that currently ongoing across HN, GitHub, Arxiv, and social media
Built with ratatui + crossterm on top of a full async tokio event loop. Modal editing (Normal/Insert/Visual) with Spacemacs-style SPC leader keys, LSP support via rust-analyzer, syntax highlighting through syntect, and a streaming
Copilot agent panel that can read and edit files in your project.
The agent is sandboxed to your project root and all network calls go exclusively to GitHub's Copilot endpoints — no telemetry, no analytics. CI runs cargo-audit, cargo-deny, and GitHub code scanning on every push. Full network call inventory is in SECURITY.md.
Largely AI-assisted build (Claude). Curious whether others have shipped production tools this way and what the maintenance story looks like longer term.
MIT. Builds with a single `cargo build --release`.
https://github.com/danebalia/forgiven
Your Ai hallucinated, automated posting by scripts or bots is against the rules
If you copy-pasted instead, you didn't even look to see the obvious mistake
I pasted by hand. Not sure why the hate. I solved a problem for myself that I failed to get right in Emacs or Neovim. It was a joy. Be kind man, the world needs love, I'm not selling you anything.
It's not hate, it's about keeping HN high quality
1. Posting content with obvious mistakes is low quality. Have you recognized it yet? It's clear you didn't read the Ai output before posting.
2. Primarily using HN for self promotion breaks the HN rules, as evidenced by your submission and comment history. Please review the Guidelines and FAQ linked at the bottom of most pages.
This is good. Thanks for feedback. I wasnt promoting myself, but a learning and amazement at the art of the possible with AI and some engineering. I thought this could help others. I did read it before, a few times.
> I wasnt promoting myself
Do you have any submissions that are not your stuff?
"promotion" is loosely interpreted on HN
You might also consider how your post history and other public content appears within the larger context of the claw spam that currently ongoing across HN, GitHub, Arxiv, and social media