这两天看都在吹agy什么orchestrator,这帮死.➗是都没见过好的吗,omp早有这个功能了,而且还能接本地模型。
话又说回来总体来说gemini还是好用的,反正我现在没什么重度开发工作没觉得argon像x上说的那么不堪。总之就是一个好模型被捆绑在烂壳子里了。要不以后就直接买api不订subscription不知道行不行。
这两天看都在吹agy什么orchestrator,这帮死.➗是都没见过好的吗,omp早有这个功能了,而且还能接本地模型。
话又说回来总体来说gemini还是好用的,反正我现在没什么重度开发工作没觉得argon像x上说的那么不堪。总之就是一个好模型被捆绑在烂壳子里了。要不以后就直接买api不订subscription不知道行不行。
#588341 [release-26.05] matrix-continuwuity_latest: 26.9.3 -> 26.9.4
#588338 matrix-continuwuity: 26.9.3 -> 26.9.4
#588331 python3Packages.semgrep: mark broken
#588323 omp: 18.18.9 -> 18.20.1
#588318 neowall: 0.8.0 -> 0.9.0
#588341 [release-26.05] matrix-continuwuity_latest: 26.9.3 -> 26.9.4
#588338 matrix-continuwuity: 26.9.3 -> 26.9.4
#588331 python3Packages.semgrep: mark broken
#588323 omp: 18.18.9 -> 18.20.1
#588318 neowall: 0.8.0 -> 0.9.0
Orchestrate many Claude Code, Open Code, and omp CLI instances in parallel from Elixir, with zero-zombie subprocess management, structured JSON/RPC I/O, and ⋯
Licenses: Apache-2.0
Orchestrate many Claude Code, Open Code, and omp CLI instances in parallel from Elixir, with zero-zombie subprocess management, structured JSON/RPC I/O, and ⋯
Licenses: Apache-2.0
I use Pi and OMP and I think the sweet spot is somewhere in between those 2.
Besides harness I think you summarized pretty well the major problem I'm seeing on companies adopting agentic development: lack of direction and someone up the hierarchy whose role is to deny features.
I use Pi and OMP and I think the sweet spot is somewhere in between those 2.
Besides harness I think you summarized pretty well the major problem I'm seeing on companies adopting agentic development: lack of direction and someone up the hierarchy whose role is to deny features.
I'm using omp with glm-5.3-flash to recover it -- it's decompiling from the build folder and looking at session transcripts that created it.
I'm using omp with glm-5.3-flash to recover it -- it's decompiling from the build folder and looking at session transcripts that created it.
#589034 nono→0.82.0
#588511 npm-groovy-lint→19.0.1
#588461 nwg-panel→0.12.4
#585570 ocaml→4.14.5
#585466 ocamlPackages.alcotest→1.10.0
#588519 omniwm→0.8.0
#589030 omp→18.20.3
#588473 openpgp-card-tools→0.11.16
#589050 openspec→2.0.0
#589034 nono→0.82.0
#588511 npm-groovy-lint→19.0.1
#588461 nwg-panel→0.12.4
#585570 ocaml→4.14.5
#585466 ocamlPackages.alcotest→1.10.0
#588519 omniwm→0.8.0
#589030 omp→18.20.3
#588473 openpgp-card-tools→0.11.16
#589050 openspec→2.0.0
- it's too reliant on omp for some fucking reason; why did i make it this way
- its using python (tho i think this would unfortunately stay for a "complete" release; discord.py is just too good).
- i don't have "generic" orchestration systems - i have *one* specific orchestration network.
- it's too reliant on omp for some fucking reason; why did i make it this way
- its using python (tho i think this would unfortunately stay for a "complete" release; discord.py is just too good).
- i don't have "generic" orchestration systems - i have *one* specific orchestration network.
keep cooking @can1357
keep cooking @can1357
Huit outils, huit dossiers de config. Chez moi ils lisent tous le même dépôt : une skill ajoutée une fois apparaît partout.
Changer d'outil devrait coûter un lien, pas une réinstallation.
Huit outils, huit dossiers de config. Chez moi ils lisent tous le même dépôt : une skill ajoutée une fois apparaît partout.
Changer d'outil devrait coûter un lien, pas une réinstallation.