jrswab's comments

jrswab | 2 days ago | on: Show HN: Axe – A 12MB binary that replaces your AI framework

Not yet but is on the short list to implement. What would you need from a session for single purpose agents? I'm seeing it more as a way to track what's been done.

jrswab | 2 days ago | on: Show HN: Axe – A 12MB binary that replaces your AI framework

hahaha; this is what I was going for.

jrswab | 2 days ago | on: Show HN: Axe – A 12MB binary that replaces your AI framework

This is not an LLM but a Binary to run LLMs as single purpose agents that can chain together.

jrswab | 2 days ago | on: Show HN: Axe – A 12MB binary that replaces your AI framework

> how you would approach budget when using Axe

Great question and it's something that I've not dig into yet. But I see no problem adding a way to limit LLMs by tokens or something similar to keep the cost for the user within reason.

jrswab | 11 days ago | on: Show HN: Axe – A CLI for running single-purpose LLM agents

Me too! I just shared with a coworker that the binary is only 6.57MB and running in a Alpine Docker container is only 24MB.

jrswab | 11 days ago | on: Show HN: Axe – A CLI for running single-purpose LLM agents

Hi everyone, I built Axe because I got tired of the "everything is a chatbot" pattern in AI tooling.

Axe treats LLM agents like Unix programs. Each agent is a TOML config with a focused job such as a code reviewer, a log analyzer, or a commit message writer. You run them from the CLI, pipe data in, get results out. Chain them together. Trigger them from cron, git hooks, CI.

Whatever you already use.

Some things that make it different:

- No framework lock-in: it's a single binary with two dependencies

- Stdin piping: `git diff | axe run reviewer` just works

- Sub-agent delegation: agents can call other agents via tool use

- Persistent memory: agents remember across runs without you managing state (if you need)

- Path-sandboxed tools: file ops are locked to the agent's working directory

Written in Go because I wanted fast cold starts and easy distribution. No daemon or GUI.

This is early stage to solve a need I have. I would love feedback on the agent config format and the skill system.

What's missing? What would make you actually use this?

jrswab | 1 year ago | on: Show HN: A Minimalist Coffee Bean Rating System Built with Go and Htmx

This is a great thought. I'll have to do some planning around this. Though I'd assume if you don't like light roasts you'd not be buying them and then would have nothing to rate. But trusting the users to not "hate rate" may not be the bust idea.

jrswab | 1 year ago | on: Show HN: A Minimalist Coffee Bean Rating System Built with Go and Htmx

haha yes, thank you for sharing. I wanted to get out an MVP to see if people would actually want something like this. It was a balance between spending too much time making it perfect upfront vs. getting something out to test the desire for a site link this.

jrswab | 1 year ago | on: Show HN: A Minimalist Coffee Bean Rating System Built with Go and Htmx

Thanks for giving it a look! And thank you for the kind words

Yes, scaling is going to be in interesting problem to solve. I may need accounts for things in the future such as saving beans and making lists or something but for the functionality of rating and finding beans I want to stay account-less.

I love your suggestion about adding some gamification to the site. I'll have to think about how that could be done well in the context of coffee.

jrswab | 1 year ago | on: Show HN: A Minimalist Coffee Bean Rating System Built with Go and Htmx

The go-htmx-forge is the base for this web app :)

jrswab | 1 year ago | on: Show HN: A terminal tool for Logseq journal entries

I don't know but since obsidian uses plan text files like Logseq does you should be able to update the code a bit and point LSQ to your directory. My default it opens up the files in your $EDITOR

jrswab | 1 year ago | on: Show HN: A terminal tool for Logseq journal entries

Thank you for this! I'll check it out as I do want to add the ability to navigate to pages from with the TUI. And at some point add in search functionality since I use it a lot within the Logseq app.

jrswab | 1 year ago | on: Show HN: A terminal tool for Logseq journal entries

You're welcome! I'm glad it's not some niche thing that only I needed XD

If you have any idea that will make your workflow easier add an "issue" on GitHub so I can keep track of it.

jrswab | 1 year ago | on: Show HN: A terminal tool for Logseq journal entries

I'll add some to the repo when I get a chance.

jrswab | 1 year ago | on: Show HN: A terminal tool for Logseq journal entries

I don't know of any at the moment. That said I do want to add the ability to search pages and navigate links within the Logseq graph. This would have to be in the TUI as I don't want to maintain several plugins for various editors.

jrswab | 1 year ago | on: Show HN: A terminal tool for Logseq journal entries

If you run `lsq` without `-t` it will open with what you have defined as `$EDITOR`.

jrswab | 8 years ago | on: Working on own startup instead of an internship. How to make sure I'm learning?

In relation to my start-up now I've been challenged by learning the finical side of things. I know the tech and love the tech but all that money stuff has not come as easily. So taking the time to learn it all has been a bit of a challenge.

jrswab | 8 years ago | on: Working on own startup instead of an internship. How to make sure I'm learning?

I'm in the works on a start up as well. I think the best way to avoid stagnation is to challenge yourself. Back when I was looking for a job I had the option of two. One with a small company basically being the whole IT department and one with a big name company doing menial work. I picked the big company and kind of regret not going with the small to learn as much as I could have from the challenge.