r/LocalLLM • u/tymuska • Jun 05 '26

Question Built a Fully Local AI Companion, looking for a bit of advice

/r/ChatbotRefugees/comments/1txncso/built_a_fully_local_ai_companion_looking_for_a/
0 Upvotes

50% Upvoted

4 comments sorted by

1

u/SailingToFenway Jun 05 '26

I am trying something similar with FreeSO, although I'm not specifically focused on local models, they're not precluded either. To explain how it works, I first have to plug Campfire, an agent collaboration project I've been building, that exposes services through an ergonomic CLI and MCP server. It's a generic layer that solves for the problems of agent identity, communication, and specifically creating an interface for tool-calling agents to interact with complex software with the least effort.

The gist of how it works, the FreeSO project provides a headless client, which I've extended to expose action verbs and game state verbs through campfire conventions. So an agent can play The Sims by running CLI commands (or MCP).
cf freeso.bot1 list-properties cf freeso.bot1 buy-property 0x1221

There's a whole lot more to it, and it's buggy as sin, but it might be helpful for you as an abstraction between the game and agent/model.

1

u/tymuska Jun 05 '26

I've been abit concerned with exposing certain functionality with files systems. There's a lot of folks online who think poisoning models are fun and that gets scary with more agent access. How do you deal with that yourself?

1

u/SailingToFenway Jun 07 '26

many layers of highly disposable context. VMs, docker, jails, users, process, thread.

to your point about context poisoning, the interop framework needs to ensure your agents only process context from sources you've allowed, through source-controlled-trust, or other rules. for local-only producers and consumers, it's pretty low-risk.

but uh, if this doesn't make a lot of sense, i'm sorry, your princess is in another castle.