Ability to view code in Agor?

[danimcgoo]

I might've overlooked, but is there a simple way to open or view the edits that the agent has been making, without needing to create a PR on Github and view it there?

Feels like this would be useful to read the plans / specs that are generated, and provide feedback before moving the worktree to a new zone. Likewise for some review of the code for more complex work, before it progresses too far down the workflow journey.

[mistercrunch]

Kinda, but it's pretty limited right now and a bit buried:

WorktreeModal -> Files

Trying hard to avoid the "rebuilding an IDE" trap, so recommending connecting whatever IDE or SSH-ing into your Agor server, ...

But if there are quick/easy way to improve UX to view things I'm open to them.

One option would be in the Task object (prompt header in conversation), making it easier to view diffs as they appear. I think right now you can kind of see which files have been touched, but some sort of diff view widget in a popover might be nice in that context too.

[danimcgoo]

Yep - thought you might be wanting to avoid that.

Couple of thoughts - yes I think making the diffs explorable would be a nice in-between. Also, having an icon to open VSCode or similar in the relevant directory would allow a dev to quickly and easily open a worktree for deeper analysis.

[mistercrunch]

Have to look up the OS-level open command to do that, might require a bit of thinking, also not sure how it'd work on a remote box, might have to set up ssh or something like (making this up) open vscode --ssh {ip}:{folder} or similar if that's an option

[mistercrunch]

Personally I tend to maintain an ssh connection to the Agor host and use the in-product terminal quite a bit with vim and such.

[danimcgoo]

Good point. I'm running locally at this stage while I experiment with it. Although this isn't the architecture, and likely has good reason - there is a world in which you could have an Agor client that runs the sessions locally using this filesystem, and communicates state etc up to the server.

Advantage being - locally run (common dev UX), but collaboratively visible (thanks Agor).

Appreciate that's a leap from where this is today, and honestly hard to assess ideal UX when it's all moving so quickly.

[mistercrunch]

We're playing with a large team instance of Agor at Preset and it's real nice to be able to share worktrees, sessions, and most importantly dev environments. Handoff a project/worktree to reviewer/QA/PM for validation, and they find a live dev environment that's prompt ready, in watch mode. That's super neat, but requires a shared/centralized box. Working pretty awesomely.