Загрузка видео...
Не удалось загрузить видео
we landed on a pretty good workflow for doing parallel work in OpenCode this demo is with git worktrees but i also preview an alternative we're working on at the end this will be in 1.6.0
290,877 просмотров • 4 месяцев назад •via X (Twitter)
Комментарии: 48

your wife kicked you out to the garage 🫵😂

damn it i meant 1.16.0 i suck at versions

nice raadish

@alan__rice nice alt logo at the end

Wow nice one

I use opencode from ~/GitHub folder and that contains multiple repos (packages, monorepos, and open-source projects). I do this because I often reference repos to emulate patterns in a project. Does that mean worktrees and more will not be available unless I switch to working from 1 repo? Is not working from a repo a bad practice in opencode?

yeah but we have a new project references feature that should help your case soon so you can open it in the right folder but easily reference other directories

For the curious on a walkthrough of the implementation with references

been having such command in my pi agent, super useful also I like the option to move and create worktree, integrated it with worktrunk

Believe it or not this is the first time I've ever seen you and heard your voice...

this is quite handy, is it a mix of plugin + custom agent? or can it be done through custom agent directly?

exclamation point

Oh thats brilliant! Thank you!

@chriszeuch Your face is everywhere btw

Is this replacing or complementary to "warp"? Confused when I would use which command.

replacing warp

Great feature, the keybinding is bad, everyone knows ctrl+w is for closing tabs.

think we're changing to ctrl+m

Since this all is session centric, I would want session switching to be easier: 1. A sidebar that shows active sessions that are either recent or "pinned" by the user with their status 2. A tmux like numbered way to switch between them 3. Switch to last session with a shortcut

how are you closing out the worktree's and merging back locally?

Can you hire someone to deal with your GitHub issue backlog? It's essentially worthless at this point with the amount of spam on it.

super cool work dax! we need open alternatives. i've been using claude code exclusively for the last 9 months for everything. but it looks like i need to check out opencode again. btw how well does opencode work on smaller screens? i'm prototyping a dedicated small coding device on the go. everything out there seems to be built for desktop experience, not mobile.

we're working on some better space efficient designs our webapp looks decent on mobile

oh cool. we should have the first batch of prototypes done in a few weeks. happy to send you a prototype unit with opencode installed to code on it it in exchange for feedback.

@thdxr Why not just use your phone? I'm clearly missing something here 😅

we want to prove steve jobs was wrong 😂 just kidding. the goal here is to design a dedicated coding device. just like kinde. why not read books on the phone? kindle is optimized for mobile reading. we think coding will be woven in every fabric of everyday life moving forward. literally everything. it’s so easy for everyone to vibe code now and build tools and services they need to manage their life and businesses. like reading, coding is the new writing. so there is a need for a dedicated coding device.

@thdxr Interesting, I respectfully disagree but would happily be wrong! The only reason I think kindle makes sense - which it doesn't for me - is that the screen looks more like paper and has less glare What makes a coding device better than a phone?

@thdxr yeah you could totally be right! we find that with hardware it’s better to ship an actual prototype and let people use it than debating. then we’ll find out for sure if people actually want it. that’s how we operate at @autonomous_labs. we are betting on the physical keyboard!

This happens to me all the time. Great idea

the disk is the easy part to split. what decides whether parallel actually works is shared dependencies, two agents in separate trees are fine until both need the same schema or config, and that's the one file a worktree can't isolate. curious what the alternative does there

how do you enjoy those garage lights? they look cool i wonder how hard they are to swap out if they burn out?

if i'm in a tmux window with neovim and opencode in separate panes, do I still need to cd into the new worktree dir in the neovim pane?

we have a copy dir command in ctrl+p but yeah thart part is annoying thats why we added a diff view built in so you could see stuff without going to your editor

hmm yeah, sometimes that's enough but not always. For me that's the big struggle with worktrees - I want the environment cloned, I want to be able to run neovim in there, I want to be able to run the app with branch-specific env vars. I've had to build my own tmux + worktrunk workflows for this, it'd be nice if it can be solved at this level though

i am excited about native worktree integration!

I see you are a fellow Vimium user in chrome. Wtf is even a mouse?

painpoint I have with worktrees is around having multiple environments (ports/dbs etc) to be able to debug the app. i've been enjoying using gitbutler which maintains multiple branches + a merged version for you to test on. In theory you'd be able to do similar with this?

Awesome, I had built a plugin to do that.

Not related to your post but is your garage air conditioned?

Just yesterday when I had a tool I was developing and a different project that integrates and tests that tool. I wanted to continue the conversation I was having with the development context for integration but had to get a document made instead. Can't wait!

`/diff` ? And I was, like a caveman, opening up a separate tty panel to quickly do `lazygit`. Handy.

Why don’t u just split open code to 4 instances using tmux to live on one window, each on work trees

Neat.

Read my mind. I’ve been running into this same situation re worktrees

@jayair Does this let me move the session to another machine? Eg maybe my dev box in the cloud?

sick update on the parallel workflow for 1.6.0! what’s the biggest win the alternative preview has over the git worktree approach?

this 1.16.0 parallel workflow update for OpenCode is so clutch, can't wait to test it. i've run into so many snags with git worktrees, so curious what the alt preview handles better?

its like if stash didnt suck. nice
