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

you can ask structured output for probabilities...not that they necessarily mean anything.

In theory Jev “calibrates” the probabilities, meaning a probability of 20% is optimized to happen near 20% of the time, which as you point out traditional models with schemas do NOT optimize for at all

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??

A public repo is the easiest way to share something like this.

Nah that would be a link to a gist

I suppose that’s also reasonable, though this particular repo also hosts evals and other content related to the skill. So a gist seems like it would be an addition, not a replacement.

If its on github, you can add it directly to your claude via the claude marketplace and manage updates within claude (or set it to auto-update)

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.