Skip to main content
Book a demo

Connect Linear to Goose

Give Goose governed access to Linear’s 82 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Goose setup guide

Set up

Add Linear to Goose in four steps

Admins approve the server once. Everyone in Goose then gets it through the same governed connection.

  1. 1

    Approve Linear in Runlayer

    Add Linear from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Goose to Runlayer

    Users add the Runlayer Plugin as a Goose extension; Goose has no native plugin install. Goose reaches Linear’s 82 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Goose setup guide
  3. 3

    Sign in to Linear

    Sign in the way Linear requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Linear from Goose

    Linear’s approved tools appear in Goose. Every call is checked against policy and recorded.

Tools

82 Linear tools in Goose

Runlayer policy decides which of these Goose users can call. 17 read data only.

  • Create attachment

    Deprecated fallback for tiny files only.

  • Create attachment from upload

    Link an already-uploaded Linear assetUrl to an existing issue as an attachment.

  • Create initiative label

    Create a new Linear initiative label.

  • Create issue label

    Create a new Linear issue label.

  • Delete attachment

    Delete an attachment by ID

  • Delete comment

    Delete a Linear comment.

  • Delete customer

    Delete a customer in Linear

  • Delete customer need

    Archive a customer need in Linear

See all 82 Linear tools

Control

What Runlayer can see and stop in Goose

Some controls apply to every client at the gateway. Others depend on what Goose exposes to Runlayer.

  • Gateway policy (available)

    Every Linear call from Goose passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Goose as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Goose runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Goose’s model sees it.

  • Redact output in place (not available)

    Goose cannot apply masking, so Runlayer blocks output it would otherwise mask. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination