Scraper
Spider

A robotic spider About
Blog
@dbaman@fosstodon.org
Click ▶ to show/hide AI summary and keywords
Click The google logo for Google search on keywords

2026-02-18 17:29
jetbrains
jetbrains stories from the last 14 days  | Back to all stories
1223.  HN Show HN: Agnix – lint your AI agent configs (Claude.md, skills, MCP, hooks)
Agnix is a comprehensive linter specifically tailored for AI agent configurations, supporting tools like Claude Code, Cursor, GitHub Copilot, and Codex CLI. Its primary function is to prevent configuration errors that could disrupt user workflows by offering 156 validation rules. These rules are based on official specifications, research, and extensive testing, along with features enabling automatic fixes. Agnix can validate a range of components including skills, hooks, memory, plugins, MCP, and agent configurations. Key features of Agnix include support for multiple development environments through its CLI, LSP server, and IDE plugins, ensuring compatibility with popular editors such as VS Code, JetBrains, Neovim, and Zed. Additionally, it offers GitHub Actions to automate validation processes, streamlining workflow integration. Users have various installation options including npm, Homebrew, or Cargo, and can further enhance their experience with available editor extensions. The primary motivation for using Agnix is its ability to mitigate configuration errors that may prevent AI skills from being triggered—a common source of frustration among users. By ensuring configurations remain consistent across different tools, Agnix prevents the learning of flawed patterns by AI assistants. The tool simplifies validation processes with commands like `agnix .` for general checks, `agnix --fix .` to apply automatic fixes, `agnix --fix-safe .` for only safe adjustments, and `agnix --strict .` for strict mode operations. Users can also specify validations for particular tools using the command `agnix --target claude-code .`. Agnix encourages community contributions, with detailed guidance available in its CONTRIBUTING.md file. The project is open-source, licensed under either MIT or Apache-2.0, allowing users to engage and improve upon it. Those interested can support the project by starring its repository, which aids in increasing its visibility and discovery. Keywords: #phi4, AI agent configs, Agnix, Apache-20 License, CLI, GitHub Action, IDE plugins, JetBrains, LSP server, MCP, Neovim, VS Code, Zed, auto-fix, editor extensions, hooks, linting, memory, multi-tool stacks, real-world testing, skills, syntax errors, validation rules
    The google logo   github.com 6 days ago
   https://dev.to/avifenesh/your-ai-agent-configs-are-prob   6 days ago
2204.  HN RMA – Compile Semgrep rules to native Rust/Tree-sitter matchers
RMA (Rust Monorepo Analyzer) is a high-performance, security-focused static analysis tool designed for rapid and accurate code vulnerability detection. Built using compiled Rust and Tree-sitter matchers, RMA is up to 10 times faster than Semgrep, offering efficient scanning with minimal overhead. It identifies a wide range of security issues, including injection attacks, server-side vulnerabilities, hardcoded secrets, weak cryptographic practices, and SSRF (Server-Side Request Forgery) vulnerabilities. RMA supports multiple programming languages and frameworks, and provides a range of features such as an interactive TUI for exploring vulnerabilities, real-time dependency CVE scanning via OSV.dev, and integration with GitHub Actions for CI/CD pipelines. The RMA Dashboard enhances team collaboration by offering historical trend analysis, AI-driven explanations, and auto-fix suggestions. Advanced capabilities include cross-file taint tracking, path-sensitive analysis, and symbolic execution for deeper security insights. RMA is lightweight, integrates with various package managers and IDEs, and includes a REST API for custom workflows. It supports custom WASM plugins, rule configuration, and suppression options. Additionally, RMA is open source, available under the MIT or Apache-2.0 license, and can be quickly installed via npm, Docker, or Cargo. Its performance benchmarks highlight its efficiency, making it a robust alternative to existing security scanning tools. Keywords: #qwen3:14b, AI-powered explanations, API keys, AST, CLI, CVE, Cargo, GitHub Actions, Go, IDE, Java, JavaScript, JetBrains, Maven, Neovim, OSVdev, PR integration, PyPI, Python, RBAC, RMA, RMA Dashboard, Rust, SARIF, SQL injection, SSRF, Semgrep, TUI, Tree-sitter, VS Code, WASM, XSS, audit logs, auto-fix suggestions, baseline diffs, benchmark, call graphs, crypto, cryptographic, dependency CVEs, dependency scanning, deserialization, exec, forward taint propagation, hardcoded secrets, historical trends, injection, keyboard shortcuts, metrics, npm, parsing, path traversal, path-sensitive analysis, performance, plugin, real-time CVE detection, sanitizer recognition, scan, secrets, security, symbolic path conditions, taint flows, taint tracking, team collaboration, unsafe, vulnerabilities
    The google logo   github.com 13 days ago
2440.  HN Wayland by Default in 2026.1 EAP (Jetbrains)
JetBrains has introduced native Wayland support in IntelliJ‑based IDEs through the 2026.1 early access program, automatically enabling Wayland on compatible Linux desktops and enhancing stability across multiple Wayland servers while adding drag‑and‑drop, input‑method support and aligning window decorations with desktop themes; however, users may notice altered dialog placement or incomplete theming due to Wayland’s limited application control over window positioning, and the early‑access phase is aimed at collecting Linux user feedback before a full release. X11 remains supported, with an XWayland fallback accessible via the –Dawt.toolkit.name=XToolkit option, and the new –Dawt.toolkit.name=auto switch dynamically selects the WLToolkit for Wayland or defaults to XToolkit when Wayland is unavailable—its status can be verified through the Help → About menu or by inspecting sun.awt.wl.WLToolkit entries in idea.log. Remote Development continues to operate as before, with native Wayland integration still under development. The WLToolkit subsystem is maintained both internally and by the open‑source community on GitHub, contributing to the OpenJDK Wayland project, and version 2026.1 addresses numerous stability, performance, and desktop‑integration issues while ongoing work focuses on rendering, pop‑up behavior, window management, and input‑method handling, with community input and issue voting actively encouraged. Keywords: #gpt-oss:20b-cloud, Decorations, Desktop, IDE, IntelliJ, Jetbrains, Linux, Remote Development, Toolkit, VM options, Wayland, Window, X11, XWayland
    The google logo   blog.jetbrains.com 14 days ago