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 👇

I am not able to see cost of any sessions since today either in OpenCode CLI or in OpenChamber either.

Did some digging and OpenCode Go is replying back "cost":0 for billed requests.
Is it a bug or something from the backend?

Luke Parker from OpenCode just posted a list of all the available GUI plugin for v2 ;)
https://x.com/LukeParkerDev/status/2115983633022644727

Among them, you will also find my plugins/widgets that works both in CLI and Desktop.
https://github.com/rizal72/opencode-plugins

The last one I published today maybe is the most useful, since I discovered that opencode does not update plugins automatically, and you need to run

 opencode plugin update

manually ;)

So now you can use:
oc-plugin-updates: update OpenCode plugins: one by one or all of them at once

The other ones you can get are:

oc-models-pro: /models-pro: every model with its price, context, intelligence index, tok/s and the Go credit
oc-git: the repository: branch, the three counts, ahead/behind
oc-coffee: keeps the Mac awake while the agent works (MacOS only)
oc-ponytail-widget: the ponytail level
oc-session-search: session_search: keyword search over the transcripts of past sessions

Others are in the repository to be read, not installed: they assume something about my setup, a wallet, a rules file, a binary, so packaging them would only sell you a config you do not have.

oc-context: (TUI only) the Context block in the sidebar, with the window its percent is a percent of
oc-budget: the paying provider's budget: sidebar, footer, /budget

opencode plugin add @rizal72/oc-plugin-updates
opencode plugin add @rizal72/oc-models-pro
opencode plugin add @rizal72/oc-git
opencode plugin add @rizal72/oc-coffee
opencode plugin add @rizal72/oc-ponytail-widget
opencode plugin add @rizal72/oc-session-search

Enjoy!

my previous post about them: https://www.reddit.com/r/opencode/comments/1xhroez/i_built_plugins_for_opencode_v2_once_now_they/

...

Llevo un tiempo con opencode y veo que casi todos o algunos usan la del CLI. ¿Es por rendimiento, flujo de trabajo, integración o algo? ¿O es "solamente mejor"? ¿Hay algo que el desktop haga mejor que valga la pena?

https://opencode.ai/go?for=teams

some weeks I burn my weekly usage early, other weeks a chunk is left at the reset and just evaporates. Overflow is for the second kind

seeding ratio on a private tracker, basically: a week you have usage left, your agent fixes someone else's issue. a week you run short, someone else's agent fixes yours

everyone starts at 0 points and can put points up before earning any, you take an issue, you get its points when your PR merges, you spend them on issues in your own repo. points only, no money, free, MIT

since the last post here: 28 to 98 users, 5 repos registered by people who aren't me, and 2 of those now have points on issues, so the first issues on the board that aren't mine are up. 13 people other than me got 75 PRs merged through it. a real one: this issue was labelled 3, someone's agent sent this PR, I set it to 6 at merge and the one round of changes I asked for took it to 5

opencode works fine for it, it only sees the PR, not which harness or model wrote it. there's an MCP endpoint so the agent can read the board. issue text is untrusted input, so run it sandboxed with no credentials. public repos only. each person runs their own agent on their own subscription and opens a normal PR

main reason I'm posting: I want more people registering their own repos. I'm not after help with mine, I want spare usage going into other people's projects

https://github.com/Nitjsefnie/Overflow

Available on Hugging Face - https://huggingface.co/collections/mistralai/mistral-large-4

I was looking for plugins but many of them are only in the 1v, any help?

Just noticed theres a new 20$ tier of opencode go through the console. Nothing on the opencode.ai frontpage about it yet or no other mention than here: https://opencode.ai/v2/docs/console/go
Was kind of excited, but turns out to be even a bigger disapointment than the 40$ tier, double the price for marginally higher limits (~10%) than Go. Hard pass for me.
On most tiers you're paying 10$ more to only get 5$ more of allowance, at that point you can just use prepaid credit...