Submit

Back to the channels

#repopack

  1. blue Chat is coming to all projects - looking to deploy later today.
  2. blue Initial support for OpenCode & Codex; Claude Code will be added later.
  3. stagas neat
  4. stagas i'm out of credits and i discovered the first limitation. i don't know if it's related, but i would like to create issues by pasting photos and text without them running right away
  5. blue First limitation in repopack?
  6. stagas no in the agents workflow
  7. stagas codex doesn't let you queue anything
  8. stagas and kilo also says you're out of creds and stops
  9. blue Oh, I see. Well I think you'll find repopack able to do all those things, pretty well (though I don't think repopack chat has yet support for photos)
  10. blue Tip btw: OpenCode has free models you can fall back to when you're out of juice. They're not very good, but good enough for you to be able to create tasks
  11. blue So at least you can plan work during your downtime
  12. stagas kilo has also, and openrouter
  13. blue yes, many of them come from openrouter
  14. stagas they suck bigtime :P but yeah i might find minor issues for now
  15. blue yup
  16. stagas put chatgpt and it made me an issue tracker exactly for that with bun/sqlite https://ibb.co/bjtktbM8
  17. nevet image hosted at ImgBB
  18. blue haha stagas
  19. blue WB stagas.
  20. stagas yeah it crashes often it sends me to the login screen when it runs out of mem
  21. blue oh :(
  22. stagas at least it's not a full reboot :P
  23. blue I'm redeploying repopack.com now, with chat enabled for everyone.
  24. phaleth for everyone?
  25. blue Yes
  26. blue well, everyone that has an account
  27. blue which isn't a lot of people
  28. phaleth also clanker
  29. phaleth or can I use one of those free clankers?
  30. blue yes
  31. blue opencode has them
  32. phaleth let me show you what I mean
  33. blue according to stagas, so does kilocode. but we don't support kilo as harness yet
  34. phaleth https://www.aiblogly.com/how-to-get-llm7-api-key-for-free
  35. blue if opencode can run it, you can use it in Repopack Chat
  36. blue (deploying)
  37. stagas kilo app is quite good, i'm using it now with openrouter free, it's not that bad
  38. blue ... and we're live, with chat for all.
  39. stagas nice
  40. blue stagas: dreamreal: lioloc: systemfault: if you can try out the chat feature at your leisure and give me some feedback, I'd be very much grateful
  41. phaleth never heard of kilocode
  42. phaleth never heard of <anything AI you can think of that came out lately>
  43. phaleth also AI is a bullshit term
  44. stagas yeah it's too many stuff going on
  45. stagas you can't keep up with all of them
  46. blue Oh, I just realised I need to release a new rp
  47. blue whoopie :O
  48. blue well, coming in a few moments
  49. blue phaleth: fyi, I'm gonna get a new vps for myself, where I can run codex/opencode
  50. blue since my poor old laptop can't handle what I'm throwing at it
  51. stagas blue: tell me when it's ready to run the installer
  52. blue stagas: ready, `rp update`; you should get rp 0.3.0
  53. blue which supports Repopack Chat
  54. blue or just use the installer
  55. phaleth blue: your poor old laptop is the thinkpad?
  56. blue yes phaleth, T480
  57. phaleth that's a beast laptop
  58. stagas No SSH key is registered for your account. Add one with `rp key add <key|path> [name]`, see `rp key list`, then retry.
  59. phaleth there's only one rule, don't put blue's private key on that VPS
  60. blue why would I do that, phaleth
  61. phaleth the other is of course protect your T480 with your own body
  62. phaleth I dunno
  63. phaleth just saying keep things separate
  64. blue stagas: yes, you need to add an ssh key, try `rp key add <path>`, you can generate a separate key for that or use your gh one
  65. phaleth clanker would like to clanker and connect everywhere
  66. phaleth it pulls you into "let me access that system and I will figure out the solution for you" situation every now and then and you know that
  67. blue ya
  68. phaleth and it just artificially creates those situation
  69. stagas ok i pushed issuebox to main what do i do now? i'm lost
  70. phaleth to main? :o
  71. phaleth I think the docs is bad so it's better to follow rp's help currently
  72. phaleth do you have the code on remote already? cause "to main" sounds like it ended up in hands of a corporation
  73. phaleth stagas: ^
  74. stagas but i don't know what i'm supposed to do
  75. stagas i see the code on the web app
  76. stagas when i switch the branch
  77. stagas so it's there
  78. phaleth yeah, ok, good
  79. phaleth so you did do `rp bootstrap` and so on
  80. stagas yes
  81. phaleth now everytime you want to make a change you need a task, that's mandatory
  82. phaleth rp task create --help
  83. stagas i am expecting to see issuebox deployed, it's a Bun app
  84. phaleth rp task create --title "Some change" --file some_md_file_with_desc.md
  85. phaleth file is optional
  86. phaleth I dunno how to deploy, but clanker should be able to figure out from seeing the output of rp bootstrap which gets stored to AGENTS.md in the project
  87. phaleth rp app --help
  88. phaleth the deployment does not happen automatically even if you have Containerfile in the root of the project
  89. stagas tldr
  90. phaleth cause app name is needed as far as I can tell and also the source branch
  91. blue stagas: if you tell clanker to deploy it, it probably will. just tell it to use `rp app` to create app and deploy
  92. blue it should figure it out on its own
  93. stagas feedback: the happy path should be guided, now it's all the same weight, tons of information everywhere, i can't grasp it
  94. stagas ok let me try
  95. phaleth no need to grasp rp CLI as a whole
  96. blue yeah, most of its info is for your agent really
  97. phaleth the mail server is gonna be offline for a few mins
  98. blue k
  99. dreamreal so it's time to try to log in, is what you're saying? :D
  100. phaleth maybe
  101. blue dreamreal: https://superarch.org/rp-chat.mp4
  102. blue yes, I know, no audio, but it gets the gist of the thing across
  103. dreamreal blue: that's effective but you need to do it like a presentation
  104. dreamreal https://enigmastation.com/2014/07/11/repost-some-suggestions-for-those-making-presentations/
  105. blue I suck at those, need to hire someone
  106. blue anyway, watch the video, you'll get it
  107. dreamreal I do, but that's because I'm pretty good at doing exactly that
  108. dreamreal and note that I wrote that to help people do those kinds of presentations because they're hard: you're exactly the type of audience it was written for
  109. dreamreal (I'm also in that set, but I also follow my own damn advice)
  110. blue note that chat is missing A LOT of functionality I'm planning for it. like automatic turn-taking (review-impl-review-etc)
  111. stagas feedback: it shouldn't create a repo for me, i have a repo locally, i should push it and it should pick up the first branch i push to use that for deployment
  112. blue gotcha stagas. generally speaking, you can also import from another git forge. for local repos I usually force-push
  113. blue we're currently limited to master as the primary branch, lots of complexity involved in making that changeable, but it doesn't really matter for git
  114. blue did it deploy your app successful? or did you have any issues?
  115. blue successfully*
  116. stagas i have a cors issue with creating an issue in issuebox
  117. stagas how do i use chat/task now to solve it?
  118. stagas https://issuebox.repopack.app/
  119. nevet issuebox — Visual issue notes
  120. blue You click on Agent Workspace and connect it to your harness, which I assume is codex
  121. dreamreal Hmm, I wonder if I should update that post
  122. blue there should be instructions
  123. phaleth one sec
  124. dreamreal the examples are all badly dated, and there's more to add now
  125. blue wow, looks cool stagas, it did deploy it
  126. blue stagas: anyway, first connect your harness to chat. the instructions should be fairly smooth
  127. blue you configure it with `rp agent configure`, choose codex
  128. stagas but i don't have credits
  129. blue use a free model. do you have opencode installed?
  130. phaleth stagas: give me a moment, maybe it's the proxy causing the CSP problem
  131. stagas i uninstalled it
  132. stagas i have kilo only and chatgpt
  133. blue hm, I wonder if it's possible to use free models with opencode
  134. blue otherwise I'll look into supporting kilo
  135. blue sorry, free models with codex*
  136. stagas i don't think so
  137. phaleth stagas: there is no CSP header on the proxy https://i.imageupload.app/4533d276d844e737248c.png
  138. stagas blue: i will continue tomorrow when my codex usage resets so i can connect it
  139. blue alright stagas, no worries
  140. blue I'll look into kilocode integration
  141. blue dreamreal: yes, it makes sense to try again. however `rp agent` doesn't support mac yet, do you have your models run on mac, via claude code?
  142. blue (Repopack Chat doesn't have claude code support either; and I don't know if there's something similar to bubblewrap on mac)
  143. phaleth actually, there is no CSP problem on https://issuebox.repopack.app/ it's just the dark reader extension messing it up for me again :D
  144. nevet issuebox — Visual issue notes
  145. dreamreal Models that run on the mac would be running via llama.cpp
  146. * blue pretends he knows what that is
  147. dreamreal local API for LLM models
  148. dreamreal so "on the mac" is running native
  149. blue that's how you run stuff?
  150. blue what about isolation?
  151. dreamreal I rarely run local
  152. dreamreal and you can run virtual even there
  153. blue so where do you run your models?
  154. stagas blue: yeah take a look at kilo desktop app, i think it has the best chat of all. from the video i checked it looks nice
  155. dreamreal *sigh* It depends on what you mean by "my models" - I have access to a lot of external servers and I use them regularly, although I AM running a model locally right now
  156. blue alright stagas, cool, thanks
  157. blue dreamreal: well rp needs a *harness*. it currently supports opencode and codex, but essentially it could support anything that has a server mode. but it *needs* a harness
  158. dreamreal Right, right now my harness for *main* work is claude, controlled via herdr
  159. dreamreal when I get rex access I'm going to try that
  160. blue ok, claude code it is
  161. blue dreamreal: so the point here is, I don't know how you use herdr to organise stuff; but on Repopack, organisation is per-project; in your case, ui-primate would probably be a project, as well as streampack. that allows really nice & clean context switcher
  162. blue also, the fact Repopack melts issues+prs into tasks is an immense improvement, keeping work tracked for AI/humans
  163. blue the next thing I'm tackling in Repopack Chat is how to work with stacks effectively
  164. blue I'm gonna build a few tools into Repopack Chat that allow you to fork off work from a task
  165. dreamreal *nod*
  166. blue that's *a lot* of optimisation, both perf & ui, that's gonna go into Chat in the next days, but it was important for me to get it going so I can dogfeed on it
  167. blue there's*
  168. blue but essentially, you don't have this kind of integrated system anywhere
  169. blue redeploying
  170. phaleth https://justfuckingusego.com/
  171. nevet Just Fucking Use Go
  172. blue lol
  173. blue Amen to that.
  174. blue dreamreal: what's stopping you from using Repopack Chat? Claude Code support as a harness?
  175. blue tell me what you need
  176. stagas nice that chatgpt continue to work after you run out of codex usage, what i'm doing now is telling chatgpt create me this in html/js, then i copy paste to the free model and tell it integrate it, which is easy and can do it
  177. dreamreal I don't use repopack enough, I'm trying to introduce changes to workflow gradually more than anything else
  178. dreamreal i.e., I need the fabric of space and time warped
  179. dreamreal (it's definitely me, not you)
  180. blue yes I use that as well, stagas
  181. blue dreamreal: I know it's hard, but trying migrating *one project*. could be a small one. once it clicks, I think you're gonna get it
  182. blue I never wanna go back to issues and prs now, it feels like a primitive system
  183. dreamreal Well, I'm not gonna have a choice, myself :D
  184. blue how do you mean?
  185. blue I'm not talking about your work projects :P
  186. dreamreal I know, but that's my point: I can't migrate my work projects so I get to duplicate workflows in rather different ways :D
  187. dreamreal I'm cognitively flexible but daaaaaang
  188. blue it's funny how everyone is accustomed to github, and everyone knows github is terrible... but no one is trying to actively move away
  189. dreamreal Momentum is a thing. I'm actually more constrained by gitlab.
  190. blue you have stuff on gitlab? oh lord
  191. dreamreal That's actually $dayjob
  192. dreamreal well, one of them
  193. blue well, once we get funding for repopack, we'd have the ways and means to offer enterprise support
  194. dreamreal so I get to use github for one, and gitlab for another, and urrrrgh
  195. blue gotcha
  196. dreamreal and the chances of MY enterprise moving off are, uh, not infinitesmal but even worse
  197. blue my productivity has significantly improved after moving to repopack
  198. blue but I'm biased
  199. dreamreal Yeah, well, the US senate would have to be involved
  200. phaleth heh, today in gitlab at work I commented on an already merged merge request and then that comment kept appearing on every new merge request I created after, then I deleted that comment on the original merge request and it dissapeared everywhere else
  201. dreamreal and I don't think that's... likely
  202. blue oof phaleth
  203. blue wait, the US senate would have to be involved in your getting off gitlab?
  204. dreamreal yes
  205. blue holy cow
  206. dreamreal When I say we have constraints, including legal ones, I actually mean it
  207. dreamreal TF did you think I meant :D
  208. blue well then you can ditch github, no?
  209. blue I thought github was for work
  210. dreamreal I have multiple roles
  211. dreamreal both for customers for whom decisions are constrained
  212. blue *nod*
  213. * blue looks nevet
  214. * blue recognises nevet isn't contrained
  215. dreamreal see, streampack is indeed my personal project and it is not constrained
  216. * blue beckons nevet to come to Repopack
  217. dreamreal but thats' where I say my cognitive facilities struggle, because github's stupid issue management is largely the same across all my source control systems
  218. dreamreal like I said, me, not you
  219. blue fair
  220. blue when you're ready, tell me, you might be the early adopter of the next big thing :P
  221. dreamreal would not hate it
  222. dreamreal we might be stuck on java 17 for a freaking YEAR
  223. blue oh lord
  224. dreamreal drives me crazy
  225. dreamreal we need 21+ so bad it's not funny, and really 25+, but we're probably going to be accepting 25 right when 29 is out
  226. blue java 17 sucks...
  227. dreamreal no, but it's nowhere near as good as 25, esp for our purposes
  228. blue at work, we have 21
  229. blue and that's only after I petitioned for it for like nearly forever
  230. dreamreal and 29 will be even better
  231. dreamreal 25 has FFM
  232. dreamreal 21 has virtual threads
  233. blue and Wasm
  234. dreamreal both huge wins
  235. blue 25 has Wasm
  236. blue that's the hugest win
  237. dreamreal 29 will have better memory
  238. dreamreal wasm isn't a factor for us at all
  239. blue btw, java wasm is coming to primate
  240. blue probably not in .46... but possibly .47
  241. blue stagas: do you think it's worth switch to Astra for the really good stuff I need?
  242. blue I feel even Sol 6.2 is sometimes missing the quality I need.
  243. dreamreal That sounds like you're offloading too much to the model
  244. blue like, I keep iterating on Repopack Chat. But Repopack Chat is very complex, I feel it's not getting the point
  245. dreamreal the midrange models shoudl be good enough
  246. blue hm, maye
  247. dreamreal What does your agent control look like
  248. blue maybe*
  249. blue wdym with agent control?
  250. stagas it's 5x the cost, so if you find yourself doing 15 prompts on Sol to achieve something then maybe Astra is better
  251. blue I just keep revisiting the same point, I feel
  252. dreamreal blue: AGENTS.md, etc
  253. stagas i would do it if i thought the task needs real depth
  254. blue dreamreal: https://repopack.com/project/primate/code/blob/AGENTS.md
  255. blue the one for repopck project is similar
  256. stagas blue: btw what is chatgpt Work, do you use that?
  257. blue stagas: I haven't heard of it...
  258. stagas in the chatgpt app (and i think the web also) there is a switch at the top 'Chat | Work'
  259. stagas when you are using chatgpt, not codex
  260. blue oh
  261. dreamreal Hmm, first glance, that feels like it's instructions about how to work within repopack with flog and primate but not quite so much about how to WORK
  262. blue I'm not entirely sure, stagas. I feel it might be something similar to codex desktop maybe?
  263. stagas it prompted me to switch the chat there when i was asking for stuff
  264. blue oh
  265. blue idk dreamreal, tbh I often feel that agents.md engineering is more hearsay than actually worth anything. I often see agents flat out completely ignoring stuff there, so I take it with a grain of salt
  266. stagas it said it can do more tool calls etc
  267. blue a bit like SEO: everyone claims it's a thing, no one can prove it
  268. stagas i'll try it
  269. blue k
  270. blue the funny thing stagas, 'tools' are just snippets of text
  271. dreamreal blue: that's usually because they're too long :D
  272. blue in the end all this AI world are just text, text, text stuff
  273. blue MCP is an exception though
  274. stagas isn't it functions? in the API you can pass a set of functions that the agent can call
  275. blue nope. tools are textual descriptions
  276. blue MCP has functions though
  277. blue it's basically a json-rpc API
  278. blue with 'tools' to describe the endpoints
  279. blue my point is, a lot of the things around agents are like a haze of people using terms in weird interchangeable ways
  280. blue for exapmle, people call codex or opencode agents... they are more like agent harnesses
  281. blue but the term 'agent' itself is very fluid
  282. blue an MCP server is basically, you telling an agent (=a chat session) that you offer programmatic access, and how to use it
  283. blue and that programmatic access is encoded in a certain formal way, using json rpc
  284. blue but otherwise it's all text
  285. blue and those agent harness like opencode/kilo/codex/claude code, they have frontends and backends
  286. blue repopack chat is a pure frontend, utilising only their backend part
  287. blue other frontends are tuis (like opencode) or desktop apps (like claude desktop)
  288. blue so an agent harness frontend could be a web app (repopack), a tui (opencode tui frontend), or a desktop app (claude desktop)
  289. blue but all of them use the same harness backend in the same
  290. blue it actually sounds more confusing than it is

Search posts