🚀 Vibe Stack açık kaynak!
Docker ile tek komutta:
✅ AI Coding (Claude Code)
✅ Browser-based VS Code
✅ Vibe-Kanban orchestration
✅ Güvenli secrets yönetimi
AI destekli geliştirme ortamını dakikalar içinde kur 🤖
⭐ https://t.co/naNbiZ7yK2
#OpenSource#AI#Docker#DevTools #Coding #Claude #VSCode #AIEngineering #BuildInPublic @claudeai@vibekanban@Zai_org@Docker
Notlarımı markdown tutuyorum çünkü yapay zeka zaten düz metinle çalışıyor.
Aynı dosyayı ben Obsidian'da düzeltiyorum, Claude Code okuyup cevap veriyor.
Hi everyone, this time, I compared the outputs and performance of some of the most widely used AI Harness tools. I evaluated Pi, OMP, Droid, and Codex CLI using the same development prompt in the GLASS CATHEDRAL — Fracture Dynamics Benchmark scenario. 🔥
I used GPT-6 Luna with high effort across all tools. Instead of moving directly into development, I followed a planning-first, development-second workflow. For Pi, I explicitly instructed it to prepare a plan first, then proceeded with the development command.
Task Summary;
I tasked the tools with developing an application that simulates three Gothic stained-glass windows, incorporating 150–200 independent triangular glass fragments, XPBD-based breakable constraints, physical collisions, wind effects, and structural support loss. The application had to run in a single HTML file, complete a 75-second autonomous scenario, and generate a measurement-based results report.
Note: I used GPT-6 Astra Pro as the Judge LLM for the evaluation.
AI Harness Delivery Performance Scores /10
1st — Droid: 9.33/10 @droid
2nd — Pi: 6.43/10 @pidotdev
3rd — Codex CLI: 5.86/10 @OpenAIDevs
4th — OMP: 3.10/10 @stencil_labs
Cost and Speed
- Droid — $0.17 — 15 minutes
- Pi — $0.15 — 42 minutes
- Codex CLI — $0.34 — 24 minutes
- OMP — $0.83 — 1 hour 17 minutes
Results;
👉Best speed-to-cost balance and fastest completion — Droid. Despite costing just $0.02 more than the cheapest option, it completed the task in the shortest time. Its delivered code also included phase-based time series, event logs, and fracture causes in the report, which was a positive feature in terms of auditability.
👉 Lowest direct cost — Pi. However, its $0.15 cost advantage came with a completion time of 42 minutes. Therefore, in this run, the cheapest option did not provide the strongest overall efficiency.
👉 Second-fastest completion — Codex CLI. It completed the task in 24 minutes. However, it took 9 minutes longer than Droid and cost twice as much.
👉 Longest completion time and highest cost — OMP. At 77 minutes and $0.83, it ranked last in the economic dimension of this evaluation. This result does not mean that OMP's overall capabilities are insufficient, but rather that its time and cost in this task were not justified by the metrics I selected.
One difference was particularly noteworthy: Droid completed the task 27 minutes faster than Pi for just $0.02 more.Compared with Codex CLI, it delivered the task in 37.5% less time and at 50% lower cost.
In this benchmark, Droid clearly stood out by combining speed with low cost. Pi was the most economical option, while Codex CLI ranked second in completion time. OMP, despite taking longer and costing more in this run, ranked last in the delivery performance scores.
Hi Friends! This time, instead of comparing different AI models, I compared the delivery performance of different AI Harness tools running the same model. We evaluated Pi, OpenCode, Claude Code, and Cursor using the same development prompt in the Port Crane Chess scenario. All tools used Sonnet 5.5 via OpenRouter, configured with medium effort.
Task Overview:
We asked the tools to develop a port simulation featuring autonomous crane control, physics-based cargo handling, dynamic task allocation, collision avoidance, and automatic task reassignment when a crane becomes unavailable. The evaluation focused on how quickly and cost-effectively each harness completed the development task, how easily the resulting software could be tested and inspected, and how effectively it reported its results.
AI Harness Delivery Performance Scores /10 — Cost & Completion Time:
🥇 Pi — 8.46/10 — $2.634 — 17 minutes
🥈 Claude Code — 8.16/10 — $4.390 — 13 minutes
🥉 OpenCode — 7.68/10 — $2.370 — 25 minutes
🏅 Cursor — 7.24/10 — $3.780 — 19 minutes
Key Findings:
— Best balance between speed and cost — Pi. Ranking second in both metrics, Pi achieved the highest overall score.
— Fastest completion — Claude Code. It completed the task in just 13 minutes, but also had the highest execution cost.
— Lowest cost — OpenCode. However, it also recorded the longest completion time at 25 minutes.
— Explicit testing and state inspection interfaces — Claude Code and Cursor. Both delivered implementations with named access points for externally stepping through execution and inspecting the current simulation state.
— Restart behavior issue — OpenCode. Its implementation failed to clear the previous benchmark results after restarting.
The cost–time trade-off was particularly interesting:
— Pi completed the task 8 minutes faster than OpenCode for just $0.264 more. Compared with Cursor, Pi was 2 minutes faster and $1.146 cheaper.
— These results demonstrate that the lowest execution cost does not necessarily translate into the highest overall efficiency. More importantly, this benchmark highlights a key observation: Using the same model, the same development prompt, and the same effort configuration does not guarantee identical completion times, execution costs, or output characteristics.
— In this particular run, Pi delivered the most balanced performance, Claude Code was the fastest, and OpenCode was the most cost-efficient in absolute spending. Although Cursor's explicit testing interfaces were a positive aspect, it still fell behind Pi in both completion time and cost.
Ultimately, the harness itself matters. Even when the underlying model remains identical, orchestration, execution workflows, and delivery behavior can significantly influence the final outcome.
Ajan = model + harness.
Model motor; tek başına bir yere gitmiyor. Araçlar, hafıza, izinler ve iş sırası onu arabaya çeviriyor.
Bugün Claude, yarın GPT. Model değişir, sistem kalır.
Hey @elonmusk, 0–60 in under a second is cool and easy.
But have you ever tried a curb? 🦽
So I built my own Roadster 😂
Consider this a challenge. Build it. I’ll wait. 😏
SpaceXAI’da Baş Mühendis olarak görev yapan Yağız Nizipli, X’i 5 kişilik ekiple baştan yazmaları ve Elon Musk’ın şirketlerindeki çalışma kültürü hakkında konuştu.
“Eskiden yaklaşık 150 kişinin geliştirdiği siteyi şu anda beş kişi yapıyoruz hatta 2 ay öncesine kadar 2 kişiydik.”
OpenChamber 2.0 is out, on OpenCode v2.
Skills, agents, MCP servers and plugins now apply the moment you save them. No restarts. My restart button is unemployed.
Plus Code Mode, web search cards and a stats page.
https://t.co/GHw0LzmLjS
Yapay zeka gelişmelerinden önce, hayatı izleyen, merak etmeyen ve bir şeyler yapma çabası olmayanlara yapay zeka araçları bir fayda sağlamadı.
Diğer yandan, YZ gelişmelerinden önce imkan ölçüsünde bir şeyler yapmaya çalışan, bahane sevmeyen kitle ise eskiye nazaran çok daha üretken ve belki altın dönemini yaşıyor.
Yani olay kafa yapısında bitiyor yine. Yakınan tiplere istediği imkanı ver yine yakınacak ve bir eylemde bulnmayacak, mücadeleci kitle ise imkanları geliştiğinde bunu kaldıraç olarak kullanmaya devam ediyor.
Yıllardır bilinen ve bahsedilen şeyin sağlaması oldu bu gelişmeler.
Claude Fable 5 will be available again globally tomorrow.
After a series of productive conversations with the US government, we're redeploying the model with a new set of classifiers to target and block more cybersecurity tasks. In the near term, some routine tasks like coding and debugging will fall back to Opus 4.8. We’ll continue to refine these classifiers over the coming weeks to reduce false positives and better distinguish genuine misuse from legitimate requests.
We’ve also begun drafting a consensus framework—with Amazon, Microsoft, Google, and other Glasswing partners—for assessing the severity of AI jailbreaks and how AI developers should respond to them. We invite other industry partners and model providers to join us in this effort.
Finally, we’re scaling up our collaboration with the US government on model testing and safeguards. This will include pre-release access to models and safeguards for evaluation, information sharing on jailbreaks and misuse, and dedicated resources for joint research.
Thank you to our users for your patience, and to our partners across the government, industry, and the research community who worked alongside us to make Fable 5 available again.
Read our full blog: https://t.co/VHyum831ri