blueman I REALLY need chat. I keep confusing all those opencode tmux sessions :(
blueI have three sessions per project. and I have the projects: repopack, primate, rcompat, flog, dog/cit (and sometimes socialcloud). also planning on future projects, superarch and many others
blueimagine how much confusion this causes
bluewith chat now, you always are in the context of a project (this is a local change I haven't deployed) yet. going to the homepage redirects you to your first, in the future default project
bluebeing always in the context of a project is immensely helpful
blueand btw: I think this is why people use herdr
phalethyeah, I think so too
bluebecause they realised tmux with a ton of agent sessions is gonna be totally confusing
bluebut repopack.com solves this so nicely. you always have a project context
bluealso with hosted agents, I can restart the computer as often as I want. the git checkouts survive because they're not on my computer
blueit's perfect
bluedreamreal: ^
blueI might be wrong, but I think we've hit gold here. only time will tell
bluethree workflows:
blue1) you host your agent on your computer and connect it to repopack.com via rp; that's how I intend to work now; rp manages the worktrees in ~/.local/rp/agent-workspaces
blue2) you host your agent on a vps or otherwise a server you own, and use rp to connect. same thing like 1), but not on your computer
blue3) you buy a hosted agent (essentially a vps or another abstraction) from repopack.com, you don't need to setup anything
blue3) will be the most elegant way to work, but also you might ask yourself - how do I get previews of the things I'm working on?
bluethat's why we have task previews, that's exactly the reason they exist
blueit's a new way to do development
blueradically different, I think, but also very interesting
blueand also crucially, it means your computer can burn down and you don't lose anything
blueand you can do development on a weak(er) laptop
blueyour computer becomes a terminal to your development environment, via your browser and repopack.com
phalethlot of people will pay clanker and be wanting to get clanker hooked up to the project easiest way possible
blueyes
phalethif you make it so that the person has to write commands in terminal then you've lost them
bluewell ideally, they're all gonna work through repopack.com chat
phalethI mean for hooking up clanker
phalethlike to me the chat says some nonsense cause I have no clanker
phalethit should shove down a guide how to hook up clanker to the user's throat
blueyes, this is going to change with hosted agents
phalethalso once they set it up it should make them feel like a winner
bluewell with hosted agents, there's no setup involved othre than connecting to your provider
blueand if you buy a hosted agents, you would still get the free models immediately
phaleththe gamification aspect is important, people are way too screwed nowadays, especially the youngsters
bluelol
bluedreamreal: you use claude code, correct?
blueI currently only have rp wire opencode sessions. I do need to extend chat to claude code and codex
blueyou don't have to work on the task, just create it
blueI want to make it perfect but I need to know about things that don't work well
bluejust create tasks, it's cheap
phalethyeah, but clanker is just gonna write more walls of texts
blueignore it, just create tasks, tasks are the cheapest currency we have
bluethe walls of texts are something we can work against in AGENTS.md
bluethat doesn't make creating tasks invaluable
phalethso does `rp bootstrap ...` create a project?
blueor well, "not valuable"
phaleththe bootstrap term is confusing
blueit doesn't
blueit sets up a project by cloning it
bluetry this
phalethah, now I get it
bluemkdir ttt && cd ttt && rp bootstrap primate
blueit will clone the project into ttt/primate, and print instructions. it's mostly for agents
blueif you run rp bootstrap INSIDE a repopack.com project, it will just print instructinos
blueit detects it by looking at the .git/config and finding repopack.com origins
phaleththat information is missing there
blueya
phalethclanker would just turn it into a wall of text
bluecreate task, I will fix
blueor add manually :P
blueeither way you need a task for it
phalethyeah, I will try to read the docs, prolly impossible
bluechat is working REALLY well
blueonce I have this deployed, you gotta try it out phaleth
phalethok, anyway, I don't have a clanker
bluethere are open models
phalethlast time I messed around with LLMs was in 2023 and since then I forgot everything
phalethI remember I used some python environment thing that was painful to work with
phalethevery single project worked only on specific version of python
blueyou just need opencode
phalethisn't opencode's source closed?
phaleth:)
phalethI think it was anthropic who published sourcemaps of their CLI to npm package registry and then somebody found two vulnerabs in their shitty CLI thanks to that
* phaleth looks up if garbage is still running on the VPS
phalethbut people also use CLI so it's impossible to distinguish people from clankers
blueyes. but the CLI isn't assumed to be 100% safe
phalethand people should also be denied to take that action
blueyes
blueanyway can script your CLI
bluethe last authority is the website
blueguarded actions always require you manually approving on the ui
bluethere are not a lot of them, but important things are guarded
blues/anyway/anyone/
phalethok, that task says: "equires a deliberate human confirmation in Repopack's browser for every invocation"
phalethrequires*
phalethbut how is that confirmation gonna look like? will it be enough that I'm logged in only via rp CLI?
phalethcause now I have to be logged in on repopack site itself and hunt for the merge button everytime
bluethe human confirmation is a popup that appears on the top right in the browser
blueand yes, you wouldn;t need to hunt for the merge button
phalethyeah, but in the browser after logged in to repopack website right?
blueyes
phalethwell, that's still the same then
bluesame as what?
phalethmakes no sense to implement that task at all
bluewait, are we talking past it other? `rp task merge` would allow your clanker to request a merge
phalethlike currently, in CLI you get link to task, open it and hit the merge button there after logging into the website
bluethat would show up as a popup on the UI
phalethyeah, but I'm in role of the clanker too :D
bluethat spares you from looking for the task and scrolling down to the merge button
blueif you're in the role of the clanker, that's useless for you, yes
phaleththere is no looking up the task, the URL to the task is already in the terminal after `rp task submit . --push`
blueyou wouldn't type `rp task merge`, then go to the website and confirm it
blueyou'd just go directly to the website, I agree
bluebut human-driving rp isn't the most common use case
phalethok, then lets move on, no need to implement
phaleththat means I should enable that knob I shown on the picture above again
bluewell arguably it can move things a bit faster... let's imagine I'm in chat
bluethen I tell the review clanker, review this task, and if approved, request a merge
bluethen it can work in the backgronud and at some point I get a merge popup request
blueI think there is some rationale for that task in the task description
phalethyeah, that makes sense, but I was thinking it should just be available to anybody, but clankers will not have permission by default, or better yet that merge availability is off by default, which is already done by that knob I posted on the picture above
blueso the probem is, you cannot distinguish who's driving rp, right?
phalethI dunno, prolly not
blueit's literally impossible to distinguish it. maybe in chat because we run in a sandbox. but even then we cheat with RP_CHAT_SANDBOX=1
bluean env variable should not become an access gate
blueI believe in repopack, we should have two levels of access. rp and browser. browser can do less actions, but has higher permissions
bluerp can do anything, but important stuff is guarded, because it's scriptable and agent-runnable
phalethok, how about doing something like `rp login` does
phalethit opens up a web browser to confirm and only a human can confirm that
bluerp login just gets you the token
phalethyeah, I mean that behaviour
blueessentially we have that behaviour already for guarded actions. except it doesn't open a new browser, it sends a push SSE to your existing session
phalethso just show a merge button there, no need to logged into the website itself and click some notification or whatever
bluebut remember that with rp login, you already need to be logged into the website anyway
bluethis is more or less the exact same flow as push popups, just in a new tab
phalethyeah, that's true
blueI honestly don't even know why we're doing rp login in a new tab
blueshould just do a push notif
phalethso the client would just have to generate a one time token that the server can recognize as something belonging to the user
blueI guess, yeah
phalethsomething super obscure
bluephaleth, there's a new feature on repopack.com if you're interested
bluewhen you're in a project, click on the project switcher
bluethe last line allows you to subscribe
blueyou can choose which events you're interested in getting informed about
phalethI see, looks nice
bluethe transport mechansim is confirmed in your account settings: any combination of email, bells and push notifications
phalethI mean, by making the problem in the first place
phalethwell, whatever it wrote there looks like a bloat
phalethah, so clanker added a bunch of flags to the CLI it seems
phalethor query options
phalethon task stacks page in docs there is this: "the stack merges from parent to child" and later "An unmerged parent cannot be closed while open children remain"
phaleththat sounds contradictory
phaleththe first statements is most likely wrong, or at least I'd think so
blueya
bluethe problem is phaleth, before it was filtering in the cli, now on the server, that's faster
blueanyway, I merged 919, gonna redeploy
phalethyeah, figured
bluephaleth: try now
bluerp task list --status review
blueis much, much faster
blueyou need `rp update` first and to be on the unstable channel