hey if you are like me and use a lot of CLI AI tools right now you probably know this pain. lately whenever i want the agent to fix something or i need to explain a complex architecture in detail and discuss it i find myself completely lost in the middle of typing. like i literally lose my train of thought and forget what i was even gonna ask or prompt the agent by the time i'm halfway through typing it out lol
so i was thinking it would be great if we could just speak and voila the prompt gets sent to the AI. most apps do that now but the CLI doesn't really have a built in way to do it. or at least i didn't know how until now.
turns out you don't need to build anything. you just place your cursor right in the terminal and press the windows key + H at the exact same time. it pulls up the built in windows voice tool and you can just talk and it types everything right there. saved me so much headache today thought i should share.
so i was thinking it would be great if we could just speak and voila the prompt gets sent to the AI. most apps do that now but the CLI doesn't really have a built in way to do it. or at least i didn't know how until now.
turns out you don't need to build anything. you just place your cursor right in the terminal and press the windows key + H at the exact same time. it pulls up the built in windows voice tool and you can just talk and it types everything right there. saved me so much headache today thought i should share.
Forwarded from Life in Commits 💻 (Chaos)
hey if you are like me and use a lot of CLI AI tools right now you probably know this pain. lately whenever i want the agent to fix something or i need to explain a complex architecture in detail and discuss it i find myself completely lost in the middle of typing. like i literally lose my train of thought and forget what i was even gonna ask or prompt the agent by the time i'm halfway through typing it out lol
so i was thinking it would be great if we could just speak and voila the prompt gets sent to the AI. most apps do that now but the CLI doesn't really have a built in way to do it. or at least i didn't know how until now.
turns out you don't need to build anything. you just place your cursor right in the terminal and press the windows key + H at the exact same time. it pulls up the built in windows voice tool and you can just talk and it types everything right there. saved me so much headache today thought i should share.
so i was thinking it would be great if we could just speak and voila the prompt gets sent to the AI. most apps do that now but the CLI doesn't really have a built in way to do it. or at least i didn't know how until now.
turns out you don't need to build anything. you just place your cursor right in the terminal and press the windows key + H at the exact same time. it pulls up the built in windows voice tool and you can just talk and it types everything right there. saved me so much headache today thought i should share.
Life in Commits 💻
https://freebuff.com/cli
Been trying the free Buffer cli with DeepSeek V4 lately, and honestly it's been pretty good so far.
One thing I really like is the amount of tokens they give you. It's actually generous. U can do a ton of projects task with it without constantly thinking about running out of credits or limits, which is something I appreciate a lot.
So far, from the testing I've done, I've found it genuinely useful.
The only thing I'm kind of disappointed about is the permission system. You know how coding cli ai agents tools let you switch modes? Like, one mode where the agent asks for permission before writing or running scripts , and another where it can just go ahead and execute everything automatically.
In this case, you have to explicitly tell it upfront that you want a plan first. And to be fair, it does give you the plan. But after the third or fourth iteration, it kind of starts assuming that you agree with what it's doing and just continues from there also they only allow one session.
That's probably the only catchs I've found so far.
Other than that, honestly, it's been really good. The token limit alone makes it worth trying if you're building projects or experimenting with ideas.
Has anyone else been using it? Curious to hear what your experience has been.
One thing I really like is the amount of tokens they give you. It's actually generous. U can do a ton of projects task with it without constantly thinking about running out of credits or limits, which is something I appreciate a lot.
So far, from the testing I've done, I've found it genuinely useful.
The only thing I'm kind of disappointed about is the permission system. You know how coding cli ai agents tools let you switch modes? Like, one mode where the agent asks for permission before writing or running scripts , and another where it can just go ahead and execute everything automatically.
In this case, you have to explicitly tell it upfront that you want a plan first. And to be fair, it does give you the plan. But after the third or fourth iteration, it kind of starts assuming that you agree with what it's doing and just continues from there also they only allow one session.
That's probably the only catchs I've found so far.
Other than that, honestly, it's been really good. The token limit alone makes it worth trying if you're building projects or experimenting with ideas.
Has anyone else been using it? Curious to hear what your experience has been.
Forwarded from Jebenna
proof2.png
332.2 KB
In the mooring I did one insane experiment and it worked. Now we can bypass our ISP CGNAT entirely and talk to each other without needing other third party apps :)
In the future hopefully If I found time I will build a CLI app for this. Stay tuned :)
In the future hopefully If I found time I will build a CLI app for this. Stay tuned :)
Did you know that Cursor lets you generate unlimited commit messages, even on the free plan?
This feature alone is one of the biggest reasons I still use Cursor.
I'm a big fan of writing commits using conventional commit formats like feat, fix, chore, and so on. I usually structure them with the type of change, a clear summary, and a more detailed description underneath.
It might sound like a small thing, but having well-structured commit messages makes a huge difference. It helps me quickly understand what changed, why it changed, and how the project evolved over time. And honestly, it also makes it much easier for AI agents to read the project history and navigate the codebase effectively.
A clean commit history isn't just about being organized—it's about making your project easier to understand for both humans and machines.
And have biggest impact on ur workflow.
This feature alone is one of the biggest reasons I still use Cursor.
I'm a big fan of writing commits using conventional commit formats like feat, fix, chore, and so on. I usually structure them with the type of change, a clear summary, and a more detailed description underneath.
It might sound like a small thing, but having well-structured commit messages makes a huge difference. It helps me quickly understand what changed, why it changed, and how the project evolved over time. And honestly, it also makes it much easier for AI agents to read the project history and navigate the codebase effectively.
A clean commit history isn't just about being organized—it's about making your project easier to understand for both humans and machines.
And have biggest impact on ur workflow.
Conventional Commit Format
<type>(<optional-scope>): <short description>
<optional body>
<optional footer(s)>
Forwarded from Beka (Beka)
Better Auth is joining Vercel!
Thank you everyone who has been part of this journey in so many different ways 🙏
More to come! Excited for what’s ahead ❤️
Thank you everyone who has been part of this journey in so many different ways 🙏
More to come! Excited for what’s ahead ❤️
There is a saying from the movie the matrix where neo says
As mental reset yeah he was right .
There is no spoon
As mental reset yeah he was right .
Finally got smth to brag about never thought I'd be committed to smth .
👍3