Could you make it use Parakeet? That's an offline model that runs very quickly even without a GPU, so you could get much lower latency than using an API.
literally just 'git rebase origin/main' to insert new commits to main into my branch history prior to the commits I made. No rewrites of later commits required if there are no conflicts. You seem to have an extreme misunderstanding of how git works.
What you and I consider routine work, someone who works with mostly Webdev or might consider extremely difficult. There a lot of programmers who have never used a Linux shell, or know much about networking beyond TCP, or used Linux before outside of a uni class 20 years ago.
Installing it on your PC or laptop puts your personal data and ISP subscription at risk, while installing it in a hosted VM yourself requires a bunch of Linux security and networking knowledge or else you'll get pwned pretty much immediately (https://youtu.be/40SnEd1RWUU). So this service is giving you a VM already set up with a security baseline.
At my workplace we now use Claude Code to parse written specs and source code, search through JIRA, and draft, refine and organize tickets (using the JIRA API via a CLI tool). Way faster than through the UI.
However as you point out we have no program-accessible source of data on who stakeholders, contributors, managers, etc. are and have to write a lot of that ourselves. For a smaller business perhaps one could write all of that down in an accessible way to improve this but for a large dynamic business it seems very difficult.
The evidence has shown that this thinking is flawed - disruption of jobs in an industry causes a slow, wrenching, scarring adjustment process that increases the load on welfare programs and makes quality of life broadly worse: https://www.npr.org/2025/02/11/g-s1-47352/why-economists-got...
Look at the problems South Korea is having, where there are not enough young people to support and care for the elderly. Elders face economic hardship and the healthcare system is buckling under load.
Issues, CI, and downloads for built binaries aren't part of vanilla Git. CI in particular can be hard if you make a multi-platform project and don't want to have to buy a new mac every few years.
I have worked at organizations where most engineering and many product decisions were made bottom-up, through written RFDs and ADRs, and horizontal conversations between lead, staff and principal engineers. The tradeoff is that it can take weeks, months or years to both agree or schedule work on larger projects, where other (especially small) organizations might take hours to weeks.