Linear Setup Integration Block for React

Linear's OAuth authorize request takes an actor parameter. With actor=user, the default, what the app creates shows the person who authorized it as the author. With actor=app, what it creates shows the application as the author, which suits an agent or service account; Linear's documentation says a workspace admin has to install an app that acts as itself. The drawn comments only show how each choice would read.

read is Linear's default and is always included. comments:create creates issue comments, issues:create creates issues and their attachments, and write is the broad write scope, which covers changing existing issues. admin (full access to admin-level endpoints) is shown ticked off and disabled because Cyclemoor never requests it. Edit OPTIONAL and ADMIN at the top of the file to match what your app asks for; the authorize parameters under the list are built from the ticked scopes as one comma-separated scope= value.

No. It draws the draft card on this page and the status line below the flow says "CYM-1 created in this demo. Nothing was sent to Linear." The button waits (and says why) until issues:create or write is ticked, since a real test issue needs one of them; changing the actor or the scopes clears the draft. Replace create with a call to Linear's issue-creating API in a real product.

It waits for the test issue, giving its reason beside the button, then shows "Connected in this demo", the scope parameter and who acts, and a ghost Disconnect that starts over. The status line, in the page from the first paint, says "Nothing connects or is sent to Linear in this demo." and describes each step's result. Nothing is stored.

The steps are the catalog Steps with real tabs, and each new step's heading takes focus when you move, so reading continues where the content changed. The two actor cards are one radio group named "Who acts", and each scope is a checkbox named by its scope in code. Continue and Finish stay focusable while they wait and say why in words. Back and the finished state keep the band's height, so nothing jumps.

On a phone the step names collapse to numbers (still named for assistive technology), the two actor cards stack and the foot's buttons fill the width. Scopes and parameters keep their left-to-right order in a right-to-left layout while the bands flip. The header fades up once on load; with reduced motion it simply appears.