Skip to content

FloatingBar v0.2.0

Pre-release
Pre-release

Choose a tag to compare

@orkvacy orkvacy released this 31 Oct 11:20
· 2 commits to main since this release

FloatingBar v0.2.0

Answer Claude’s permission prompts from your floating bar, with daily planning and improved Discord voice controls alongside your music and notifications.

Highlights

  • Review Claude commands and answer Allow / Deny without switching windows, through Claude desktop prompts or the Claude Code hook.
  • Local to-do list: add, edit, complete, and delete tasks.
  • Today’s Google Calendar agenda with shared/subscribed calendar selection, recurring events, and read-only OAuth PKCE sign-in.
  • Discord voice members, speaking indicators, bounded per-member volume sliders, reconnect controls, compact avatars, and pin to stay expanded.
  • Drag the header to position the bar; drag page content to switch slides. The bar expands upward near the bottom and stays within the monitor’s work area.
  • Discord credentials are configured locally instead of bundled in source. Discord and Google credentials/tokens use Windows DPAPI encryption.
  • Refreshed documentation and screenshots using fictional demo data.

Install

Download FloatingBar_0.2.0_x64-setup.exe or FloatingBar_0.2.0_x64_en-US.msi below and run it on Windows 10/11. Quit any running FloatingBar instance before updating.

Notes

  • This is a pre-release. The interface is in Indonesian; installers are not code-signed.
  • Claude desktop integration requires the app’s English interface. Claude Code permissions require the hook documented in the README.
  • Discord voice requires Discord desktop and your own application credentials with appropriate RPC access. Configure these in the Discord panel.
  • Google Calendar is optional and requires a Desktop OAuth client. Existing connections may need Perbarui izin Google to list shared calendars.
  • If you used a Discord secret from an earlier source version, rotate it in Discord Developer Portal and enter the replacement locally. Removing a secret from the latest source does not invalidate copies in Git history.