Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

fx v0.0.9 Use a frontier model to steer, then hand implementation to a fast workhorse. • Give each subagent its own model and reasoning effort • Subagents keep working while you steer • Send feedback to subagents mid-task • Switch models with Ctrl+P without losing your draft or images...

177,195 Aufrufe • vor 1 Monat •via X (Twitter)

7 Kommentare

Profilbild von Nikolay Petkov
Nikolay Petkovvor 1 Monat

oh that’s so cool 🔥

Profilbild von Tinoco2
Tinoco2vor 1 Monat

Why don’t we have the possibility to to oauth with Kimi, Claude and more models? Thanks.

Profilbild von Nandan Priyadarshi
Nandan Priyadarshivor 1 Monat

Ran into the same wall last week — one Opus session doing steer + implement just burned context. Split it: Sonnet for the plan, a cheaper model for the patch loop. Mid-task feedback without restarting the whole thread was the unlock.

Profilbild von Ersin KOÇ
Ersin KOÇvor 1 Monat

🙄

Profilbild von Julian Guerrero
Julian Guerrerovor 1 Monat

wanna be able to undo the last message (put it back in the composer), like opencode ctrl+x u. thx

Profilbild von Pranit
Pranitvor 1 Monat

Coming up 🔜

Profilbild von Julian Guerrero
Julian Guerrerovor 1 Monat

love it

Ähnliche Videos

how to use claude code mods like a top 1% user, step by step: give this to your agent before everyone catches on👇 1. set up Jev connect Jev to the model registry you want to use. check that the connection works and the listed models are available. 2. build your claude code mod open claude code 2.1.287 or later and paste this prompt: “build a mod called run-ledger. load plugin-authoring and use the API types for my installed version. create a dashboard that shows: - estimated cost per run, model, and source plugin where known - which model handles each task - each subagent’s status, latest action, and elapsed time include token counts, cache usage, and reported retries. count each request once. keep background tasks linked to their original run. use dated prices. label costs as API estimates, not subscription charges. show unknown when data is missing. connect the mod to my existing Jev setup. give Jev the task, available models, prices, budget, and relevant past results. ask it to recommend a model and explain why. start with recommendations. make automatic routing optional for eligible subagents. show the recommended model, actual model, result, and cost. include Jev’s own cost. keep state across hot reloads. add details and export. the dashboard itself must make no model calls. validate the plugin. test rendering, costs, attribution, and duplicate counting. give me steps for a live test.” 3. test the setup allow hot reload when prompted. run a simple task, a subagent task, and a mod-triggered model call. check that the dashboard updates, each request counts once, and Jev’s recommended model can actually run the task. 4. install the working mod ask claude to copy it out of the temporary folder and install it as a persistent plugin. see the cost. choose the model. check the result.

Avid

47,276 Aufrufe • vor 1 Monat