Submit

Back to the channels

#primate

  1. * phaleth joined #primate
  2. blue new in rcompat, .md pages available https://js.stdlib.run/packages/http.md ; https://js.stdlib.run/api/http.md, as well as https://js.stdlib.run/llms.txt and https://js.stdlib.run/llms-full.txt
  3. phaleth hi blue
  4. blue hi phaleth
  5. blue what's up?
  6. phaleth just looking at if repopack issue count increased again
  7. blue chat is coming along so nicely
  8. blue you can now fork off task chats from a Steering conversation, and also set them to autorevise and autoreview, as well as fork the review to a new tab
  9. blue I think the two bigger things that remain for now with chat, is stacks, and claude code integration
  10. blue then I can move all my work from my tmux sesions into repopack.com
  11. phaleth does that mean it's easier to manage multiple clankers?
  12. blue yes, much easier
  13. blue and then I'll also get me a vps where I can run `rp agent`
  14. blue so it doesn't run on this computer
  15. phaleth but your laptop can handle the browser client right?
  16. blue the browser client is nothing
  17. phaleth and tokens get burned out fast anyway I guess
  18. blue the problem is tens of agent sessions all running, compiling go, compiling cit, running node
  19. phaleth clanker needs podman and so on I guess, but still
  20. blue repopack.com doesn't actually use podman, it uses bwrap
  21. blue or well, I mean `rp agent` uses bwrap
  22. blue anyway this means I can offload most of the copmuter from my laptop onto repopack.com. repopack.com manages the frontend, and the vps manages the backend
  23. blue the 'vps' is what we will in the future sell as 'hosted agents'
  24. blue most of the computation*
  25. blue oh man this will save me so much boilerplate
  26. blue I spent a lot of my time now writing clankers "revise #1016", "review #1000"
  27. blue this is all going to be automated
  28. phaleth it cannot be that bad, I mean, there is a ton of TS code, but maybe that's just has to be taken care of
  29. phaleth cause that laptop is a beast
  30. blue gets hot fast
  31. blue especially with cit and compilation
  32. phaleth also you might wanna think of having a builder machine and just tell clanker how to use that
  33. phaleth cause the code will be uploaded fast I'm sure
  34. phaleth but you know still control the whole thing from your laptop
  35. blue yes that's gonna be part of repopack.com. we'll have packages @repopack/build and @repopack/test for offloaded tests. those are also necessary for the sandboxed agent sessions
  36. blue the sandboxed agent sessions have tools, too
  37. phaleth also consider just using the existing VPS, it's already overpowered
  38. blue I thought you were against me running clankers on it
  39. blue to be fair though, it would be running under blue without sudo
  40. phaleth well if they don't put their nose into /opt/haproxy
  41. blue they can't, without sudo at least, unless blue can
  42. phaleth then that's fine, that means they cannot even read repopack.env
  43. blue ok let me try that
  44. blue though I want to complete my existing sessions, since moving rp agent would disconnect those. but actually I think most of my chat sessions are done
  45. phaleth it's just like you know, not really used at all, and I tend to compile a lot of go there and the performance of the VPS is still good
  46. phaleth I mean responsiveness of websites and so on
  47. blue ok, I'll install codex since it's better than opencode I think
  48. phaleth but really just start a concept of a builder
  49. blue or well, 'install' it into my profile
  50. phaleth I'm still not sure why you updated the VPS btw, 12 GB RAM was more than enough
  51. blue Because it was for free
  52. blue same price double RAM, why would I not update it?
  53. phaleth oh, really, nice
  54. phaleth so it's still about 7 euro?
  55. blue yes
  56. blue the price didn't change
  57. phaleth damn, and it got 2 cpu cores extra
  58. phaleth I mean shared, but still
  59. blue yes
  60. blue phaleth, added you to contabo
  61. blue you've received the invitation as your @repopack.com addr
  62. blue S3 Read, S3 Read and Write, Technician, Abuse & Fraud
  63. blue those are the permissions
  64. blue Technician gives you full access to managing stuff
  65. blue the only permission you didn't get is invoice/billing, because it has my personal CC data
  66. phaleth ok, I will register then
  67. blue anyway, current monthly total price is 16.07 EUR including VAT
  68. blue server itself is 9.52, autobackup is 1.19, mail server is 5.36
  69. phaleth yeah, not too bad
  70. phaleth but new VPS not needed still, just saying
  71. blue yes, will run codex under blue
  72. phaleth they require a card number
  73. blue a card number?
  74. blue weird
  75. phaleth codex looks like something that should be more efficient than the other CLIs
  76. blue yes
  77. blue another clanker is working on adding: `rp task verify`; this will reuse blueprints to run stuff on the server, allowing the task chats to not need ot run it locally
  78. phaleth nice
  79. * phaleth quit (Ping timeout: 266 seconds)
  80. * phaleth joined #primate
  81. * nevet joined #primate
  82. * blue!~blue@user/blue changed the topic to: https://primate.run | This channel is logged: https://bytecode.news/logs/irc/libera/primate
  83. * dreamreal joined #primate
  84. phaleth tried to update flog to golang's new json API and after it finally compiled i got a bunch of test failures https://upaste.de/raw/zP3
  85. blue oof phaleth, is that in the latest go?
  86. phaleth yeah 1.27.4
  87. phaleth well, I got the executable
  88. phaleth -rwxr-xr-x 1 user user 17M Nov 22 20:29 main
  89. phaleth it's just it's impossible to compete with clanker when it wrote so many tests
  90. phaleth :D
  91. blue lol
  92. blue phaleth: Task compute is coming.
  93. blue I also hope to be able to cut Primate 0.46 next week
  94. * lioloc quit (Server closed connection)
  95. * lioloc joined #primate
  96. blue ok, configuring rp agent+codex on the vps, phaleth
  97. phaleth ok
  98. blue trying with --task-compute, let's see if that works
  99. blue or I mean, --enable-compute
  100. blue [blue@vmd170320 ~]$ rp agent start --enable-compute
  101. blue Task Compute unavailable: expected a local rootless Podman engine. Fix local rootless Podman or start without --enable-compute
  102. blue :(
  103. blue don't we have rootless podman on the vps?
  104. blue oh nvm, it's an rp bug
  105. * jreicher quit (Quit: In transit)
  106. phaleth rootless podman should work, it might just output some warning regarding user linger
  107. blue yes, rp falied on those, fixing
  108. blue phaleth: json/v2 is amaze sauce
  109. phaleth but that can be ignored since all containers are temporary
  110. phaleth yeah, saves some lines of code :)
  111. blue maybe can be adapted for the js std
  112. blue std:fs/v2 ... would be cool
  113. phaleth well I have no chance fixing all those tests
  114. phaleth anyway, time to crash
  115. blue ciao, have a good night's sleep
  116. * phaleth quit (Quit: phaleth)
  117. * jreicher joined #primate

Search posts