thdxr

this is a 1 day old vibe coded experiment where i'm exploring some ideas

API support was never removed

this isn't true

it will use whatever small model there is in your provider

we had a fallback where we provided free small models if your provider did not have one (gpt nano)

some configs fell back to this unexpectedly which upset people so we removed it

we are going to implement this

the email they found was from a different repo and not monitored. this is ultimately our fault for not having a proper SECURITY.md on our main repository

the issue that was reported was fixed as soon as we heard about it - going through the process of learning about the CVE process, etc now and setting everything up correctly. we get 100s of issues reported to us daily across various mediums and we're figuring out how to manage this

i can't really say much beyond this is my own inexperience showing

hey maintainer here

we've done a poor job handling these security reports, usage has grown rapidly and we're overwhelmed with issues

we're meeting with some people this week to advise us on how to handle this better, get a bug bounty program funded and have some audits done

curious why /clear instead of making a new session?

and nothing expires out from the session until you get near the context window max - at which point we do a compaction process

we actually do heavily use prompt caching now

it's implemented in the backend, will expose in frontend soon

hey one of the authors here

we're a little over a month into development and have a lot on our roadmap

the cli is client/server model - the TUI is our initial focus but the goal is to build alternative frontends, mobile, web, desktop, etc

we think of our task as building a very good code review tool - you'll see more of that side in the following weeks

can answer any questions here

author here - right now it's all the same prompts as claude code

but we're going to make all this very configurable next week