Submit

Back to the channels

#primate

  1. * phaleth joined #primate
  2. blue Hi phaleth.
  3. blue phaleth: https://github.com/primate-run/primate/issues/286
  4. nevet pema: `p.loose.bigint` / `i64` / `u64` / `i128` / `u128` coerce numeric strings via `Number()`, losing precision above 2^53 · Issue #286 · primate-run/primate
  5. blue Primate is commited to delivering in record time :P
  6. blue I used that report as a reason to introduce changelogs per package, which is kinda cool
  7. phaleth hi blue
  8. phaleth a research group led by Professor Yu Feng
  9. phaleth looks like they don't care how is that implemented
  10. blue how what is implemented?
  11. phaleth the number overflow
  12. blue well it's good we got their attention
  13. blue also, we're the fastest in delivering fixes, less than an hour from the original report to patch on npm
  14. phaleth yeah, but it's a lot of mess in the code https://repopack.com/project/primate/tasks/414#file-70c75a59428a18c31f4c3a38
  15. phaleth only a student would be worried about 2^53 overflow, practically that's not going to happen
  16. blue I see if I can move some of the complexity into rcompat
  17. phaleth well, would be nice if a lot of the JS clanker recently added to the website's app js bundle would go away
  18. blue what JS clanker?
  19. blue can you create task?
  20. phaleth I mean the JS that clanker recently added
  21. phaleth nah, prolly waste of time, and clanker has no chance anyway
  22. blue but where? what task?
  23. phaleth all of them I guess, like each release adds more and more kBs
  24. phaleth it used to be at around 71 kBs
  25. blue can you create task so I can review this? just write it used to be 71kBs and now it's whatever, and I'll look into it and figure it out why
  26. blue also I didn't update repopack.com yet to primate .45, still need to do it
  27. phaleth don't worry, it does not matter
  28. blue I think it does matter if it bothers you :{
  29. blue :P*
  30. phaleth yeah, would be nice if there was some work done for repopack
  31. phaleth just saying that bloat is being added
  32. blue in primate or repopack?
  33. phaleth I mean you've propably promised those 64 bit ints in pema or whatever, so that bored student chuckled over it
  34. phaleth but in the end who cares if somebody runs into a bug there
  35. phaleth both
  36. blue well please create tasks, I will look into it, memory consumption is kinda good in repopack, it's been running for a while and it's at 288MB
  37. phaleth but I've already created other tasks that are more important
  38. blue k
  39. blue major chat update is coming, phaleth
  40. blue and btw you can use with free models :)
  41. phaleth oh, hmm
  42. phaleth last time I've tried running Mistral on my laptop the laptop was dying
  43. blue we're gonna get hosted agents soon
  44. blue this will be a paid feature
  45. blue and I know dreamreal is gonna love it
  46. blue phaleth: https://repopack.com/project/primate/tasks/423
  47. blue man I REALLY need chat. I keep confusing all those opencode tmux sessions :(
  48. blue I 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
  49. blue imagine how much confusion this causes
  50. blue with 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
  51. blue being always in the context of a project is immensely helpful
  52. blue and btw: I think this is why people use herdr
  53. phaleth yeah, I think so too
  54. blue because they realised tmux with a ton of agent sessions is gonna be totally confusing
  55. blue but repopack.com solves this so nicely. you always have a project context
  56. blue also with hosted agents, I can restart the computer as often as I want. the git checkouts survive because they're not on my computer
  57. blue it's perfect
  58. blue dreamreal: ^
  59. blue I might be wrong, but I think we've hit gold here. only time will tell
  60. blue three workflows:
  61. blue 1) 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
  62. blue 2) 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
  63. blue 3) you buy a hosted agent (essentially a vps or another abstraction) from repopack.com, you don't need to setup anything
  64. blue 3) 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?
  65. blue that's why we have task previews, that's exactly the reason they exist
  66. blue it's a new way to do development
  67. blue radically different, I think, but also very interesting
  68. blue and also crucially, it means your computer can burn down and you don't lose anything
  69. blue and you can do development on a weak(er) laptop
  70. blue your computer becomes a terminal to your development environment, via your browser and repopack.com
  71. phaleth lot of people will pay clanker and be wanting to get clanker hooked up to the project easiest way possible
  72. blue yes
  73. phaleth if you make it so that the person has to write commands in terminal then you've lost them
  74. blue well ideally, they're all gonna work through repopack.com chat
  75. phaleth I mean for hooking up clanker
  76. phaleth like to me the chat says some nonsense cause I have no clanker
  77. phaleth it should shove down a guide how to hook up clanker to the user's throat
  78. blue yes, this is going to change with hosted agents
  79. phaleth also once they set it up it should make them feel like a winner
  80. blue well with hosted agents, there's no setup involved othre than connecting to your provider
  81. blue and if you buy a hosted agents, you would still get the free models immediately
  82. phaleth the gamification aspect is important, people are way too screwed nowadays, especially the youngsters
  83. blue lol
  84. blue dreamreal: you use claude code, correct?
  85. blue I currently only have rp wire opencode sessions. I do need to extend chat to claude code and codex
  86. phaleth and to seepdeek
  87. phaleth oops
  88. blue seepdeek?
  89. phaleth yeah, try saying that
  90. blue seepdeek!
  91. phaleth this is difficult to understand without an example https://docs.repopack.com/start#connect-a-project
  92. blue can you edit it or create task to improve?
  93. blue you don't have to work on the task, just create it
  94. blue I want to make it perfect but I need to know about things that don't work well
  95. blue just create tasks, it's cheap
  96. phaleth yeah, but clanker is just gonna write more walls of texts
  97. blue ignore it, just create tasks, tasks are the cheapest currency we have
  98. blue the walls of texts are something we can work against in AGENTS.md
  99. blue that doesn't make creating tasks invaluable
  100. phaleth so does `rp bootstrap ...` create a project?
  101. blue or well, "not valuable"
  102. phaleth the bootstrap term is confusing
  103. blue it doesn't
  104. blue it sets up a project by cloning it
  105. blue try this
  106. phaleth ah, now I get it
  107. blue mkdir ttt && cd ttt && rp bootstrap primate
  108. blue it will clone the project into ttt/primate, and print instructions. it's mostly for agents
  109. blue if you run rp bootstrap INSIDE a repopack.com project, it will just print instructinos
  110. blue it detects it by looking at the .git/config and finding repopack.com origins
  111. phaleth that information is missing there
  112. blue ya
  113. phaleth clanker would just turn it into a wall of text
  114. blue create task, I will fix
  115. blue or add manually :P
  116. blue either way you need a task for it
  117. phaleth yeah, I will try to read the docs, prolly impossible
  118. blue chat is working REALLY well
  119. blue once I have this deployed, you gotta try it out phaleth
  120. phaleth ok, anyway, I don't have a clanker
  121. blue there are open models
  122. phaleth last time I messed around with LLMs was in 2023 and since then I forgot everything
  123. phaleth I remember I used some python environment thing that was painful to work with
  124. phaleth every single project worked only on specific version of python
  125. blue you just need opencode
  126. phaleth isn't opencode's source closed?
  127. phaleth :)
  128. phaleth I 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
  129. * phaleth looks up if garbage is still running on the VPS
  130. phaleth nope, it doesn't
  131. blue opencode is open source
  132. blue https://github.com/anomalyco/opencode
  133. blue MIT
  134. phaleth wow, it can be installed via pacman
  135. phaleth then it must be important
  136. blue ya
  137. blue anyway try it, rp can connect to it and then you can use the chat :) I'll soon push out this amazing update
  138. blue almost done with it
  139. phaleth my computer does not have a GPU and it's CPU is too old
  140. blue don't worry about it, this is a T480
  141. phaleth yeah, but you use a remote clanker
  142. blue I don't
  143. blue opencode is running on my computer currently
  144. blue I don't have an extra vps atm
  145. phaleth by clanker I mean the LLM
  146. phaleth I found this knob https://i.imageupload.app/0ca74ba34e780ae573b2.png but in rp CLI there isn't anything like `rp task merge .` right?
  147. blue Yes. I think I removed `task merge` from the cli at some point. It should return, but I think it should always guarded
  148. blue Clankers should not be able to autonomously push code onto master. So that will become an always-guarded action.
  149. phaleth yeah, with a permission on the project
  150. blue here, https://repopack.com/project/repopack/tasks/868
  151. blue we don't need a permissoin on the project
  152. blue task merge will always be guarded
  153. phaleth but people also use CLI so it's impossible to distinguish people from clankers
  154. blue yes. but the CLI isn't assumed to be 100% safe
  155. phaleth and people should also be denied to take that action
  156. blue yes
  157. blue anyway can script your CLI
  158. blue the last authority is the website
  159. blue guarded actions always require you manually approving on the ui
  160. blue there are not a lot of them, but important things are guarded
  161. blue s/anyway/anyone/
  162. phaleth ok, that task says: "equires a deliberate human confirmation in Repopack's browser for every invocation"
  163. phaleth requires*
  164. phaleth but how is that confirmation gonna look like? will it be enough that I'm logged in only via rp CLI?
  165. phaleth cause now I have to be logged in on repopack site itself and hunt for the merge button everytime
  166. blue the human confirmation is a popup that appears on the top right in the browser
  167. blue and yes, you wouldn;t need to hunt for the merge button
  168. phaleth yeah, but in the browser after logged in to repopack website right?
  169. blue yes
  170. phaleth well, that's still the same then
  171. blue same as what?
  172. phaleth makes no sense to implement that task at all
  173. blue wait, are we talking past it other? `rp task merge` would allow your clanker to request a merge
  174. phaleth like currently, in CLI you get link to task, open it and hit the merge button there after logging into the website
  175. blue that would show up as a popup on the UI
  176. phaleth yeah, but I'm in role of the clanker too :D
  177. blue that spares you from looking for the task and scrolling down to the merge button
  178. blue if you're in the role of the clanker, that's useless for you, yes
  179. phaleth there is no looking up the task, the URL to the task is already in the terminal after `rp task submit . --push`
  180. blue you wouldn't type `rp task merge`, then go to the website and confirm it
  181. blue you'd just go directly to the website, I agree
  182. blue but human-driving rp isn't the most common use case
  183. phaleth ok, then lets move on, no need to implement
  184. phaleth that means I should enable that knob I shown on the picture above again
  185. blue well arguably it can move things a bit faster... let's imagine I'm in chat
  186. blue then I tell the review clanker, review this task, and if approved, request a merge
  187. blue then it can work in the backgronud and at some point I get a merge popup request
  188. blue I think there is some rationale for that task in the task description
  189. phaleth yeah, 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
  190. blue so the probem is, you cannot distinguish who's driving rp, right?
  191. phaleth I dunno, prolly not
  192. blue it'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
  193. blue an env variable should not become an access gate
  194. blue I believe in repopack, we should have two levels of access. rp and browser. browser can do less actions, but has higher permissions
  195. blue rp can do anything, but important stuff is guarded, because it's scriptable and agent-runnable
  196. phaleth ok, how about doing something like `rp login` does
  197. phaleth it opens up a web browser to confirm and only a human can confirm that
  198. blue rp login just gets you the token
  199. phaleth yeah, I mean that behaviour
  200. blue essentially 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
  201. phaleth so just show a merge button there, no need to logged into the website itself and click some notification or whatever
  202. blue but remember that with rp login, you already need to be logged into the website anyway
  203. blue this is more or less the exact same flow as push popups, just in a new tab
  204. phaleth yeah, that's true
  205. blue I honestly don't even know why we're doing rp login in a new tab
  206. blue should just do a push notif
  207. phaleth so the client would just have to generate a one time token that the server can recognize as something belonging to the user
  208. blue I guess, yeah
  209. phaleth something super obscure
  210. blue phaleth, there's a new feature on repopack.com if you're interested
  211. blue when you're in a project, click on the project switcher
  212. blue the last line allows you to subscribe
  213. blue you can choose which events you're interested in getting informed about
  214. phaleth I see, looks nice
  215. blue the transport mechansim is confirmed in your account settings: any combination of email, bells and push notifications
  216. phaleth I mostly care about tagged releases
  217. blue can you create repopack task for that?
  218. blue `add tagged releases as subscription option`
  219. phaleth ok
  220. blue thanks
  221. blue thanks, I got a push notif for that :)
  222. phaleth heh
  223. * phaleth continues to read those walls of texts
  224. blue https://repopack.com/project/repopack/tasks/918
  225. blue is ok phaleth? it's not a wall of text..
  226. phaleth yeah, that means clicking on that notif will open the release page I guess
  227. blue yes
  228. phaleth ok
  229. blue rp is kinda nice, don't you think
  230. blue can really do cool things with it
  231. phaleth yeah, would be nice if I could merge without logging into the website
  232. phaleth that's the only piece missing I guess
  233. blue that would give rp a lot of power to merge things into master autonomously
  234. phaleth also I dunno if it's possible to list task with review state, but that prolly already is possible
  235. blue maybe we should allow this per rp token, phaleth?
  236. blue so when you do `rp login`, we can could offer an option "Allow rp to merge tasks without confirmation, subject to project settings."
  237. phaleth per project
  238. phaleth oh, that login token, yeah
  239. blue ok, per project is also fine by me
  240. blue my thought about the login token was that you could have your personal rp login on your computer, to merge stuff
  241. blue and then your clanker login on your vps, with no merge capabilities
  242. blue we could even define that that `rp login --headless` never gets merge unguarded merge capabilities
  243. phaleth no clue how that works currently, but I can see on the repopack website there are like a lot of already expired tokens from the CLI
  244. phaleth not sure if they get autodeleted at some point from the db
  245. phaleth yeah, that's a good idea
  246. phaleth I noticed that `rp login --headless` in the docs, but the docs are not telling much I can understand
  247. blue it's mostly self explanatory but should still document
  248. blue rp login --headless will print a url, I think repopack.com/auth/cli/dervice or so
  249. blue [blue@vmd170320 ~]$ rp login --headless
  250. blue Repopack server: https://repopack.com
  251. blue Open: https://repopack.com/auth/cli/device
  252. blue Enter code: REDACTED
  253. blue This code expires in 10 minutes. Waiting for authorization...
  254. phaleth and clankers just curls that url?
  255. blue it's a server-server token exchange, yes
  256. blue you need to authorise the token
  257. phaleth cool
  258. blue this is for environments that have no browser
  259. blue like a vps.
  260. phaleth yeah, that's understandable form the docs, it's just no example there
  261. phaleth from*
  262. blue ok, could you create task to improve that? I will do. no walls of text, promised
  263. phaleth nah, don't worry about it, I just need to read all repopack docs
  264. blue k
  265. phaleth all of those functionalities are going to change several times anyway
  266. phaleth at this stage docs are just a pure waste of time
  267. blue yes but remember we will add to AGENTS.md, to update docs on every task
  268. blue and remove as much internal docs as possible
  269. blue anything that's not 'secret' (whatever that is), should be public-facing
  270. phaleth I think then in AGENTS.md there should be something about docs in admin area, if there is going to be anything internal ever documented
  271. blue YES
  272. blue create task?
  273. phaleth at this point, no
  274. phaleth there is nothing internal, except in #392 which should just be closed already
  275. blue 392 is a dumpster fire :)
  276. phaleth wall of text, yeah
  277. phaleth `rp task list --status review` takes a few seconds to respond, is it not like one db query behind the scenes?
  278. blue yes
  279. blue should be faster
  280. phaleth 2 seconds https://upaste.de/raw/bER
  281. blue I'll be looking into it
  282. phaleth ok, great
  283. blue working on perf now
  284. blue phaleth, for the record, at some point we're gonna need to develop our own agent to make things even more streamlined
  285. blue supporting opencode and codex and claude code is nice, but having our integrated agent makes things a whole lot smoother
  286. phaleth I thought the chat replaces opencode
  287. blue no. the chat is not an agent. the chat is a multiplexer over agent sessions
  288. blue it connects to your local opencode/codex/claude code
  289. blue an agent is a complex thing, needing instructions, context compaction, tools, and so on
  290. blue it's doable, but it's not what the chat or rp currently does
  291. phaleth ah, ok, so it could be doing that in the future, but looking at the size of the opencode project that is a huge undertaking
  292. blue yes and no. because our chat agent will be 100% headless, just a server, not a client like opencode/codex/claude code
  293. blue that saves you a lot of complexity
  294. blue all those opencode/codex/claude code are both. they are a server and a client. and I think a lot of the complexity is in the client
  295. phaleth so I don't know how a web browser can control a CLI tool, sounds like there is a security problem
  296. blue our chat replaces the client essentially
  297. blue it doesn't
  298. blue rp starts an outgoing connection
  299. blue the web browser doesn't really control it, it's more like rp connects to repopack.com and they exchange info
  300. blue you could say in essence it does control it, but that's not a real security problem since connection can only be initiated from rp
  301. blue installing or running rp does not allow any repopack.com user to control rp
  302. phaleth yeah, the docs do not explain any of that
  303. blue you need to explicitly run `rp agent start`, and enter the code shown to link it
  304. blue yeah, the docs are also unfinished :P
  305. phaleth https://docs.repopack.com/guides/agent-chat
  306. phaleth wall of text
  307. blue yes, we're gonna need to deal with that
  308. blue believe me, I'll handpick all the docs and make sure they're reduced and understandable
  309. blue and then I'll have dreamreal go over them and scream at me when he doesn't get something
  310. phaleth no, don't worry about the docs, they are a pure waste of time
  311. blue give it some time, all good things take a while
  312. phaleth no no no, no time given to that
  313. blue the docs are actually important because people have been asking for them
  314. blue dreamreal did, as did stagas
  315. blue I can't ignore that forever
  316. phaleth yeah, but those current docs are useless
  317. blue not entirely. they already have structure, and some useful information
  318. blue the problem is they're gonna outdate fast
  319. phaleth so it's like waste of token, and people can type in `rp agent --help`
  320. blue and for that we need to update AGENTS.md
  321. phaleth tokens*
  322. blue ya
  323. phaleth yeah, but if you update rp CLI's help then clanker can figure things out
  324. phaleth and so can people
  325. phaleth no person is gonna read AGENTS.md
  326. blue ya
  327. blue phaleth: you can now subscribe to new releases, too
  328. blue it's deployed :)
  329. phaleth cool, thanks
  330. blue oh man, it's not marked on by default
  331. blue stupid clanker :(
  332. blue need to fix that
  333. blue phaleth, are you on rp unstable?
  334. blue should switch to the unstable channel for now, I'm not cutting releases for everything
  335. blue `rp update --channel unstable`
  336. blue I'm gonna deploy the perf improvement in a few mins
  337. phaleth I think stable but it's working well so far
  338. blue ok
  339. phaleth ok, I could test that then
  340. blue you will need the latest version for the chat. I might cut a new rp version. but for now you can switch to unstable
  341. phaleth I have no local LLM
  342. phaleth but maybe later I can try finding some
  343. phaleth ever since hugging face requires a log in I just don't bother with LLMs anymore
  344. phaleth yeah, clanker is stupid cause of coding this way https://repopack.com/project/repopack/tasks/919
  345. phaleth I mean, by making the problem in the first place
  346. phaleth well, whatever it wrote there looks like a bloat
  347. phaleth ah, so clanker added a bunch of flags to the CLI it seems
  348. phaleth or query options
  349. phaleth on 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"
  350. phaleth that sounds contradictory
  351. phaleth the first statements is most likely wrong, or at least I'd think so
  352. blue ya
  353. blue the problem is phaleth, before it was filtering in the cli, now on the server, that's faster
  354. blue anyway, I merged 919, gonna redeploy
  355. phaleth yeah, figured
  356. blue phaleth: try now
  357. blue rp task list --status review
  358. blue is much, much faster
  359. blue you need `rp update` first and to be on the unstable channel
  360. phaleth yeah, trying to update
  361. blue `rp update --channel unstable`
  362. phaleth much better, yeah https://upaste.de/raw/eA5
  363. blue yup
  364. * phaleth quit (Quit: phaleth)

Search posts