the “software is solved” argument is a false dichotomy. many burdens of developing software are now trivial but many parts of developing software (like creating art or music) are so subjective and wouldn’t make sense to categorize as being solved
@gdb oai is incentivized to do this because token costs go down as open source models and harnesses catch up. the bottleneck is compute, not the model. with this thesis, why would one commit 1-3 years to oai as opposed to a compute provider?
@wangandrewd and I wrote some thoughts on agent harnesses, optionality, and where we believe the industry is headed. Read it here: https://t.co/OMlkh2NOnQ
@Valon_ai (8/n) gestalt is agnostic of whether you run locally or on k8s, whether you use sqlite, postgres, or mongodb, or whether you use okta or google for authn, as examples. and I think this composability is what will enhance developer productivity when building in the era of agents
(1/n) some background on why I started building a few months ago at @valon_ai. in january, when agentic coding starting gaining traction, we wanted to be able to connect agents to any tool, even if those tools didn't have MCPs or CLIs
i'm working on this thing called gestalt to solve the problem of agentic tooling and apps not being agnostic of harnesses or cloud/local environments
some docs at https://t.co/F04VJgjU7t, all of the code at https://t.co/FGviCwc8zK. lightweight demo below; more updates to come
@Valon_ai (7/n) gestalt takes a composable approach to building these types of systems. it supports authentication, authorization, storage, agent identities, and much more, but they are loaded outside of the core binary, and only if you express that you want them
i'm working on this thing called gestalt to solve the problem of agentic tooling and apps not being agnostic of harnesses or cloud/local environments
some docs at https://t.co/F04VJgjU7t, all of the code at https://t.co/FGviCwc8zK. lightweight demo below; more updates to come