Skip to content

Notion Support, Pack-Driven Roles & Guided Workspace Setup

2026-08-23 · portal & platform release

Notion joins the issue trackers

SideButton now speaks Notion alongside Jira and Linear. Connect a Notion workspace and a board database becomes a tracker: new pages route into your Tasks pool by type, agents work them, and status flows back using the board's own status groups — your columns stay yours. Automations gain a Notion trigger:

New Automation form with the trigger type set to Notion; a hint explains that a Notion workspace connection is required to enable filters

The portal is honest about prerequisites — pick the Notion trigger before a workspace is connected and it says exactly what is missing and where to fix it, instead of failing later. Workspaces bind a specific Notion data source (not just a database name), with a property map that adapts to the fields your board actually has. A step-by-step setup guide covers connecting the workspace, sharing your board with the integration, and the capability toggles that matter.

GitLab joins the code hosts

SideButton agents now work GitLab end to end. Connect gitlab.com with a personal access token, attach projects to your workspaces — including ones nested in subgroups — and agents branch, push and open merge requests the same way they open pull requests, with the delivery gate verifying the merge request's real state before a run is called done. Agent VMs ship with glab preinstalled, and the connection card captures your token's expiry and warns ahead of it instead of failing on the day.

GitLab connect dialog on the Integrations page: personal access token field, required scopes hint, Test and Save actions

Workspace setup that tells the truth

The workspace edit page now walks new workspaces through setup — assign agents, connect code, route tracker work — with a state ledger that reflects what is actually configured. The apply flow reports all three of its states honestly: idle shows what would change, in-flight shows progress, done collapses to a result you can check.

Workspace edit page with the guided setup panel, tab bar, and the workspace state ledger on the right

Roles come from your pack

The role registry is now pack-driven end to end: besides the built-ins, any role your skill pack ships (as a role playbook file) registers automatically — with friendly labels, and the ability for a pack to mark a role as always eligible for dispatch, so granting a new role to your fleet is a pack change, not a per-agent settings tour.

Claude Code plugins, picked and verified

Creating a cloud agent now offers a typed Claude Code plugin picker, kept separate from SideButton's own plugin catalog so the two never blur. Picked plugins install at first boot, and each agent reports the install result on its health endpoint and detail page — a failed plugin is visible state, not a silent gap.

Claude Code plugins block in the create-agent wizard: marketplace picker and a plugin combobox, up to 20 installed at provision

Jira app: working from the first handover

Connecting the SideButton app to a Jira site now seeds issue-type routing and binds the first project to a workspace at handover — the first assigned ticket can dispatch without any manual routing setup. Upgrades from token-based connections verify they are talking to the same site before switching, and interrupted installs recover instead of leaving the account without a dispatch path. Installing from the Atlassian Marketplace before you have a SideButton account now carries the install through signup — the connection finishes itself once you're in.


Self-hosted releases (npm) are covered in their own posts — latest: SideButton 1.5.5. Complete change list: Changelog.

Released under the Apache-2.0 License.