messh

How is this not monopolistic behavior?

Bloat. I like Pi much better with it's minimalism

Ohh but there is and there always be struggle. Don't worry about it

I use a Mac at work and a pc w/vanilla KDE at home. And... I don't feel anything is less good with KDE? If anything I prefer that over modern Mac

How is this different than bwrap or srt and others? Im using bwrap to achieve read only everywhere and and write on pwd. Also pi and other coding agents all have sandboxing that work in similar way

If there are no summaries then when context is full messages need to get evicted. If doing so one by one then it would indeed destroy the cache. Of course... maybe the implementation evicted 50% of messages at once, I didnt verify in code

In Jev you pass options in the input and its output just gives some probability for each. Oai structured output just follows a schema. The exact output is still generated and there is no probability

this is for local apps

how do you decide to start a new agent, and when to kill? also... do you use some works-tealing style task board, or otherwise how would the agents get new tasks.

This is gonna be a hard name to google :)

"A n̈ew kind of AI"... yeah... join the pile :)

good skill. but why should all this repo e needed for a small MD file??

How is this better than say using bubblewrap sandbox solutions. Is it safer, is that the advantage?

What about AWS Bedrock??

TUIs also live where the rest of the interesting stuff happens, in the terninal. They don't force you to move to a different env

If you use the terminal a lot then TUIs keep you there wo the need to manage yet a other window in the OS. For e.g. you can run nvim in another pane in tmux.

Html has also some of these properties, targeting the browser. Don't get me wrong. I do like TUIs, they are light weight and compose very nicely with the rest of the terminal (eg tmux). Also, i generally prefer just cli commands over tuis when possible.

The downside is that... you don't get to brainstorm with the agent about ways to implement stuff. Architecture, design etc. It would feel like.. you're on your own. Of course you could just a regular chat interface alongside but theb you deal with two interfaces. Maybe this could be a target format for another chat agent that you talk to.

For eg. on a large codebase I do hierarchical review where higher level agents focus on modules and leafs on files. Each reports upwards a summary of its findings incl children summaries.

that's an amazing project! people always say why 6mb vs CC's 250mb even matter when you are calling out to LLMs hosted in the cloud. But... I regularly run hierarchies of agents with say 50-100 on a regular basis. So 650 vs 25050 ... is "can do" vs "cannot"

If you don't need GPU, check out https://shellbox.dev - it snapshots memory, processes. And you pay only for actual running time per minute

If you don't need GPU, check out https://shellbox.dev - it snapshots memory, processes. And you pay only for actual running time per minute

Im currently doing something like this. The agent wakes up automatically at the end of the day and runs it's interactive checks. Using https://shellbox.dev as substrate so it is independent of my own schedule.

I run a cron job, an agent sacas HNs and sends me potential interesting links via telegram bot. Using https://shellbox.dev cron, the box is up for a couple of minutes and im not paying for the rest

There are more creative ones. Check out https://shellbox.dev

The x2 instance has 8gb memory. They go up to x8. And if you don't use it say during a weekend, then you stop it and resume on Monday, not paying for that period

A box with 2vcpu, 4gb ram and 50gb hdd on https://shellbox.dev is $0.02/hr and you pay per minute only for what you use. Even using it 24/7 is like less than $15

For the microcm, take a look at https://shellbox.dev, se3ms like a good fit. Real linux, and very affordable

half have fewer... and.. half have more?