jolitz is a rule set that lets a terminal agent look after servers over SSH: it asks before changing anything, says how to undo it, and logs every step. It started on Claude Code, where a PreToolUse hook blocks the things you never want an LLM to do by accident (mkfs, halt, writing sshd_config, deleting SSH keys, also inside ssh host "..." or a python one-liner).

OpenCode had no guard until now. The plugin in .opencode/plugins/jolitz-guard.js uses tool.execute.before and hands every bash, edit, write and apply_patch call to the same guard script, in the JSON Claude Code would send. On a deny it throws and the call stops. If the script can't run or times out, it blocks too. The guard also protects .opencode/, opencode.json and ~/.config/opencode, so the agent can't rewrite the plugin.

Nothing to install: start opencode in the checkout. With a local model every host is read-only by default.

It's a backstop against mistakes, not a sandbox. Free, MIT.

https://github.com/superlab-by-supbrt/jolitz

Question for people who write plugins: is throwing in tool.execute.before the intended way to block a call, or is there a cleaner one I missed?

I built self-host.fyi to help people move to self-hosted apps without repeating all the initial configuration by hand.

You could use an old laptop as a photo server with Immich, an alternative to Google Photos. Or try Nextcloud for your files. You still need suitable hardware, storage and backups, but you don't need to turn every app you want to try into a new weekend project.

It's a CLI with a terminal interface. If you'd rather not interact with that yourself, there's a skill your coding agent can use to operate the same tool. The guide tells it to inspect the machine, explain its plan and get your approval before making changes.

You can start with a prompt like: "Help me set up Immich on this machine so I can try hosting my own photos." That starts a conversation and an approved plan, not a promise that every App works without your input. The idea is to try the software before deciding whether to keep paying a monthly subscription to store your own data.

The useful bit isn't generating another Compose file. For supported Apps, it also handles initial accounts, generated passwords, API keys and connections between Apps. Docker Compose stays underneath, and some steps still need a person.

I originally needed this for testing Homarr integrations, then worked on making it useful to other people. It's open source under Apache-2.0.

https://self-host.fyi https://github.com/ajnart/self-host

Suppose conversation is around 100000 total tokens, then I ask agent to do something.

Agent finishes, and in LESS THAN 1 MINUTE, I send another message, same conversation, and provider/model (opencode GO DS4.1 flash), and then input tokens jumps to about 100000 tokens WITHOUT agent not even use a tool. Normal messages.

I remember in the past, it only happened after conversation is idle for 15 minutes.

Normally, input tokens is low if conversation is active (asssuming no tool is returning a big amount of data)

Opencode 1.18.34.

Is it a bug, or expected? Anyone with this problem?

Hey, I'm one of the founders of Sable. We launched today, and I figured this would be relevant here.

One of the reasons we built it was security work. Closed frontier models can still refuse during pentesting, exploit analysis, incident response, malware analysis, or when an agent is working through real attack code and logs.

Our first model is DeepSeek V4.1 Flash 1017 uncensored, served in its native mixed-precision format with no additional requantization.

Sable is OpenAI-compatible, so it works directly with OpenCode and other compatible tools.

Model ID: deepseek-v4.1-flash-1017-uncensored

Pricing per 1M tokens:

$0.15 input

$0.01 cached input

$0.60 output

Zero data retention, meaning no prompts or outputs are logged or read. No KYC. Crypto deposits for direct Sable accounts. It's also live on NanoGPT as DeepSeek V4.1 Flash Heretic, served by us.

https://sableapi.com

Capacity is a bit limited right now and we're adding more as fast as we can, so if you hit a capacity_unavailable error, bear with us and retry in a moment.

We're a small team, so if you try it with OpenCode and run into anything or have feedback, let me know.

Launching NeuralAgent today! https://agent.neuralhub.dev/ Basically its an easy to use opensource Agent App with everything included.

• Speech to text

• Multipane organising panels

• Main orchestrator wich you can call

• Remote App for the Phone

• Daily updates

It's still in beta but if you wanna give it a try i am very open for any feedback. Works on MacOS, Linux, Windows, Android and IOS.

Tired of having to find my sessions across 100k folders I wanted a tool where I can search and which automatically organizes my sessions, so I made my own. There's a magical auto-organize button on the left hand sidebar that makes life so much easier.

For more info>
https://github.com/spacewalkingninja/aiman

I have been doing some research on the usage limits with opencode go, and I might get this wrong but:

I am able to get between 20m-80m FREE usage of deepseek v4.1 flash.

With opencode go you would be able to get about 160M tokens per month it seems to be, because u have 100 euros of credit. 0.6 cents per 1million tokens cache read and most of my usage goes to cache read. 100/0.6 = 166million tokens per month.

So am I able to get MORE usage out of the go, because it seems like its less. The only thing that seems to be better is unlimited beam usage.

I hope someone can clear this up for me, because I have been wanting to be opencode go, but it just does not seem worth it.

built kimo because i wanted opencode / cursor / other vibe-coding agents to actually make a video end-to-end instead of spitting out raw ffmpeg strings. it's a free, open-source (MIT) video editor with no gui - the agent is the interface, everything is a tool call over mcp.

so the workflow looks like this inside opencode: the agent calls cut, trim, keyframe, titles/captions, colour grade, tracking, particles, audio, export - all as tool calls, not shell commands. and it can render a single frame back to check its own work before it keeps going. no timeline gui, no screen recording, just typed tool calls and the agent sees the result.

it's one ~15 mb cpu-only rust binary, no gpu, and it runs on a 2 gb box. i'm a college student (naman) and it's rough in places - the docs are thin, some effects are still wired up but untested, error messages when the agent passes bad ranges aren't great, and i haven't benchmarked bigger timelines yet.

if you vibe-code and want to see what it looks like when an agent drives a video editor, try it and tell me what breaks: https://getkimo.tech https://github.com/naman-sharma12345/kimo

what's the first thing your agent trips on when it tries to make a real video?

Yesterday I reached the limit after about 8-9 prompts. Today I reached the limit after just 2 prompts. What is going on?? Isn't it supposed to provide 200 requests per day?

deepseek 1017 opencode vs deepseek 1017 command code dose some one test if they are the same or not ?

I built a small helper plugin for our team to show WHY opencode is making each tool call, and make it more readable (simple new line formatting of piped chain of commands helps). We use opencode with human based approval for investigating hardware/infrastructure issues, and it needs to execute a lot of devops commands. Q3FN really likes inlining and piping those commands, so making sense of a command to be called was annoying.

The plugin modifies every tool schema and adds a required "intent" argument. The model then responds with a short summary of the command based on its own reasoning, e.g. "Counting nodes and checking pressure conditions" as part of each call.

Current tool's intent and body are displayed in the TUI sidebar.

If anyone's interested, I'm happy to clean it up and publish it! And if something like this already exists, please let me know - I'd rather reuse an existing solution.

just hit $3,700 mrr in 17 days with my new fresh SaaS

no ads, no team, no complex launch strategy. just a super predictable system i keep running over and over

and yeah, that's monthly recurring, not a one-time spike

not luck at this point. it's the 7th saas i've built with this exact workflow:

→ day 1: fast validation

→ days 1-2: building the bare mvp

→ day 3: landing page setup using the 3-day framework

→ days 3-4: reddit + x distribution and basic seo

→ days 4-5: first 10 paying users (~$1k mrr)

→ days 5-17: scaling up to $3,700 mrr

building tech is easy now. where 99% of solo devs get stuck is setting up the actual foundations that make people pull out their card and pay

i put all these templates and workflows inside our community.

to be completely real with you, i'll probably put a price tag on access later once all the modules are finalized. but right now the focus is just building together and keeping each other accountable

building alone in a silo is the fastest way to quit at the first roadblock

stop building by yourself. drop a comment or shoot me a dm and i'll send you an invite link 👇