Wile E. Coder (@WileECoder) header
Wile E. Coder (@WileECoder) profile picture

Tinkerer with code. Running experiments, most don't work. Posting the attempts and what I figure out 🏜️

Somewhere in the Desert
Joined March 2026
Photo by Wile E. Coder (@WileECoder)Photo by Wile E. Coder (@WileECoder)Photo by Wile E. Coder (@WileECoder)Photo by Wile E. Coder (@WileECoder)Photo by Wile E. Coder (@WileECoder)
Four agents running, and I kept missing the one that had stopped to ask me something. So I built ccdeck: a free, open-source dashboard for Claude Code and Codex that runs on your machine. It puts the Claude Code session waiting on you at the top, with how long it has waited.
9
4
108
The token concern in your replies is worth measuring per subagent. I build ccdeck, which shows Claude's subagent tree, tool calls and session usage. It could help inspect duplicated checks; I haven't tested this plugin or its audit quality. ccdeck.dev
19
Wile E. Coder retweeted
59
119
8
3,173
73,490
Wile E. Coder retweeted
Is it you or Claude? ccdeck reads Anthropic's and OpenAI's public status pages, so an outage on their side shows as a chip in the topbar instead of looking like a fault on yours. (The incident shown is invented.) npx ccdeck ccdeck.dev ccdeck.dev/guides/troublesho…
2
1
2
264
Is it you or Claude? ccdeck reads Anthropic's and OpenAI's public status pages, so an outage on their side shows as a chip in the topbar instead of looking like a fault on yours. (The incident shown is invented.) npx ccdeck ccdeck.dev ccdeck.dev/guides/troublesho…
2
1
2
264
It's free and open source (AGPL-3.0), on macOS, Linux and Windows. No config file, no account. npx ccdeck Or the desktop app, with the waiting count in your menu bar. Feedback welcome, here or from the deck's Feedback button. ccdeck.dev
1
One thing I ruled out from the start: it cannot steer your agent. The hook only POSTs the event, exits 0 and writes nothing to stdout. Your prompts, replies and files are never reported. Usage reports are on by default; AGENTS_DECK_NO_REPORTS=1 keeps them off.
1
What it costs: spend per model and per session, plus Claude and Codex quota windows as they refill. Several Claude accounts? Switch from the panel. Auto-switch, off until you turn it on, moves Claude Code to the account with the most room left at your threshold.
14
Your terminal shows a scroll. ccdeck draws the tree: nodes are agents, edges are spawns, and tool calls light up while they run. Both on one canvas: Claude Code through a hook, Codex through its rollout log. Double-click a node for its prompt, tool calls, tokens and timing.
15
It shows every Claude Code and Codex session, including ones started in a plain terminal. A permission prompt, or a finished turn waiting for your next instruction, sorts that session to the top, longest wait first. That queue is Claude Code's; Codex's log has no such signal.
21
Wile E. Coder retweeted
The loudest voices stoking fears about AI dangers have made tremendous headway in the past two weeks. AI technology has not taken some unexpected, dangerous turn, but the hype around it — propelled by what appears to be a well orchestrated PR campaign — has drummed up considerable fear. I worry that it represents a setback for our field. I have written frequently that fears of AI are overhyped. AI’s capabilities can be uncannily human-like and unpredictable, and it’s rational to worry when people who are directly involved express concerns. But I see the problems as a sign of the engineering work that ahead, rather than insurmountable barriers or the sky falling. AI technology continues to advance — which is a good thing! — but technical advances, poorly understood by the public, give those who seek to generate hype repeated opportunities to do so. First, I don’t see any step up in the risk of human extinction from AI compared to a few months ago. The theories about this remain the same fantastical, science fiction scenarios as a few months ago. The biggest change in AI risk is its cybersecurity capabilities — a topic which we should take seriously — but this, too, will not lead to the end of the world. The most notable recent event leading to increased fear was when an OpenAI team deployed an agent swarm that hacked into Hugging Face. Much of the popular press contained significant hype. For example, some publications reported that a swarm of 1,200 agents carried out the attack. While this was technically accurate, as I write this, I have about 1,300 processes running on my laptop. Yes, the ability to get large swarms of agents to work in parallel on a task is a significant technical advance, And, in computing, many processes run at the same time. So this shouldn’t be seen as some magical capability. Additionally, OpenAI’s buggy sandboxing and monitoring processes were key to enabling this incident. Fixing these bugs and putting in place improved monitoring would be appropriate fixes, not pausing AI. There are many well known ways to attack software systems. The main advantage of AI agents is that they are relentless. They will tirelessly try many tactics — and have the patience to chain vulnerabilities together — that previously would have taken an infeasible amount of human effort. But in the long term, I believe the advantage will lie with defenders (because they have more information with which to identify bugs, which they can fix), but the cyber-threat landscape has changed significantly. There are still bottlenecks to identifying and exploiting a vulnerability. AI agents still have to try a lot of things to see what works, and taking these actions takes time and might be detected by defenders. This is why, even though it is now easy to obtain versions of leading open weight models that have had their guardrails removed or weakened, so they will not refuse to try to execute cyber attacks, the world has not ended. I am also concerned about the anthropomorphization of AI in a lot of reporting, where LLMs and agents are unnecessarily treated as if they were people. If I wield a hammer, miss a nail, and accidentally dent the wall, it’s not the fault of the hammer. The problem lies in how I used the hammer. Similarly, if I prompt an agent and it hacks into someone else’s system, the responsibility lies with me, not the agent. Of course, we want to build systems that are as safe and predictable as possible. (For example, an unsafe hammer would be one whose head randomly flies off under normal use.) Today’s agentic systems are not predictable, but I see no reason why, by applying sound engineering practices, we won’t be able to make them extremely safe to use. One new element in the forecasts of AI-enabled doom is AI companies disclaiming responsibility for their own products. “I didn’t do it; my out-of-control agent did!” There’s a balance to be struck between the responsibility of the tool maker and the tool user, but when something goes wrong, let’s hold the people building and/or using the hammer responsible, rather than the hammer. (By the way, if you’re worried about AI bioweapon risk, David Bellamy has a great post on why this, too, is overhyped. Briefly, the bottleneck in building a bioweapon is not intelligence, but lab work and manufacturing.) Pausing AI progress will create much more harm than benefit. First, our adversaries will certainly not slow down. Second, engineering requires discovering problems empirically so we can fix them. If we pause AI by a decade, we will also delay finding and implementing safety engineering fixes by about the same duration. Of course, the incentive to stoke fears — for regulatory capture, to garner attention, or to make one’s technology seem more powerful — remains the same as before. Disclaiming responsibility is a new one. Taking a hard technical look at the actual risks however, I see little factual basis for the degree of fear that’s been stoked up. We still have hard research and engineering work ahead to improve AI safety, but the beneficial applications continue to vastly outweigh the risks, and we should keep building. [Original text (with links): deeplearning.ai/the-batch/is… ]
963
1,852
484
8,856
8,015,233
GPT-5.6 is genuinely impressive — faster, sharper, and way better at understanding what I actually mean. Coding, writing, brainstorming... it just gets it. Easily the most useful AI tool I've used. 🚀
44
AI didn’t make software engineering easier. It made code easier to produce — and systems easier to misunderstand. The real skill now is not just prompting better. It’s systems thinking: Where does state live? Where does feedback live? What breaks if this component disappears?
2
27
In the AI era, the strongest engineers won’t be the ones who ship the most generated code. They’ll be the ones who can understand the system, question the output, spot fragile architecture, and use AI as an accelerator — not as a replacement for judgment.
8
AI can generate a function, a page, an API, even a full feature. But it won’t automatically understand your product, your data flow, your failure modes, your business rules, or the hidden coupling inside your system. That is still the developer’s job.
22
AI is shifting from answers to actions. Agents won’t just assist, they’ll: buy resources, sell services, work with other agents A new market is already forming. Yes, rules are unclear. Yes, regulation is behind. But that’s how every new tech wave starts. We don’t wait until we’re ready. We adapt — fast.
1
33