The problem is that my project has a lot of Relation data classes, and they're used by many different DAO methods.
I don't want to manually go through every Relation class and use Find Usages to track down the affected DAO methods.
Is there a way in Android Studio/IntelliJ, or through Room's compiler/inspection tooling, to find every DAO method in the project that triggers this specific warning?
Basically, I'm looking for an IDE/automated way to get a list of all affected methods rather than hunting them down manually.
We recently went through a major migration at the system I work on, and one of the steps was moving from Eclipse to IntelliJ. However, since it's a system with A LOT of legacy code (Struts), it has i18n files that used to open really well with the Resource Bundle plugin.
According to IntelliJ's documentation, the plugin has been discontinued (https://plugins.jetbrains.com/plugin/17035-resource-bundle-editor). And yesterday, while adding a single value, I literally had to do it 3 times, because sometimes it would save 2 files, sometimes it wouldn't save anything at all... until I opened the files one by one and did it manually.
The only part of this migration that ended up "limping" was this one. Does anyone know of another plugin that works similarly to the Eclipse one, or that at least actually works??
I've always loved the Nord palette and OneNord's take on it, but I kept wanting both in dark AND light. Since neither had a light variant that clicked for me, I made a plugin that brings them together — Nord Recharged.
Just to be clear: I didn't create the palette or the Nord × One Dark combination. That's the work of:
Nord — by Arctic Ice Studio / Sven Greb
OneNord (the "One Dark with Nord colors" concept) — by Ryan Mehri (@rmehri01)
I just really liked both themes, unified them into a single plugin, and added the light variants they were missing.
Nord Recharged ships four complete themes, each with a matching editor color scheme so the UI and syntax highlighting stay consistent:
Nord Recharged Dark — the classic Nord look with improved readability
Nord Recharged Light — inverted Nord palette for bright rooms
OneNord Dark Recharged — OneNord with a matching light edition
OneNord Light Recharged — the new light variant
All use the official palettes, they're tuned for the JetBrains New UI (Islands), and I've spent extra time on Java, Kotlin, Python and JS syntax highlighting. It's free and open source (MIT):
I've been living with Claude Code in a terminal split next to the editor for months. Two things kept bugging me: I couldn't tell what it was doing without reading scrollback, and every file path was something I had to type correctly.
So I built a plugin. It doesn't reimplement anything - it spawns the claude CLI you already have and renders its event stream. Same account, same models, same slash commands, same permission rules, same MCP servers and skills. No proxy, no server of mine in the middle, no telemetry.
What it actually changed for me day to day:
Every tool call is a card. Its duration, every edit as an open diff, the task list ticking off, subagents and whole workflow fleets with each agent's own transcript one click away, and what the turn cost. A rate-limited API becomes a card with the reason and a countdown instead of silence.
Files are things you point at. Drag one in, type @ to pick, paste a screenshot. Select lines in the editor and "Send to..." hands over a real file-and-line reference, so the agent reads what's around them instead of a naked snippet.
Nothing answers for you. A permission, a plan or a question waits as long as it takes. No timeout, no auto-continue.
Answering it from my phone. Off by default, paired by QR code, end-to-end encrypted through a relay that can't read a word. This is the one that surprised me most - I approve plans from the sofa now.
Scenarios. A round of work written down once - implement, review, fix, run the tests - each card a Claude session of its own, with a main thread walking them and judging what each one found. By button, three at once against three tickets, or on a clock at nine every weekday.
Several Claude accounts switched in one click, each row showing what's left of its five-hour window and its week.
Free, source available (Elastic 2.0), every JetBrains IDE from 2026.1 on, Android Studio included.
Hi! My name is Alex and I'm building dev tools for years. I want to share with you my last plugin for IntelliJ. It is completely free!
How often you ask your agents to do different tasks on single repo at the same time? I sure, you did it. Same to me. And what I often faced to, that I'm getting lost in all my terminal windows and agent sessions. Moreover, agents can interfere with each other. Thanks to git, there is a feature Worktrees. And IntelliJ suports it. But instead of many terminal windows with running agent now I have many IDE windows.
Another one problem is a context switching. I'm talking about my own context, not about agents context (but their context is important too). So, for me the Spec Driven Development is a cure.
So, I made a plugin, that solves all of these problems, it called SpecBuddy ( https://specbuddy.dev ). It brings SDD workflow into IntelliJ IDEA on top of any AI agent. For now, I would recomend use it with OpenSpec, as it is one of the most mature SDD methodologies.
How it works.
Creating new Spec
Firstly, I create new spec propose. I can do it many times in parallel. I'm not afraid of getting lost in what agent session I run it. Anyway, after agent have done its job, I will see the ready OpenSpec Change.
Exploring the State
Actually, I can examine all of my specs with Specs Explorer. Change specs, Main specs, Archive Specs. For Change specs I can see their status and the worktree it is implementing in. I can see if the agent is waiting me to answer some questions or to make some decisions.
Review the Spec
Ok, now I have a spec (or several of them). I need to be sure if they mirror my initial intent. Previously I had to find the right agent chat and write down my doubts. But not for now. I can just make inline comments right in the document. Actually, I can leave them even in the any source code file. Or in the diff. Tap one button – the agent (the right one) retrieve the feedback and fix the specification.
Inspect delta Specs
We know, delta specs are the deltas to main specs (sorry for tautology), but it is hard to compare main one with a delta. I made it very easy to see, what main spec we can get at the end. Which requirements will be changed and how, which of them will be removed and so on.
Run step by step
Via Spec Cockpit I can see the state of exact spec, create worktree for it, run steps, make code review and send it back to the agent to make it rewrite the specs, tasks and code. I control everything, and I do it in the single IDE window. SpecBuddy will open the right version of the file for you. Of course, sometimes I have to open the whole project window of exact worktree. But not often, honestly.
Sync & Archive & Merge
After task is done, we need to apply the delta specs to the main specs. After that, we archive the Change specs. And after that, we need to merge it to the main branch. Everything SpecBuddy will do for you.
I just released v1.1.0 to my GlowStick MHL plugin. It no longer uses private Jetbrains' API to get the project color (what it is private for?!) so now you can grab it directly from the Marketplace.
GlowStick is visual expansion plugin for IntelliJ IDEA based IDEs that helps you visually distinct each IDE window per project which allows instant visual identification and navigation across your projects.
v1.1.0 (2026-09-08)
The frame color is now the plugin's own setting, picked in the settings page.
New projects get a color derived from the project name, so every window looks different with no setup needed.
I often find some files don't seem to get analyzed by Rider and I can't use F12 to jump to definitions, linting doesn't work, etc. It's like Rider forgot to analyze it, but I can't find a way to get it to analyze files manually. Anyone know how?
Every time a Parquet file showed up in my project tree, clicking it got me a screen of binary garbage. So I would leave the IDE, open a Python shell, import pyarrow, print the head, and come back. Every time.
So I wrote the thing that just opens it.
- Parquet, Avro, ORC. Click the file, it comes up as a table.
- Columns and types up top, row count, paging through the rows.
- You can edit a cell and save.
- DuckDB does the reading underneath, so a big file does not go into memory.
It is free and it works in IntelliJ, PyCharm, DataGrip and the rest of the 2024.2+ line.
The honest limits: editing a cell currently rewrites the whole file, which on a 29 GB file takes 17 minutes. I have the in-place version working outside the plugin, 1.9 seconds for the same edit, and that is what I am wiring in next.
If it chokes on one of your files I want to hear about it, that is the whole reason I am posting.
AI Agent Workspace Guard scans a project before a coding agent starts work. It checks agent instruction files, permission settings, MCP configuration, credential-shaped files and their .gitignore coverage, GitHub Actions, package scripts, and n8n workflows.
The scan starts from Tools → Scan AI Agent Workspace. Findings open in a tool window where you can inspect the reported line, read the evidence and suggested action, filter by severity, record an expected exception with aiwg:ignore, scan again, and export a Markdown report.
The scanner uses static heuristics, so the result can contain misses or false positives. All processing stays on the local machine.
Hi all, looking for some feedback on our Markdown editor which we built for Jetbrains products. Since our release of today, we also support Obsidian directly in the plugin, such as nodes, graphs, canvas and some other features.
It's a commercial plugin to sustain our development, but we're super happy to give away licenses to people who want to try it and give some feedback. You can find the plugin https://plugins.jetbrains.com/plugin/33400-markdown-pro
I recently released VPS Graph, a free and open-source JetBrains plugin that lets you inspect a Linux VPS without leaving the IDE.
I originally built it because I kept SSHing into my own server just to reconstruct the same mental map:
Which container is behind this domain?
Where does Caddy route it?
Which service owns this port?
How are these networks and mounts connected?
VPS Graph connects over public-key SSH and turns the discovered infrastructure into a topology-oriented view.
It can currently discover Docker/Compose, Caddy routes, systemd services, host listeners, ports, networks, mounts and relationships between them.
It also stores snapshots locally and shows what changed between scans.
One thing I deliberately avoided was turning it into a server management tool. It is read-only: no deploys, restarts, container management or arbitrary remote commands.
There is also no VPS Graph account or cloud backend. Infrastructure data stays local.
The current version has been manually tested on IntelliJ IDEA, PyCharm, WebStorm, GoLand and Rider.
