Lightnews — Scholar-powered news

Hendrik Mans

@hmans.dev

220 followers 330 following 900 posts

Building useful playthings with Go, Svelte/SvelteKit, Kubernetes, NATS, and more. Occasional kitchen content.

Bullying = block.

he/him.

Posts Replies Media Videos

Hendrik Mans

@hmans.dev

Adding full-text search (with fuzzy search!) to #beans because I can 💪

A terminal window running "beans list -S "loggin~ OR user"", with beans showing a list of issues that contain the word "user" or something that fuzzily matches the faulty word "loggin"

December 9, 2025 at 5:01 PM

Hendrik Mans

@hmans.dev

100.0%!

December 9, 2025 at 9:10 AM

Hendrik Mans

@hmans.dev

The age of BeanQL beckons. #beans

❯ beans query '{ beans(filter: { type: ["milestone"], status: ["todo"] }) { id title children { id title type } }}'
{
"data": {
"beans": [
{
"id": "chatto-03l2",
"title": "Phase 3: Beta",
"children": [
{
"id": "chatto-69g6",
"title": "Explore NATS server clustering",
"type": "task"
},
{
"id": "chatto-hlr4",
"title": "Explore hosted service",
"type": "task"
},
{
"id": "chatto-z7js",
"title": "Migration from embedded to standalone NATS",
"type": "task"

December 8, 2025 at 10:14 PM

Hendrik Mans

@hmans.dev

Beans and Claude are such a great team. Instead of whipping up a plan that will be long forgotten the very next session, just put it into a bean, and it'll stick around until you want to iterate on or implement it.

---
title: Refactor prompt command to use text/template
status: todo
type: task
created_at: 2025-12-08T20:16:08Z
updated_at: 2025-12-08T20:16:08Z
---

## Summary

Refactor the `beans prompt` generation to use Go's `text/template` package instead of
string builders and manual string concatenation.

## Motivation

The current implementation likely uses `strings.Builder` or similar manual string
construction, which can be harder to read, maintain, and modify. Using `text/template` would:

- Make the output format more declarative and easier to understand
- Separate the template structure from the data logic
- Make it easier to customize or extend the prompt format in the future
- Follow Go best practices for text generation

## Checklist

- [ ] Review the current `beans prompt` implementation to understand its structure
- [ ] Create a template file or embedded template string for the prompt output
- [ ] Refactor the command to use `text/template` with appropriate data structures
- [ ] Ensure the output remains identical to the current implementation
- [ ] Add/update tests to verify the refactored code produces correct output

December 8, 2025 at 8:25 PM

Hendrik Mans

@hmans.dev

And if you're now thinking "Wait, what? *This* is the big thing that hmans has been teasing for weeks?", fret not, for I do actually have something else in the works. Something much bigger. Something that I think you're going to enjoy quite a lot.

Stay tuned \o/

December 8, 2025 at 3:37 PM

Hendrik Mans

@hmans.dev

You can also ask your agent to file new issues, sort existing issues into meaningful epics or milestones, or just straight-out ask it what it thinks you should work on next. There's even a "beans roadmap" command that will generate a markdown roadmap document based on your issue data!

December 8, 2025 at 3:37 PM

Hendrik Mans

@hmans.dev

If you're using a coding agent, you can teach it to use Beans, too. Beans will give your agent a birds-eye view of your project, significantly increasing its capabilities to reason about the planned work. With the extra context provided, your agents will deliver even better results, automatically.

December 8, 2025 at 3:37 PM

Hendrik Mans

@hmans.dev

First and foremost, Beans is an issue tracker that stores its data in your project directory (one markdown file per issue, perfect for version control), and provides a set of human-facing CLI commands to interact with that data, including a fully-featured interactive TUI.

December 8, 2025 at 3:37 PM

Hendrik Mans

@hmans.dev

It's my birthday, but today *you* get the presents!

Introducing "Beans", a CLI-based, flat-file issue tracker designed for humans and their robot friends. 🫘

Track your work right in your repo, using the CLI. And if you work with coding agents, supercharge them with a full picture of your project!