JetBrains

Koog: A JVM framework for building predictable, fault-tolerant and enterprise-ready AI agents (4.6k stars) What it does All text below is quoted directly from the project README. >Koog is a JVM (Java and Kotlin) framework for building predictable, fault-tolerant and enterprise-ready AI agents across all platforms, from backend services to Android and iOS, JVM, and even in-browser environments. Koog is based on our AI products expertise and provides proven solutions for complex LLM and AI problems Key features: - Multiplatform development: Deploy agents across JVM, JS, WasmJS, Android, and iOS targets using Kotlin Multiplatform. - Reliability and fault-tolerance: Handle failures with built-in retries and restore the agent state at specific points during execution with the agent persistence feature. - Intelligent history compression: Optimize token usage while maintaining context in long-running conversations using advanced built-in history compression techniques. - Enterprise-ready integrations: Utilize integration with popular JVM frameworks such as Spring Boot and Ktor to embed Koog into your applications. - LLM switching and seamless history adaptation: Switch to a different LLM at any point without losing the existing conversation history, or reroute between multiple LLM providers. - Model Context Protocol integration: Use Model Context Protocol (MCP) tools in AI agents. - Knowledge retrieval and memory: Retain and retrieve knowledge across conversations using vector embeddings and RAG. - Flexible graph workflows: Design complex agent behaviors using intuitive graph-based workflows. >implementation("ai.koog:koog-agents:1.3.0") Repository JetBrains/koog Repository stats |Metric|Value| |:-|:-| |Stars|4,645| |Forks|502| |Last release|1.3.0 (2026-09-24)| |Languages|Kotlin 97.3%, Java 2.6%, Other 0.1%| |Contributors|150| |AI contributor accounts (Claude / Codex / Cursor / Copilot)|@claude (6 commits), @Copilot (3 commits), @cursoragent (1 commits)| |AI co-authored commits|Claude: 6, Cursor: 1, Copilot: 3| Main contributor |Field|Value| |:-|:-| |Name|Anastasiia Zarechneva| |GitHub|@zarechneva-a| |Commits to this repo|177 (top contributor)| |Bio|QA engineer @ JetBrains| |Company / Location|JetBrains / Germany| |Followers|66| ────────────────────────────── 📌 If you want to browse more repos like this, we've organized them by category and rankings here: bestgithubrepositories.com 🗂️ We're also archiving repos where possible, so useful projects don't disappear when they're removed from GitHub.

Modern Go Guidelines: Help AI coding agents write modern Go (3.9k stars) What it does All text below is quoted directly from the project README. >This repository contains guidelines for code agents that help them write modern Go code. Modern Go Guidelines: - For example, an agent with these guidelines uses max(a, b) instead of an if-else block, slices.Contains instead of a manual loop, cmp.Or(a, b, c) instead of a chain of nil checks. - It also knows about recent additions like new(42) to get a pointer to a value and errors.AsType[T](err) for type-safe error matching, both from Go 1.26. - The guidelines cover the most useful features from Go 1.0 through Go 1.27, including everything targeted by the modernize analyzer. - Detect the project's Go version from go.mod - Use language features and stdlib additions available up to and including that version - Prefer modern idioms over older patterns >/plugin marketplace add JetBrains/go-modern-guidelines Repository jetbrains/go-modern-guidelines Repository stats |Metric|Value| |:-|:-| |Stars|3,910| |Forks|128| |Last release|None| |Languages|Go 82.6%, PowerShell 10%, Shell 6.3%| |Contributors|9| |AI contributor accounts (Claude / Codex / Cursor / Copilot)|None| |AI co-authored commits|None| Main contributor |Field|Value| |:-|:-| |Name|Nikita Kuchur| |GitHub|@nikitakuchur| |Commits to this repo|14 (top contributor)| |Company / Location|@JetBrains / Munich, Germany| |Followers|17| ────────────────────────────── 📌 If you want to browse more repos like this, we've organized them by category and rankings here: bestgithubrepositories.com 🗂️ We're also archiving repos where possible, so useful projects don't disappear when they're removed from GitHub.

Stop letting AI agents touch your checkout! JetBrains' thinkrail is open source. Your agents get separate worktrees. Source: JetBrains/thinkrail How many agents do you run at once? #AI #OpenSource

why do we even need the rebuilt? idea is already opensource[0]. In the benchmark[1] the cpu, memory and quit time (!) are compared, but does it makes any sense without feature parity? [0]: jetbrains/intellij-community [1]: l0ng-ai/openidea

(not the person you are replying to) I am primarily an Emacs user, using the standard key bindings (and a whole bunch of custom bindings and functions I've built on top of it over the decades, ctrl remaped to caps lock and no Emacs pinky so far). But I am also 80% a NeoVim and Vim user for about 15 years now, and I consider myself quite proficient with Vim keybindings. The Emacs emulation is truly incredible, but the fact that Vim implementation quality varies wildly from environment to environment is extremely frustrating to me. For example, the jupyterlab-vim plugin is so jarringly broken in a handful of ways that it completely knocks me out of the flow of whatever I was doing when I encounter those emulation failures. IntelliJ's idea Vim plugin is a pretty decent one, but even there I have encountered the occasional issue [1][2][3]. Otherwise, I strongly agree with your point about learning one way to work with text and being able to leverage it most places. Sort of a tangent, but I think this is why Emacs users tend to end up trying to do as much in Emacs as possible: It's not really the keybindings but the fact that everything in Emacs is a text buffer. Emacs owns the input and the output, and because everything in Emacs operates on text, you can do most everything in most every mode, to most any buffer content. One example of how powerful this can be is the ability to press a key and use dabbrev-expand to autocomplete shell input I'm typing based off the shell output of a prior command. 1: youtrack.jetbrains.com 2: youtrack.jetbrains.com 3: ideavim#33

ThinkRail: JetBrains' Open-Source Agentic IDE Every AI coding task gets its own track. ThinkRail is JetBrains' open-source agentic IDE, built around the pi coding agent. Per the README: • Each workspace is a real git worktree with its own branch and directory, so agents work in parallel without touching your checkout • Living specs: a connected graph of SPEC.md files beside the code that the agent reads and maintains • Reads the Agent Skills you already keep; bundled workflows can push a branch and open a GitHub PR via your own gh • Monaco editor tabs, terminals, diffs, MCP servers • Sign in with JetBrains AI or bring any provider through pi. ThinkRail has no accounts of its own. Install (macOS/Linux): curl -fsSL raw.githubusercontent.com | bash, then run thinkrail ~/code/my-repo. There are also desktop installers on the releases page. Security tip: read install scripts before piping them to bash; releases ship SHA256SUMS. JetBrains incubator project. Full extension support is "next" per the README. Latest stable: v0.2.0; nightlies are on v0.3.0. 5.2k GitHub stars · +1,068 today on GitHub Trending · Apache-2.0 Repo: JetBrains/thinkrail · Site: thinkrail.ai Link in caption. #AI #ThinkRail #JetBrains #AIAgents #OpenSource #GitHub #DevTools #CodingAgent #Shorts

I made ThinkRail (JetBrains' agentic IDE) run on the Claude Code CLI, so it uses your Pro/Max plan instead of extra usage I've been trying ThinkRail, JetBrains' open-source agentic IDE built around the pi coding agent. I like the UI: a workspace per git worktree, diffs, terminals and a proper chat view. The problem for me was billing. Using my Claude subscription through it counted as extra usage, not normal plan usage. So I forked it and added a Claude Code mode. You pick a "Claude Code" model (Opus, Sonnet or Haiku) in the model picker. Each chat turn then runs your local claude CLI headless (claude -p, stream-json) in the project folder and streams the output into ThinkRail's chat view. That turn is ordinary Claude Code usage on your plan. How it works - Each ThinkRail chat maps to one Claude Code session (--session-id / --resume), so the conversation continues across turns. - The effort slider maps to --effort. - ANTHROPIC_API_KEY is removed from the CLI's environment, so it always uses your subscription login. - The CLI uses your own Claude Code setup: claude.md, settings and MCP servers. - If you switch a chat to Claude Code partway through, the earlier messages are handed over once. Setup # needs the claude CLI on PATH, logged in with Pro/Max git clone samuele-apiudigital/thinkrail-cli-claude-code cd thinkrail-cli-claude-code bun install bun run dev # opens in the browser # or: bun run desktop:dev for the desktop app Then open a project, start a chat, and pick a model under claude-code. Limitations (it's early) - Tool calls show as text lines (▸ Bash ls), not ThinkRail's tool cards. - It runs with bypassPermissions, so there are no approval prompts. Use it on repos you trust. - ThinkRail's own tools (TODO plan, subagents, ask-user questions, visualize) don't work in these turns. Claude Code does the work instead. - A new claude process starts each turn, which adds a second or two. - I've only run it on macOS. Windows only finds the native claude.exe. I also added a Dracula theme, because of course. Feedback and PRs welcome. Tool-card support is the obvious next step if people find this useful. Repo: samuele-apiudigital/thinkrail-cli-claude-code

The VSCode and Cursor extensions for JetBrains IntelliJ IDEA-LSP server is quite interesting: blog.jetbrains.com But, you know as an aVId user, I have my eyes on the Neovim extension: JetBrains/intellij-lsp.nvim

The VSCode and Cursor extensions for JetBrains IntelliJ IDEA-LSP server is quite interesting: blog.jetbrains.com But, you know as an aVId user, I have my eyes on the Neovim extension: JetBrains/intellij-lsp.nvim

ThinkRail: the agentic IDE that gets better every time you use it (2.7k stars) What it does All text below is quoted directly from the project README. >Vibe code with pi in a lightweight, real IDE that customises itself around the way you work: The Vibe You Need What you get: - Isolated workspaces. Open any git repo as a project and cut workspaces from it as git worktrees, each with its own branch and working directory. - A real IDE around the agent. A splittable workbench of Monaco editor tabs, a Files tree with live git change marks and a Changed view, terminals, and documents, all scoped to the active workspace. - Chats that stream like the engine thinks. Several concurrent pi sessions per workspace, each with its own model and live token and cost readout. - Specs as ground truth. A connected graph of SPEC.md files lives beside the code; the agent reads, searches, and maintains it through dedicated spec_* tools, so intent survives the session. - Skills and workflows. Portable Agent Skills you already keep for other coding agents are read in place. - Your providers, your credentials. Sign in with JetBrains AI or connect any provider through pi's own auth. ThinkRail has no accounts of its own. Repository jetbrains/thinkrail Repository stats |Metric|Value| |:-|:-| |Stars|2,694| |Forks|145| |Last release|v0.2.0 (2026-10-18)| |Languages|TypeScript 98%, CSS 1.1%, Astro 0.5%| |Contributors|27| |AI contributor accounts (Claude / Codex / Cursor / Copilot)|@claude (30 commits), @Copilot (1 commits)| |AI co-authored commits|Copilot: 1| Main contributor |Field|Value| |:-|:-| |Name|Rinat S| |GitHub|@rsolmano| |Commits to this repo|296 (top contributor)| |Company / Location|Valencia, Spain| |Followers|9| ────────────────────────────── 📌 How many great GitHub repos have you discovered and completely forgotten about? Don't let another useful tool disappear into your Reddit feed. Get the community's best repos, organized by category, plus key takeaways from real developer discussions, delivered to your inbox twice a week. 📬 Never lose track of great repos again. Subscribe free.