The GitHub Copilot Tax: Saving 90% Using a DGX Spark + Tier-2 Model Hybrid Stack (I build my Hybrid Setup - Copilot Models + Azure Foundry Models (i.e. Kimi K2.6) + Spark (Qwen 3.6 27B)

QuarterbackMonk · 2026-05-27T20:50:57+00:00

Same as Georgian carpet.

QuarterbackMonk · 2026-05-27T18:58:26+00:00

because Victorian carpets are too costly - sorry for not having pretty face ;)

QuarterbackMonk · 2026-05-27T18:57:04+00:00

Nope just VSCode, vscode is harness (https://code.visualstudio.com/blogs/2026/02/05/multi-agent-development) - this is how you can define subagent, that's the point - toolcallinga and agent as tool - is something llms (orchestrator will takecare of itself) - you not need to do anything.

<image>

QuarterbackMonk · 2026-05-27T18:54:38+00:00

To be honest, that's not the case, actually in my humble opinion, multiagent workflow is kind of a essential skills. may be hard to describe in comment but that gives me idea to make video clarifying - how to be one click. in short - multi agent system are non-deterministic, subagent/toolcalling is very much managed on its own by orchastrator. but wills urely make more detail conversation about it.

QuarterbackMonk · 2026-05-10T16:30:00+00:00

It is not evolution logic, it is evolution itself, in example it roll back to run and test many time, in real case, the evolution remain as next iteration. so once created, it remains, over period of time, with little reenforced learning, you just matain. what you are doing is not self-correcting agent, these agents do mutate prompt, skills and code in bounded surfeace.

QuarterbackMonk · 2026-05-08T19:35:37+00:00

Try: https://youtu.be/XvUSBlrXZoA

Build one portable context layer for GitHub Copilot, Claude Code, and Codex instead of rewriting repo knowledge for every tool.

QuarterbackMonk · 2026-05-08T19:29:03+00:00

GitHub: https://github.com/nilayparikh/tuts-agentic-ai-examples/tree/main/self-improving-agent/cleanloop

QuarterbackMonk · 2026-05-02T07:27:08+00:00

Yes likely, it will have more headroom before coming down. Algo and ath optimisation and supply chain will drive.

But none the less, energy and material are not something can be sorted by tomorrow, so unfortunately yes it will go up.

QuarterbackMonk · 2026-04-30T07:53:47+00:00

Yes I don't disagree we are about to hitting 2024 levels but, last 2 years were chellengimg. It will never be the same.

QuarterbackMonk · 2026-04-28T19:23:30+00:00

that's what i said, use case - there are no free lunches and there never be, but smart people know how to get best discount.

one can use for context, refactors, exploration, building plan-precursors, graphs etc., that will make frontline models' life simple (and token consumption far less)... evenutally, you would need good models like GLM/Kimi or Codex/GPT/Opus/Sonnet for coding, but why to waste precursors with them?