Ruff v0.16 enables 413 rules by default
Ruff v0.16 expands default rule set from 59 to 413 rules, replacing need for separate linters like Black, Flake8, and isort while running 10-100x faster.
Developers get stricter linting out-of-the-box without configuration, catching syntax errors and runtime issues automatically. Markdown code block formatting and improved suppression comments reduce boilerplate in mixed-content projects.
Replaces Black, Flake8 (plus plugins), isort, pydocstyle, pyupgrade—install from PyPI and update config for breaking changes (revert with `select = ["E4", "E7", "E9", "F"]` if needed). Ready now; most users update without code changes. Markdown formatting stabilized; ruff: ignore comments add expressiveness over noqa.
- “Ruff now enables 413 rules by default, up from 59 in previous versions”
- “all while executing tens or hundreds of times faster than any individual tool”
- “can be used to replace Black, Flake8 (plus dozens of plugins), isort, pydocstyle, pyupgrade, and more”
- “Ruff can now format Python code blocks embedded in Markdown files”
- “Ruff v0.16 builds on this to add two additional ruff suppression comments”
ruffpython-lintingtoolingreleaseformatter
Ruff v0.16.0 enables 413 rules by default
Ruff jumped from 59 to 413 default rules, catching syntax errors and runtime issues previously opt-in—unpinned dependencies will break CI until you fix violations or pin the version.
Blanket rule enablement forces immediate remediation across projects; comprehensive test coverage makes upgrades safe but requires active fix or version pinning to prevent CI failures. Caught hundreds of minor issues in production codebases.
Replaces implicit linting configuration discipline with stricter defaults. Requires either pinning ruff version, running `ruff check . --fix --unsafe-fixes` to auto-remediate, or configuring ignored rules in pyproject.toml. Worth upgrading now if your project has strong test coverage; expect 100–1600+ violations depending on codebase size.
- “Ruff now enables 413 rules by default, up from 59 in previous versions”
- “the number of rules in Ruff has grown from 708 to 968”
- “uvx ruff@latest check . --fix --unsafe-fixes”
- “Found 1618 errors (1538 fixed, 80 remaining)”
python-toolinglintingci-cdbreaking-changeruff
Claude models eliminate rigid prompt guardrails
Newer Claude models handle context well enough to replace exhaustive rules with tool-design principles, progressive disclosure, and judgment-based directives.
You can reduce system prompt bloat and context waste by shifting from prescriptive rules to interface design; Claude now auto-saves relevant memories and handles dynamic tool references without preloading everything upfront.
Replaces: over-specified system prompts with hardcoded constraints. Requires: restructuring CLAUDE.md around gotchas only, breaking skills into progressive-disclosure trees, using code/HTML as specs instead of markdown descriptions. Worth trying now if you're on Claude 3.5+; use `claude doctor` command to audit existing prompts.
- “newer models have better judgement and can handle these decisions well without explicit rules”
- “giving examples actually constrains them to a certain exploration space”
- “Claude now automatically saves memories that are relevant to the work and to you”
- “Claude can reference HTML artifacts created by our new artifacts feature”
- “keeping one item in_progress helps define our requested behavior”
prompt-engineeringcontext-designclaude-apiagentic-systemsbest-practices
Grabette: handheld gripper records robot manipulation data
Open-source handheld gripper (~€490 BOM) + browser-based SLAM processing pipeline converts human demonstrations into LeRobot datasets without needing a robot.
Removes hardware gatekeeping from robot learning data collection—developers can now record training data from any environment and contribute to shared datasets, addressing the actual bottleneck in visuomotor policy training.
Replaces expensive teleoperation rigs and lab-bound data collection. Requires building Grabette from off-shelf components (Raspberry Pi, OAK-D camera, magnetic encoders), uploading recordings to Hugging Face, and running SLAM processing via browser. Production-ready for early adopters; community contribution model is the real test.
- “The bottleneck isn't the model. It's the data.”
- “Grabette is a handheld gripper instrumented with everything needed to reconstruct a manipulation demonstration.”
- “BOM cost ~490€”
- “Everything is open source”
- “The output is a standard LeRobot dataset on the Hugging Face Hub, so the same data can drive different robots and different learning methods.”
robot-learningdata-collectionopen-sourcevisuomotor-policyhardware
Google deprecates Gemini CLI for Antigravity
Gemini CLI shuts down June 18, 2026; multi-agent workloads move to Antigravity CLI (Go-based, async agent orchestration) with unified backend shared across desktop and terminal.
Terminal-first developers lose weekly release cadence and must migrate Agent Skills, Hooks, Subagents to new platform. The unified harness means desktop and CLI agents sync automatically—critical if you're splitting work across multiple agents—but feature parity gaps exist at launch.
Antigravity CLI replaces Gemini CLI entirely; requires migration of Skills and plugins before June 18 deadline. Go implementation promises faster execution and async workflows (no terminal lock on large refactors), but deprecation timeline is tight and early feature gaps are acknowledged. Worth piloting now if you're already on multi-agent patterns; risky if you depend on Gemini CLI's full feature set.
- “over 100,000 GitHub stars, 6,000 merged pull requests”
- “On June 18, 2026, Gemini CLI and Gemini Code Assist IDE extensions will stop serving requests”
- “Agent Skills, Hooks, Subagents, and Extensions (now as Antigravity plugins)”
- “Antigravity CLI orchestrates multiple agents for complex tasks in the background”
- “Antigravity CLI shares the same agent harness as Antigravity 2.0”
cli-deprecationagent-orchestrationmigration-requiredmulti-agent-patternsgolang