Repository navigation
feat(web): simplify Slack sign-in with a configured app - #141
Draft
adampeterhiggins wants to merge 1 commit into
Draft
adampeterhiggins wants to merge 1 commit into
adampeterhiggins wants to merge 1 commit into
Conversation
adampeterhiggins
force-pushed
the
ah/slack-configured-app-sign-in
branch
from
October 2, 2026 08:12
a8e5343 to
54bbd61
Compare
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.
Slack settings currently instruct users to create a workspace app even when the environment already has an app client ID configured. Users should be able to sign into a supplied app without going through app creation.
Show direct account sign-in guidance when an app is configured, with an optional Change app form that preserves workspace-specific setup. Cancelling an app edit restores the configured ID. Document shared-app configuration through the existing T3CODE_SLACK_CLIENT_ID setting, workspace approval requirements, and Slack distribution/rate-limit constraints. The existing PKCE authorization, credential storage, remote callback, and disconnect paths are reused.
This does not register a shared Slack app or provide a bundled client ID. An operator must register/configure the app separately; Marketplace approval and workspace approval remain external prerequisites where applicable. Mobile can attach Slack context after connecting through web or desktop, as before.
Validation:
Model: GPT-6.1-Sol. Harness: Codex in T3 Code.