I can see you're A/B testing some different hero text.
I got:
> Write a config, not a conversation
Which I found let me wondering - "What is this thing?"
I refreshed a few times to the variations, and while some were better, I feel like your hero could do with being less pithy, and more plain explanation of what it is.
So I'm the creator of botctl which I created to satisfy my personal need for running many agents on a cron style loop. The whole premise is you don't need to be there to chat with the agent for it to do it's job.
I'm definitely not A/B testing anything, it just cycles through a couple titles I thought conveyed the project well. The sub-title directly under it explains it pretty clearly, would you agree with that?
> Manage persistent AI bots with a terminal dashboard, web UI, and declarative configuration.
There's also an interactive emulation of the TUI directly next to both titles in the hero.
22 comments
I got:
> Write a config, not a conversation
Which I found let me wondering - "What is this thing?" I refreshed a few times to the variations, and while some were better, I feel like your hero could do with being less pithy, and more plain explanation of what it is.
I'm definitely not A/B testing anything, it just cycles through a couple titles I thought conveyed the project well. The sub-title directly under it explains it pretty clearly, would you agree with that?
> Manage persistent AI bots with a terminal dashboard, web UI, and declarative configuration.
There's also an interactive emulation of the TUI directly next to both titles in the hero.
https://kern-ai.com/
I made botctl explicitly to not have to talk to my agents, I wanted them running autonomously based on their BOT.md file's prompt / goals / skills.
This was my main motivation to create this