@jeremyosih This problem is best solved in training to make model:
- aware of how much time has passed
- predict how long actions will take
- decide if an action is worth the time
the last one is what you and i do all the time, but agents don't.
LLMs don't understand the value of time.
I spend a fair chunk of my time on meta - analyzing sessions and figuring out where LLMs spend theirs, to improve prompts and tools to make them stop.
Fundamentally, it feels like this should be solved elsewhere.
Since I started using OpenCode I've wanted a native TUI.
For the last week I've been daily driving a 1:1 port of the CLI, built on new OpenTUI bindings. It talks to the same TypeScript server.
I've been working on a couple ideas for plugins:
1. native c abi, so you can write plugins in any language that can build a c-abi shared library. it's fast, and it's the same plugin api the built-in plugins use. (the built-ins are rust and compiled into the cli, so they skip the c abi.)
2. ts plugins. they run on a bun js host through a compat layer. it's likely i'll ship this, but i need to test it more. in a sweep of ~890 tui plugins from npm, ~710 behaved the same as in the current tui. this would make the ts → rust tui transition much nicer for people who've customized opencode.
3. plugins as source. to avoid putting distribution complexity on plugin authors, you need some sort of jit compiler or interpreter. i'm playing with a couple ideas:
- luau, the roblox's sandboxed lua dialect, with optional types.
- webassembly, so anything you can compile to wasm works. apple treats a .wasm file as data, not code, so plugin authors skip signing/notarization and per-platform builds.
- possibly something like tiny c compiler, but i'm not sold on it yet.
Since I started using OpenCode I've wanted a native TUI.
For the last week I've been daily driving a 1:1 port of the CLI, built on new OpenTUI bindings. It talks to the same TypeScript server.
@kmdrfx and @LukeParkerDev convinced me Luau is the best plugin runtime, but i have PTSD from a past life writing Redis Lua scripts (1-based indexing, tables for everything, and nil making holes in arrays).
Still, it has some nice properties: plugins ship as source, sandboxed with limits, fast, types, no toolchain, and complexity is low.
Since models write the code, Luau is good now, right?
I've been working on a couple ideas for plugins:
1. native c abi, so you can write plugins in any language that can build a c-abi shared library. it's fast, and it's the same plugin api the built-in plugins use. (the built-ins are rust and compiled into the cli, so they skip the c abi.)
2. ts plugins. they run on a bun js host through a compat layer. it's likely i'll ship this, but i need to test it more. in a sweep of ~890 tui plugins from npm, ~710 behaved the same as in the current tui. this would make the ts → rust tui transition much nicer for people who've customized opencode.
3. plugins as source. to avoid putting distribution complexity on plugin authors, you need some sort of jit compiler or interpreter. i'm playing with a couple ideas:
- luau, the roblox's sandboxed lua dialect, with optional types.
- webassembly, so anything you can compile to wasm works. apple treats a .wasm file as data, not code, so plugin authors skip signing/notarization and per-platform builds.
- possibly something like tiny c compiler, but i'm not sold on it yet.
@avrldotdev just more things i'm working through, like things i've missed in the plugin api. which is why it's worth doing this exercise. there will probably be a couple that don't work out, but i'm trying to get it down to a small %
Every couple of days i jump on the inference call. The team works across messed up time zones, and their call happens to land right when i’m getting started in the morning.
Most of the day i’m buried in terminal details, so this lets me have a peek at what’s happening on the other side (and practice my Chinese).
There are a couple things we do at Anomaly, like owning things end-to-end and getting into other people’s business. It’s really helpful to understand the entire funnel, even if you’re not working on all of it all the time.
Good ideas come out of that kind of cooperation, but it usually has to come from the top. It doesn’t evolve organically. Otherwise people tend to stay in their lane.
On today’s call we discussed this copy for 30 min. hahaha, anyway …