Don't be like these guys. Don't try to secretly scoop others when u hear about their potential success especially those with far less resources & power. Learn to give credit where it is due. Collaboration & healthy competition is the best way forward for science. Not this.
@iskander I like imp because it packs all useful stuff that you get from codex (spealized subagents) or claude code (advisor guardrails) but you have much more control
@iskander These are probably not available until you set up the provider, unless you have API keys in the environment. I use with Antigravity (I have the cheapest Google one) and with my Composer. The first one is very fast, and the second fixes the first.
I saw that #20157 recommends persistent workers pulling tasks through claim_task, with the contract documented in pr 23483
For this use case, would you recommend:
building a persistent pull-based worker around claim_task, or configurable non-profile spawn path proposed in #64906?
@Teknium I’m experimenting with Kanban workers that execute outside the standard Hermes profile/harness path. This would let us use models available only through their native harness and control the worker’s context, while Hermes still owns claims, heartbeats, task state, etc.