u/barad1tos

https://www.last.fm/user/barad1toz

Hello, community!

I use JetBrains IDEs daily, but occasionally still need AppleScript for macOS automation.

The existing AppleScript plugin had seen very little maintenance in recent years, so I started modernizing it and eventually released AppleScript Toolkit.

The project is based on the original Apache-licensed plugin, but the codebase has been migrated to Kotlin, updated for current IntelliJ Platform releases, and is now actively maintained.

Current features include:

• Syntax highlighting
• Structure View
• Navigation and Find Usages
• Quick Documentation
• Dictionary-aware completion
• Context-aware completion inside tell application blocks
• Application dictionary indexing on macOS
• Run Configurations
• Script execution inside the IDE
• Gutter navigation markers

One area I’m particularly interested in is bringing more of the AppleScript development experience into JetBrains IDEs. Long-term, I’d like to move toward some of the workflow capabilities people know from Script Debugger while staying within the IntelliJ platform ecosystem.

If you’re still using AppleScript, I’d be interested in hearing which features or workflows you feel are missing from existing tooling.

JetBrains Marketplace | GitHub

Active development, looking for feedback before the first stable release.

noxctl is a macOS CLI for declaratively managing Bear Notes structure.

The basic idea:

>It is meant for Bear users who like Bear as the writing app, but want a more structured / Obsidian-like workflow around master notes, hub notes, generated indexes, grouped lists, and backlinks. It manages your notes, moc/hub structures automatically, based on which structure you set in config; notes are auto-appended / auto-sorted by alphabet / auto-formatted to the basic style.

Example of what is formatting looks like:

Before

After

Repo: https://github.com/barad1tos/noxctl

Terraform for Bear notes — declarative macOS CLI for vault structure management.

Example:

[meta]
version = "1"
locale = "en"

[[domain]]
tag = "library/books"
index_title = "✱ Books"
blueprint = "flat-list"

Workflow:

noxctl validate ~/.config/noxctl/noxctl.toml
noxctl doctor --config ~/.config/noxctl/noxctl.toml
noxctl plan --config ~/.config/noxctl/noxctl.toml
noxctl apply --config ~/.config/noxctl/noxctl.toml

What it does:

• scans managed Bear tags;
• generates master / hub notes;
• stamps a canonical tag-line onto managed notes;
• keeps generated structure idempotent;
• can run once or as a daemon with a LaunchAgent (launchctl with Go binary).

Important caveats:

• pre-1.0;
• macOS only;
• Bear only;
• terminal-oriented;
• not affiliated with Bear / Shiny Frog;
• not a backup tool;
• apply mutates your local Bear database through Bear’s bundled bearcli.

So: back up Bear first, start with one small low-risk tag, inspect plan, then apply.

I’m mainly looking for feedback on the README and the user-facing model:

• Is the project understandable from the first page?
• Are the safety warnings clear enough?
• Does plan → apply make sense for a note app?
• Is this useful, or too much machinery for Bear?

Any feedback from Bear power users would be very useful. The project is in pre-alpha stage and mostly scratches my own itches, but if it engages with the community, it could be developed into something interesting. I have more ideas.

If you keep three IDE's windows open across two monitors and regularly stare at the wrong one for ten seconds before realizing it's the test sandbox, not the backend repo — this release is for you.

VS Code users have had Peacock by John Papa for years. Pin a color to a workspace, the chrome tints to match, instant visual differentiation. The JetBrains side never had a clean equivalent. Ayu Islands 2.6.0 ships one, written from scratch on JBUI.CurrentTheme primitives — not ported from VSCode, not a hack on top of UIManager.

Pin a color to a project, or to a programming language, and the following surfaces tint together:

• Status bar
• Nav bar (including the new 2026.1 Compact Navigation path widget)
• Tool window stripes (left / right / bottom)
• Panel borders

Foreground color is sampled per surface against the actually-tinted band, so contrast stays readable across the full intensity range. NosetForeground(WHITE) hardcode that falls apart at mid-luminance. Intensity slider lives in Settings → Ayu Islands → Theme Synchronization, 0–50% range tuned for daily readability rather than demo screenshots.

Free in 2.6.0

Editor color scheme follows theme variant. Switch Ayu Mirage / Dark / Light and the editor scheme auto-binds. Default ON; toggle in Settings. Important caveat: never overwrites a custom scheme. If Solarized is active, auto-bind doesn't kick in — your scheme stays yours.

Bug fixes worth naming

• Glow overlay no longer lingers when you switch to a non-Ayu theme (used to require restart)
• Sticky-line panel transparency — the floating scope header now has a solid background instead of bleeding code from the line below
• CodeGlance Pro & Indent Rainbow integrations revert in lockstep with the Settings sync toggle (used to leak the accent until restart)

Coming next

The remaining Peacock-parity items are queued:

• Shared accent committed to .idea/ so a team's project color lives in VCS
• Remote Environment awareness — Gateway, WSL, DevContainers, Code With Me guests get a distinct accent layer
• Darken / Lighten keyboard shortcuts (Alt+Cmd+− / Alt+Cmd+=)
• Favorites management with named colors
• Command Menu integration for every action

Install / feedback

• Marketplace
• Repo
• Friction, bug reports, suggestions — open a GitHub issue, or put a message on Discussions. I read all of them.

The plugin is freemium with a 30-day evaluation period. Everything works for the full 30 days; after that, per-project color set, chrome tinting, and accent rotation go premium.

Acknowledgements: Ike Ku @dempfi — author of the original Ayu palette — invited this onto ayutheme.com a few months ago. John Papa for Peacock, the workflow this release pays direct homage to.