You absolutely can use "just a /docs" directory in Fossil. You can even point the web server to /doc/trunk/docs/index.md or whatever other file names you want. :-)
Interesting - so is this a local llm that identifies scams and prevents me from clicking? Seems like an awesome opportunity for a local version of Jev to say “scam/not scam”!
What are peoples' thoughts on whether a local version of Jev is possible? Having to call an API for something that's main benefit is speed is orthagonal to their ethos.
three.js and Vite, very basic, I set out originally to make a game where Neil knocks over cones and grew it from there. If I was to start again I would use a game engine as it has scaled further than I intended.
The story synopsis next to the preview gives you the full narrative arc before you commit. But fair point on wanting to see more.
You can edit or regenerate pages if something isn't working - it's iterative, not one-shot. Happy to help you try it out without payment - drop me an email.
Yeah, it’s pretty much ready, I’m just squashing a few last bugs. Launching this week, trying to move fast for exactly that reason.
Good call on the examples, I’ll add some that show off browser automation and more complex workflows.
Memory at launch is what’s baked into OpenClaw, but I’m planning to upgrade it to vectors + a continuously updated doc shortly after (similar to what Claude Web does)
If you want early access I’d be happy to get you set up personally, just shoot me an email at ramon <at> agentmode.co
Interesting - is it just the URL or is it actually crawling the phishing site to assess whether its phishing? And how does it distinguish the site bank.com from bąnk.com (with a little curly ą) if both are an identical clone of bank.com?
That's a great question - right now it is only looking at the results from a battery of several dozen indicators that we compute upstream of the model itself (which saves massively on tokens)
As small models continue to improve, and edge hardware becomes more capable, we would really like to run larger models that could incorporate full page content and screengrab data, which would be more likely to catch these kinds of attacks.
But we also find that sites that do one shady thing usually do others, which is a big reason why a tiny model like this can work - and why we are betting on low latency being a differentiating factor in real-world impacts.
reply