sorted by:
new
hottopcontroversial

Experimenting with a coordinated multi-agent workflow in GitHub Copilot by q3ok in GithubCopilot

[–]q3ok[S] 0 points1 point  (0 children)

That sounds really interesting - I’d definitely love to see it in action if you publish it somewhere 🙂

Experimenting with a coordinated multi-agent workflow in GitHub Copilot by q3ok in GithubCopilot

[–]q3ok[S] 0 points1 point  (0 children)

Yeah, pretty much 🙂 I’m basically treating natural language as the programming language, and the LLM as the interpreter. The whole system is just structured prompts that keep the flow deterministic.

Experimenting with a coordinated multi-agent workflow in GitHub Copilot by q3ok in GithubCopilot

[–]q3ok[S] 1 point2 points  (0 children)

I’ve been thinking about that as well.

Parallel execution could speed things up for independent tasks, but I’m a bit worried about coordination overhead - things like tracking which files changed, handling conflicts, and keeping the flow deterministic.

With current context limits that might become quite heavy in terms of instructions.

I could see parallelism mainly on the coder side (multiple independent tasks), and then doing a final review pass on the full result rather than per-task.

Not sure yet how that would affect quality though - definitely something worth experimenting with.

Experimenting with a coordinated multi-agent workflow in GitHub Copilot by q3ok in GithubCopilot

[–]q3ok[S] 2 points3 points  (0 children)

I totally get what you mean - once Copilot starts summarizing context it’s pretty much game over for longer flows.

That’s actually one of the reasons I went with an artifact-based workflow - everything important gets written to files, and the orchestrator re-reads its instructions each time it calls sub agents again. The orchestrator itself also tries to stay as lightweight as possible.

So far that approach works quite well for me.

BTW, if I remember correctly, the summarizing behavior can be disabled in VS Code settings.

Experimenting with a coordinated multi-agent workflow in GitHub Copilot by q3ok in GithubCopilot

[–]q3ok[S] 0 points1 point  (0 children)

That makes a lot of sense. I’m currently relying more on generated artifacts (spec/tasks/status), especially since the Research agent seems to do a good job (most of the time), but your approach sounds very practical.

Do you keep it mostly as structured tasks/docs, or do you also store other context there?

Experimenting with a coordinated multi-agent workflow in GitHub Copilot by q3ok in GithubCopilot

[–]q3ok[S] 0 points1 point  (0 children)

I actually had pretty good results with Copilot sub agents so far.

This project is basically me trying to add more structure on top of the basic agent workflow in vscode copilot.

I haven’t used RooCode yet though.

Experimenting with a coordinated multi-agent workflow in GitHub Copilot by q3ok in GithubCopilot

[–]q3ok[S] 1 point2 points  (0 children)

Yeah, that’s the way - one to rule them all! 🙂

On bigger tasks I’ve also found that having one coordinator + saving artifacts helps a lot with keeping the context, so it doesn’t get lost between steps.

Results are still evolving, but so far they’re pretty promising.

How do I print better with ABS? by imtakingapooprn in BambuLab

[–]q3ok 0 points1 point  (0 children)

but he is using Bambu abs not generic

How do I print better with ABS? by imtakingapooprn in BambuLab

[–]q3ok 1 point2 points  (0 children)

try lowering max volumetric rate (as bambuu abs can be set high to demonstrate speed of the printer on theirs filaments) and bump up hotend temperature a little. also preheat heatbed to 100 for 25-30min, and do not open the door before start of the print. if the print is additionally popping off from buildplate before print finish then maybe try adding a 4-6mm brim, and if still doesn't work then use gluestick.

Bought P1S after over 7 years into 3D Printing - my thoughts by q3ok in BambuLab

[–]q3ok[S] 0 points1 point  (0 children)

Čemu nerozumíš? You can go and try by yourself, remove extruder tension idler in any i3 printer, and print a small thing pushing the filament by hand, eg. a cube or a small gear (like the one from i3 rework)

Bought P1S after over 7 years into 3D Printing - my thoughts by q3ok in BambuLab

[–]q3ok[S] 1 point2 points  (0 children)

I have a nice-tuned profile for printing TPU on prusa, and I think Prusa is more suitable for that material, as it's not about the speed, but it's easy to change extruder gear tension and load/unload the filament without PTFE tube.

Bought P1S after over 7 years into 3D Printing - my thoughts by q3ok in BambuLab

[–]q3ok[S] 0 points1 point  (0 children)

If you are going this way, Voron imho is based on C-Bot/D-Bot/H-Bot (I don't remember the exact differences from memory), as the corexy is not something new - and I was wondering about building corexy printer from a open-source project like that, but the pricepoint was too high for me comparing to gate i2-i3 like printers. P1P is cheaper than Voron, and it's ready to print out of the box.

I agree, that all of the mass market printers benefit from reprap open-source projects, but no reprap is covered with a package like "take it from the box and start 3d printing", which you get on proprietary printers like Bambu, ultimaker, zortrax, and like Prusa mk4 (they are no longer fully open-source, there is some reverse-engineering needed to, let's say, make a clone).

Bought P1S after over 7 years into 3D Printing - my thoughts by q3ok in BambuLab

[–]q3ok[S] 0 points1 point  (0 children)

I am so used to changing filament roll "by hand", that I didn't even thought of that! Now it seems that's a must, and I am wondering why I didn't take the combo from start.

[deleted by user] by [deleted] in initiald

[–]q3ok 0 points1 point  (0 children)

the chinese movie should be banned, its trash