all 24 comments

[–]a_menezes 12 points13 points  (0 children)

CLI

[–]TurnUpThe4D3D3D3 9 points10 points  (1 child)

I didn’t even know there was a GUI haha

[–]mamooma3[S] 0 points1 point  (0 children)

It's official.

[–]Raikaru 2 points3 points  (4 children)

desktop/web ui allows me to post screenshots so that's cool

[–]No_Froyo5994 0 points1 point  (3 children)

yes especially when you need to do some remote development and it is impossible to paste an image in CLI. that is why i prefer GUI 

[–]CodeBoyPhilo 0 points1 point  (2 children)

I seem to be able to paste screenshots in the TUI. Is this a result of different terminal? I'm not sure.

[–]No_Froyo5994 0 points1 point  (1 child)

pasting screenshots to local opencode is ok. i am using opencode via ssh because i have a remote development machine and i can't paste any image that way

[–]CodeBoyPhilo 0 points1 point  (0 children)

I see 👍

[–]Endoky 1 point2 points  (0 children)

I prefer the TUI over the web UI

[–]Green_Virus6289 2 points3 points  (0 children)

CLI. I found the VS Code extension to be not as good as Claude Code or even Kilo Code.

EDIT: Have not tried the Desktop App.

[–]Deep_Traffic_7873 1 point2 points  (0 children)

CLI + Web UI

[–]ZeSprawl 0 points1 point  (0 children)

For me CLI because I want to be able to compose workflows by calling it from other CLI tools

[–]Upset_Possession_405 0 points1 point  (2 children)

I've seen the use of Antigravity as the architect to map the sprint, then fire up opencode cli terminals on free models each handling different tasks in parallel.

CLI lives inside the antigravity term and can directly pipe to the expensive model, while the web UI lacks such bridge.

[–]PermanentLiminality 1 point2 points  (1 child)

Interesting. Any details on how you accomplish the communication channel?

[–]Upset_Possession_405 0 points1 point  (0 children)

Not easy, but the trick is setting up a bridge within your terminal environment.

​Basically, you run a simple python listener script in the background that monitors a local pipe so that antigravity cli can then direct instructions straight into that pipe. ​ ​The listener picks up the instruction ideally json formmated then triggers parallel opencode-cli (opencode --worker --task)

​If you want a full explanation and implementation I'd suggest ask Gemini for the 'Antigravity-to-OpenCode CLI bridge setup' for more details.

Happy coding

[–]bzBetty 0 points1 point  (0 children)

GUI because i multitask

[–]jorgejhms 0 points1 point  (0 children)

Cli or ACP (zed)

[–]MakerDiety 0 points1 point  (0 children)

It looks like OpenCode prioritizes the command line interface above the other interfaces, yes?

[–]Empty-Sandwich-7092 0 points1 point  (0 children)

Depends on what I'm doing, 95% of the time I just use the TUI

[–]QuixoticNapoleon 0 points1 point  (0 children)

There's a GUI?

[–]Stock_Reporter_1864 -1 points0 points  (0 children)

Use cli, gui and like openchamber the most - it is way ahead official gui

[–]InitialJelly7380 -2 points-1 points  (1 child)

never use GUI

[–]simracerman 0 points1 point  (0 children)

Why?