Arcadia Hub

approved

by arcadia-studio

GitHub integration: browse issues, pull requests, and repos from your notes. Create issues directly from note content. - This plugin has not been manually reviewed by Obsidian staff.

1 stars93 downloadsUpdated 1mo agoMIT

Arcadia Hub

Arcadia Hub puts your GitHub workflow inside Obsidian. Browse repositories, triage issues, and review pull requests from a sidebar panel, then turn any note into a GitHub issue without leaving your vault. If your project notes and your project code live in different windows, this plugin closes the gap.

Arcadia Hub

Version Obsidian License

Desktop only.

Features

FeatureFreePremium
Repository browser with active repo switchingYesYes
Issues viewer with open/closed filter, label filter, and paginationYesYes
Pull request dashboard with state and review statusYesYes
Create a GitHub issue from the current noteYesYes
Auto-refresh on a configurable intervalYesYes
Claude Code bridge (in development)NoYes
Audio notebook sync (in development)NoYes
AI router (in development)NoYes

The entire GitHub module is free. Premium covers the additional modules listed in settings, which are in development and will ship in future releases. Buying now supports development and unlocks them on arrival.

Install

Community Plugins listing is pending review. Until it is approved, install with one of these methods:

BRAT (recommended)

  1. Install the BRAT plugin from Community Plugins
  2. In BRAT settings, choose "Add beta plugin" and enter Arcadia-Studio/obsidian-arcadia-hub
  3. Enable Arcadia Hub in Settings > Community plugins

Manual install

  1. Download main.js, manifest.json, and styles.css from the latest GitHub release
  2. Create the folder .obsidian/plugins/arcadia-hub/ in your vault and copy the three files into it
  3. Reload Obsidian and enable Arcadia Hub in Settings > Community plugins

Quick start

  1. Generate a GitHub personal access token with repo scope at github.com/settings/tokens
  2. Open Settings > Arcadia Hub and paste the token
  3. Set your default repository in owner/repo format
  4. Open the hub from the ribbon icon (git branch) or the "Open hub" command

From there: the Issues tab lists open issues with label filtering and pagination, the Pull requests tab shows PR state and review status, and the Repos tab lets you switch the active repository. Run "Create issue from note" in any note to open a pre-filled issue form (selected text becomes the body; with no selection, the full note is used).

Settings

SettingDescriptionDefault
Personal access tokenGitHub token with repo scope. Stored locally in this vault's plugin settings and masked in the UI.empty
Default repositoryRepository shown on open, in owner/repo formatempty
Show closed issuesInclude closed issues in the issues listoff
Issues per pageNumber of issues loaded per page (1 to 100)25
Auto-refresh intervalMinutes between automatic refreshes; 0 disables0
License keyPremium license key with a validate buttonempty

Pricing

The GitHub module is free, with no account beyond your own GitHub token. Premium modules require a one-time license from arcadia-studio.lemonsqueezy.com.

To activate: Settings > Arcadia Hub > License key > Validate. Licenses are validated against the Lemon Squeezy API. Once validated, premium keeps working for up to 14 days without a connection to the license server, so an offline stretch never locks you out.

Network use and privacy

  • The plugin calls the GitHub API (api.github.com) to list repositories, issues, and pull requests, and to create issues. Your token is sent only to GitHub and stored only in your vault's plugin settings.
  • License validation calls the Lemon Squeezy API (api.lemonsqueezy.com) and sends only the license key you enter.
  • No telemetry, no analytics, no other network calls.

Support

Questions, bugs, feature requests: open an issue or email arcadiastudio77@gmail.com.

License

The plugin code is MIT licensed. See LICENSE.

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.