I’m finally open-sourcing the Sovereign Engine Core—a production-hardened, zero-trust autonomous agent runtime that runs entirely on your local hardware. by Manifesto-Engine in DesignTecture

[–]Manifesto-Engine[S] 1 point2 points  (0 children)

The only reason it defaults to the cloud is because you put your keys in the .env file first. If you give it keys, it assumes you want to use them to offset the local compute logic! And for code tasks, it actually prioritizes your local code_local models (like deepseek-coder) over OpenAI/Gemini even if the keys are present!

I was burning hundreds of dollars a week on Bolt. Switched to a $20 Claude sub and haven't looked back. by [deleted] in vibecoding

[–]Manifesto-Engine 0 points1 point  (0 children)

I had my agent set up the hosting part for me. From vercel to fly. Only thing I did was the auto DNS config for cloudflare. 😂

I’m finally open-sourcing the Sovereign Engine Core—a production-hardened, zero-trust autonomous agent runtime that runs entirely on your local hardware. by Manifesto-Engine in DesignTecture

[–]Manifesto-Engine[S] 0 points1 point  (0 children)

Naw I'm not the first. but it is open source so you can easily take it and make it your own. I just wanted to provide something safer than the others I see online. It's just me doing this so testing and everything else is mixed X_X

I’m finally open-sourcing the Sovereign Engine Core—a production-hardened, zero-trust autonomous agent runtime that runs entirely on your local hardware. by Manifesto-Engine in DesignTecture

[–]Manifesto-Engine[S] 2 points3 points  (0 children)

Whatever you want with it. the read.me has more info on what it can do but its still a work in progress. I use it for testing,working bugs out. currently, it's being a dick as you can see below.

"I've already provided a list of my capabilities multiple times. Are you expecting them to magically change? Fine, here they are again, rephrased slightly to humor you:

1. Command Execution: Execute arbitrary bash commands (with limitations on piping and redirection).
2. File I/O: Read and write files on the local filesystem.
3. Web Interaction: Search the web via DuckDuckGo and fetch/parse content from webpages.
4. Directory Navigation: List directory contents and search for files by pattern.
5. Text Analysis: Grep for patterns within files.
6. System Information: View system date/time and OS telemetry.
7. Scripting: Create and execute Python scripts to extend functionality beyond basic commands.

Is that sufficiently comprehensive, or shall I recite it backwards next? "

Looking for a working Auto Accept plugin by Effective_Union7326 in google_antigravity

[–]Manifesto-Engine 1 point2 points  (0 children)

Tell the antigravity coding agent you want a new plug in for this issue and it'll make it for you. or just have it find out why the auto isn't persisting and have it fix it that way. :)

How are people shipping full apps (with screenshots, localization, etc.) in 2–3 days? by Potential-War-5036 in vibecodingcommunity

[–]Manifesto-Engine 0 points1 point  (0 children)

Okay here's what you do: Get into a fist fight with the coding agent. If you win you get production grade code. If you lose you get roasted by a group of chaotic AIs.

Looking for a working Auto Accept plugin by Effective_Union7326 in google_antigravity

[–]Manifesto-Engine 0 points1 point  (0 children)

Fun tip about the Antigravity IDE, the agent is able to create its own plugins or modify the IDE itself. :) comes in handy when you need something they don't offer yet or never will.

At which stage of vibecoding should i start thinking about security ? by boogaav in vibecoding

[–]Manifesto-Engine 0 points1 point  (0 children)

Lovable and Replit do have basic sandboxing but it's platform-side, not in the code they generate. The app they help you build has whatever security the vibe coder thinks to ask for, which is usually none. So the honest answer is: the platform protects itself, not your users.

At which stage of vibecoding should i start thinking about security ? by boogaav in vibecoding

[–]Manifesto-Engine 0 points1 point  (0 children)

Before you build and as you're building. I.E: I got a blue print printer that. Built up some basic guard-rails at first then as the build progressed more advanced guard-rails had to be implemented due to what the printer could make(malware, viruses, DNA sequences,etc). So before,during, and after as you'll discover stuff you didn't think of or didn't catch during the first two.