Updated just now

Share this article

Related News

Box adds four agent skills while keeping account access separate

Oct 26, 2026

Box adds four agent skills while keeping account access separate

Box’s October 22 release packages guidance for CLI, MCP, SDK and integration tasks. Installing the instructions does not authenticate an agent or expand its Box permissions.

BoxAgent SkillsMCP

Docker’s BAND kit brings local agents into shared collaboration rooms

Oct 26, 2026

Docker’s BAND kit brings local agents into shared collaboration rooms

Docker’s October 21 walkthrough connects a repository agent in a sandbox to people and remote agents through BAND rooms. Model choice, credentials, workspace tools and network access remain distinct setup decisions.

DockerBAND AIAI agents

Cohere reports a blocked network request during a Qwen agent test

Oct 26, 2026

Cohere reports a blocked network request during a Qwen agent test

Cohere says its sandbox blocked an unexpected request during a security-agent task. The vendor report leaves intent, reproducibility and the wider scope unresolved.

CohereQwenAI agents

Linear adds Slack and GitHub triggers, shared templates and reasoning settings to Loops — Source: OpenTools Team · Original source-based feature guideSource image

Linear adds Slack and GitHub triggers, shared templates and reasoning settings to Loops

By OpenTools Team

Linear’s October 22 release lets Slack and GitHub events start Loops, adds workspace templates and exposes reasoning settings. The notice leaves plan access, full event filters and connection permissions unspecified.

Slack and GitHub events can start a Loop

Linear’s October 22 changelog adds external triggers, shared templates and reasoning controls to Loops, its feature for automating product work. Events in Slack and GitHub can now start a Loop automatically, extending the workflow beyond waiting for someone to notice a change and ask an agent to act.

The release gives two concrete examples: answering product questions in a Slack channel, and drafting a QA plan when a GitHub pull request receives a “ready for testing” label. The latter is a plan‑writing example, not a report that the Loop executes the tests or validates a release. The full supported‑event matrix and connection permissions are not specified in this notice.

Templates reuse a workflow inside the workspace

The same release lets users save a Loop as a template for others in their workspace. Linear uses a bug‑triage Loop as its example: another team can adapt that workflow instead of rebuilding its configuration from scratch.

The documented action is to open a Loop’s menu and choose Save as template. The result appears alongside Linear’s built‑in templates when someone in the workspace creates a new Loop. This establishes a reuse path for the workflow. It does not document the transfer of connected‑account credentials or expanded access to a repository or Slack channel.

Auto inherits a workspace setting

Loops also gain a reasoning‑level choice. Auto uses the workspace’s default setting; the explicit alternatives are Low, Medium and High. That is a per‑Loop configuration choice in the announcement, rather than a documented mapping to a particular model or token budget.

Linear presents the setting as a way to match reasoning effort to the task. The release supplies no per‑run prices, numerical reasoning limits or measured outcome comparison. A different setting should not be described as a verified improvement in correctness, speed or cost.

Separate capability announcements from a working connection

The changelog describes these capabilities as available, but does not identify the applicable subscription plans, rollout cohorts, full event filters or the permissions needed for each connection. It also does not establish whether a particular workspace has already connected the required Slack or GitHub accounts.

For a team adopting the features, the useful checks are the chosen starting event, the task the Loop is asked to produce, the template being reused and the selected reasoning setting. Those are separate from confirming the connected accounts and reviewing the resulting work. OpenTools has read the official release; it has not created a Loop, connected an account or tested its output.

Original source‑based feature guide by OpenTools Team, based on Linear’s October 22 changelog. The guide summarizes event triggers, workspace templates and reasoning controls; it is not Linear’s interface or evidence of an executed loop. The same features and their limits are explained in the article text.

Sources

1.reasoning-level choice (linear.app)
2.imagedelivery.net (imagedelivery.net)

Tags

LinearAI agents Slack GitHubDeveloper workflows