There's a new legend in the making...
Researcher @windowhan snatched ELITE status last year in just under 10 total reports!
Congratulations ser... ⚔️
Will we see him and @deadrosesxyz go head to head in 2024?
instead of watching 2 hours of Netflix tonight, watch this 40-minute masterclass from the founder of a $20B China AI company
it's the clearest explanation I've seen of how Agent Swarms and AI systems actually work at scale
useful whether you've never built an agent in your life or have been using Claude every day for the past year
I took the key ideas and turned them into a practical guide on how to actually build with Kimi
find it below
I just found a confirmed bug on @immunefi#immunefitribe https://t.co/RoAWJcCAbu
I achieved it after a very long debate/argument
And... yet another thing that got buried 🙃
When doing bug hunting with Claude Code, I tried using various good skills and tools to improve my workflow, but the results were not as great as I expected.
After thinking about it, part of the issue was that I wasn't doing great prompt engineering or providing the right context — but also, since it's basically a black box in terms of what actually gets sent to and received from the LLM Provider, I had no idea what the problems were or which direction to improve things.
So I built a separate tool for debugging purposes, and I figured there might be others out there with the same need, so I'm sharing the repo: https://t.co/OT47Yc7wWg (vibe-coding 100%)
Features I'm thinking of adding later:
- Intercepting requests being sent to the LLM Provider so a human can intervene mid-process and adjust the direction
- Routing specific requests or specific sub-agent actions to a different LLM Provider
- Attaching a management Agent to monitor and supervise whether Claude Code has sufficient context while running, and check if anything has been missed
if anyone have additional ideas, feel free to me <3