ccc-linear

/ccc-linear — Linear board

CC Commander · /ccc-linear · the project board by status, issue pickup and quick issue creation. Linear is opt-in and absent by default.

Usage

/ccc-linear              # open the board
ccc > Linear Board       # same board in the ccc CLI menu

What happens

1. Detect the access path. Run in one Bash call; never print the key:

   test -n "${LINEAR_API_KEY_PERSONAL:-$LINEAR_API_KEY}" && echo "key: set" || echo "key: missing"
   command -v ccc >/dev/null && echo "ccc: installed" || echo "ccc: missing"
   

   Then check whether a Linear connector is exposed in this session (load deferred tools with ToolSearch query +linear issues).

   • Connector available: use its list, update and create tools for every step.
   • Key set and ccc installed: use the CLI integration in step 2.
   • Neither: go to "Setup" and stop.

2. Load the board. With the CLI integration, resolve the install and read the configured project (set in ccc > Settings > Linear Setup):

   CCC_ROOT="$(cd "$(dirname "$(realpath "$(command -v ccc)")")/.." && pwd)"
   node -e 'const l=require(process.argv[1]+"/commander/integrations/linear");l.getIssuesByStatus().then(g=>console.log(JSON.stringify(Object.fromEntries(Object.entries(g).map(([k,v])=>[k,v.map(i=>({id:i.id,identifier:i.identifier,title:i.title}))])))),e=>{console.error(e.message);process.exit(1)})' "$CCC_ROOT"
   

   A non-zero exit means no auth or no configured project; report the error text and point to "Setup". Four empty lists with the key set usually means no project is configured; point to Setup step 3. Shell state does not carry between Bash calls, so repeat the CCC_ROOT= line at the top of the step 5 and step 6 commands.

3. Render the board from the fetched data, counts computed from the response:

   ─── Linear Board ───────────────────
   ████████████████░░░░░░ 18/24 done
   
   In Progress (2)
     ENG-61 Hero video
     ENG-62 README overhaul
   Todo (3)
     ENG-48 Foundation
   Backlog (1)
     ENG-50 CLI UI
   Done: 18 issues