与「common」相关的搜索结果

开发系统最极致高效的Agents.md，没有之一： # AGENTS.md ## Core Principles - Choose the simplest implementation that fully satisfies the current requirements. Avoid unnecessary abstraction, configuration, indirection, or speculative extensibility. - Make the smallest necessary change that fixes the root cause. Do not refactor unrelated modules or change strategy semantics unless explicitly requested. - Grow the system in layers. Start from the smallest working end-to-end version and add new capabilities incrementally. Never replace a working system with unfinished complexity. - Reuse existing project components before creating new ones. Prefer extending proven modules over introducing parallel implementations. - Prefer well-maintained libraries when they reduce overall complexity or improve reliability. Do not reimplement common functionality without a clear benefit. - Keep components modular with clearly defined responsibilities. Avoid unnecessary coupling between strategy logic, execution, accounting, replay, and infrastructure. - Design for long-term maintainability once a feature or strategy has been validated. Do not over-engineer speculative ideas before evidence exists. --- ## Strategy Development - Validate hypotheses with historical replay before introducing forward-only logic whenever historical validation is possible. - Every trading strategy must progress through Replay → Shadow → Canary → Live. Do not skip validation stages. - Base design decisions on measurable evidence rather than intuition. Optimize only after demonstrating that an edge exists. - Treat every strategy as an independent contract. Do not silently alter frozen behavior without explicit authorization. --- ## Existing Systems - Do not break running Shadow or Live systems for unrelated work. - Preserve compatibility only when required by active production or validation workflows. Otherwise, remove obsolete code instead of accumulating compatibility layers. - Reuse existing infrastructure whenever possible, including replay engines, accounting, execution, wallet management, order book handling, logging, monitoring, and daemon frameworks. --- ## Engineering Standards - Prefer deterministic behavior over hidden automation. - Fail loudly when assumptions are violated. Do not silently ignore errors or fall back to unexpected behavior. - Keep configuration minimal. Introduce new configuration only when behavior genuinely needs to vary. - Remove dead code instead of leaving unused paths behind. - Write code that is easy to inspect, replay, test, and reason about. - Keep implementation consistent with existing project architecture unless an architectural change is explicitly requested. --- ## Scope Discipline - Implement only the requested scope. - Do not introduce unrelated optimizations, redesigns, migrations, or feature expansions. - Non-blocking findings outside the requested scope may be noted separately but must not be merged into the current task. - Consider a task complete once its agreed acceptance criteria are satisfied. Treat subsequent improvements as separate work items.

Okay, the @VulcanBench results for Qwen3.8-Max are in, and it is not what I expected. First, for anyone new to VulcanBench, here's a quick TL;DR on the eval suite: 23 frontier-hard software engineering tasks taken from real merged OSS PRs, run in a Docker sandbox, 3 runs per task across all three of its effort levels. No puzzles, no random abstract stuff, all real things engineering teams would do with these models. It looks like Qwen3.8-Max has a major overthinking problem, it uses a LOT of tokens and is very slow, period, no other way to see it. My cost to run this benchmark was $126.25, to run the exact same eval suite with DeepSeek V4-Flash was only $13.60. This makes Qwen3.8-Max an insanely expensive model. The tasks Qwen genuinely can't solve fail at every effort level, extra reasoning didn't help. The regression is almost all in work it already handles: six tasks that low solves every single time account for 83% of the 26-point drop, three of them collapsing to zero. It's not losing the hard problems. It's losing the ones it already knows how to do. Since Qwen3.8-Max hit a lot of wall clock budget caps, I thought I'd share more about this. - VulcanBench caps both steps (50–200) and wall clock (5–60 min), each scaled by repo size. - This is aligned with how comparable harnesses bound agents, DeepSWE caps rollouts at 100 environment steps, sitting right inside my step range; Terminal-Bench enforces a per-task wall clock; SWE-bench Verified scaffolds typically allow 20–60 min per instance with 250–350 step limits. - Every model on my chart gets the identical budget, and Qwen is the slowest model I've tested at 20–25 min/task. Soooo... Alibaba positions Qwen3.8-Max as trailing only Claude Fable 5. But on the kind of real coding work engineering teams would actually throw at it, under a fixed budget, its best setting lands mid-pack and its default lands last, so common. If you want to optimize for accuracy, Grok 4.5 is the move. If you want accuracy per dollar, DeepSeek V4-Flash is hard to beat, heck it's 10× cheaper than Qwen and you get higher accuracy. Qwen just isn't in the game at this point, this is not a model I could see engineering teams using for daily coding work.

Grok Build keeps getting smarter.....this update expands Auto mode, gives developers more control over Bash permissions, speeds up /btw, and makes long conversations easier to navigate Release Notes: v0.2.119 Features: • Always allow for bash commands now lets you edit a free-form glob pattern instead of only word-prefix scopes. • Long responses now show a clickable arrow that jumps back to the start of the answer. • Auto mode now auto-approves more common read-only git commands and harmless file appends. • Plan previews now show Mermaid diagram buttons (Open Image, Copy Image Path, Copy Source). Bug Fixes: • Gateway connections now detect and recover from dead sockets more reliably. • Question cards now let you Tab through answers instead of losing focus to the scrollback. • Resume picker no longer tries to load a session from pasted garbage when you press Enter. • Background task completion messages no longer grow unbounded when the task produced a huge log. • Plan viewer scrollbar now responds to clicks on the border column and renders without dark stripes in • Expired external auth provider credentials now correctly trigger the interactive sign-in flow instead of a silent 401 loop. Performance: • /btw side questions now reuse the parent session’s cached prefix for faster responses. • Doctor and tmux-backed startup are now faster when no live tmux processes remain.

Akani Simbine is all about supporting younger athletes 🤝❤️ Having reached the 100m podium twice at the Commonwealth Games, the three-time Olympian and #Paris2024# 4x100m silver medallist explains how important it is for him that younger sprinters have opportunities to compete at the world's biggest stages as well. That's why, at #Glasgow2026# he's only focusing on the 4x100m relay. Are you ready to see him and his team shine today? #RoadToLA28# | @Glasgow_2026 | @WorldAthletics

🇮🇳 स्वर्णिम शुरुआत! भारत की शान मीराबाई चानू ने 2026 राष्ट्रमंडल खेलों में महिलाओं की 48 किग्रा वेटलिफ्टिंग स्पर्धा में स्वर्ण पदक जीतकर भारत का खाता खोला। लगातार तीसरे कॉमनवेल्थ गेम्स स्वर्ण के साथ उन्होंने इतिहास रच दिया। पूरे देश को आप पर गर्व है। हार्दिक बधाई! 💐🇮🇳 #MirabaiChanu# #CommonwealthGames2026# #IndiaWins#

LA28 in her sights. 👀🇱🇰 From non-travelling alternate for Team USA, to now competing for Sri Lanka at the Commonwealth Games, and aiming for Olympic qualification for her parent’s country of birth. #RoadToLA28# | #Glasgow2026# | @Glasgow_2026

As we head to the pool for more swimming medals at the Commonwealth Games, we can't help but think of this golden performance from #Paris2024#, when Mollie O’Callaghan clinched women's 200m freestyle gold. Who'll rise to the top at #Glasgow2026#? 👀 #Olympics# #RoadToLA28# | @Glasgow_2026 @AUSOlympicTeam