Repository navigation
feat: add optional Linear agent integration to generated projects - #52
Open
armandocanals wants to merge 1 commit into
Open
armandocanals wants to merge 1 commit into
armandocanals wants to merge 1 commit into
Conversation
armandocanals
marked this pull request as ready for review
November 2, 2026 03:09
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Generated projects can optionally accept Linear mentions, issue delegations, and follow-up messages through a Hermes directory plugin. The integration supplies meaningful progress updates, temporary liveness indicators, and standalone status replies that bypass long-running work.
Ship the plugin with a signed Lambda webhook receiver, encrypted SQS FIFO queue and dead-letter queue, durable SQLite inbox, scoped execution policy, and mapped-secret configuration. Wire installation, upgrades, rotation, and removal into the generated setup/manage/teardown skills. Project names and AWS regions follow the generator's substitutions.
The default Slack deployment stays unchanged. Enablement requires the documented compatible Harness image upgrade, preserves existing enabled plugins, and uses a separate stack that is removed before the main gateway stack. No custom image or Harness CLI change is needed.
Replaces boldblackai/harness#212: deployment scaffolding and lifecycle management belong in Dispatch.
Validation:
Draft pending the maintainer's live integration cycle and acceptance. The configured integration project and corkboard are unavailable in this checkout; no AWS resources were deployed or live Linear requests sent. Verify setup, follow-up replies, status, Stop, restart recovery, acknowledgement timing, and teardown on a disposable issue before acceptance. The plugin targets Hermes v0.22.2 in
hermes-1.12.0and uses internal task/final-delivery interfaces that need rechecking on upgrades.