search

hdresearch / nolita

Work with web-enabled agents quickly — whether running a quick task or bootstrapping a full-stack product.
https://nolita.ai
MIT License
79 stars 3 forks source link

bin: use nolitarc for server #92

Closed matildepark closed 3 weeks ago

matildepark commented 3 weeks ago

You shouldn't need to pass keys on the client side SDK every single time. Since Nolita is running on-device, it should just pull from nolita auth. This replaces all agent and HDR parameters with calls to nolitarc.

We also didn't have HDR integration in the browser endpoint, so I've added that.

I wish I knew how to not require any JSON at all, though. It looks like this now:

maru@keina ~> curl -X POST http://localhost:3000/browser/session/launch -H "Content-Type: application/json" --data "{}"
{"sessionId":"42a2b9c2-34b8-46ca-ad06-cf30c2f50527"}%
matildepark commented 3 weeks ago

Technically, this is an API change, but not on a core interface (i.e., our exported objects themselves), just a downstream API surface. I treat those as a bit more pliable and outside semver. What do you think?

AlephNotation commented 3 weeks ago

Im down with some semver flexibility