Google explicitly allows this and documents how: https://antigravity.google/docs/cli/headless/

This is so weird, because using a script to invoke the agy cli is clearly using a "third party tool to access the service" !

I literally just wrote about exactly that https://nicktrevino.com/your-repository-is-your-swarm.html

> bingeineering

i'm gonna start using this

I just wrote about this.

Not this exactly, but how your repository can be your swarm, and essentially be your harness.

Using Gitea/GitHub Actions within your repo and agent runner containers allow you to have agents working in your repos 24/7. Not just that, but in a containerized world you can just link up their brains over some shared storage. Using Antigravity, this means you can share the `brain` and its conversation directory with your agent runners and they can get the entire history of everything.

While building it out it becomes apparent that we are just getting started!

Where did you write about this? I am interested in reading more.

I just submitted it last night on HN, actually. So it should be on my profile in my submissions. It's written more about my experience rather than as a tutorial, but I think it becomes clear how it should work.

For those interested, myself amongst:

- https://nicktrevino.com/your-repository-is-your-swarm.html

I enjoyed it, thank you for sharing and double thanks to Bluestein for surfacing it. Your point about declarative languages is interesting and mirrors my thoughts. Prompting is declarative even.

Related repo from them, mentioned in the readme as well: https://github.com/xoreaxeaxeax/asm-hall-of-shame

> Instruction latency analysis usually focuses on performance optimization—making code run as fast as possible. The Assembly Hall of Shame takes the opposite approach: searching for the absolute floor of single-instruction performance.

Fun stuff!

And already posted to HN a few days ago which is surely where this post originated from.

This reminds me of a related issue: http://iscaliforniaonfire.com/

perma.cc is great. Also check out their tools if you want to get your hands dirty with your own archival process: https://tools.perma.cc/

Here is some related software from many years back: https://ollydbg.de/Paperbak/index.html

Here's one method for this that I have bookmarked: https://miunau.com/posts/dynamic-text-contrast-in-css/

This is interesting. I really like the DSL. It is a little limited though, just because it works on the month-level only.

One thing that I think is missing is having different dates for transactions to occur. So like some things happen just once ever, or transactions on the last day of the month which shifts.

This just means the stats that are given by this app are a bit rough. Looking at the source it seems to estimate the projections. Not a bad thing, just something to note.

I recently translated my own script-based cash flow simulator to a web app as well, which might be interesting: https://nicktrevino.com/tools.cashflow-simulator.html

One last thing, if you haven't heard of Wails, and you like Golang, I recommend it when thinking about making a desktop version of a web app: https://wails.io/

Nice! I share a similar set of thoughts and ideals around configuration languages and I'm working on one as well. Mine has a very similar syntax, so you might be interested! You can find it if you dig through my comments.