docs: clarify secrets vs inputs syntax usage #8166
Merged
Conversation
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
![continue[bot]](https://avatars.githubusercontent.com/in/1916892?s=80&v=4){kind=small}
Add info blocks to documentation explaining when to use secrets. vs inputs. syntax: - Recommend secrets. as the default for most use cases - Explain inputs. provides flexibility for reusable blocks - Reference GitHub Actions pattern for clarity This addresses user confusion around the two syntaxes and provides clear guidance on when each should be used. Generated with [Continue](https://continue.dev) Co-authored-by: Ting-Wai To <tingwai@continue.dev> Co-authored-by: Continue <noreply@continue.dev>
dosubot
bot
added
the
size:S
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Patrick-Erichsen
approved these changes
Oct 13, 2025
|
🎉 This PR is included in version 1.28.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Summary
This PR addresses confusion around when to use
secrets.vsinputs.syntax in Continue configuration blocks.Changes
Added informational blocks to two key documentation pages:
docs/guides/configuring-models-rules-tools.mdx - Added an info block in the "Working with Secrets" section explaining:
secrets.is recommended for most use cases (both personal and organizational)inputs.should be used when flexibility is needed (reusable blocks, customizable secret names)docs/hub/blocks/create-a-block.mdx - Added an info block in the "Block Inputs" section clarifying:
inputs.to allow customizationsecrets.directlyContext
Based on Slack discussion: https://continuedev.slack.com/archives/C060AV775UZ/p1759954189314559?thread_ts=1759954189.314559&cid=C060AV775UZ
Related Linear issue: CON-3803
Testing
This agent session was co-authored by tingwai and Continue.
Summary by cubic
Clarifies when to use secrets vs inputs in Continue configuration, recommending secrets for most workflows and inputs for reusable, customizable blocks. Adds info blocks to the configuring models/tools guide and the hub block creation page; addresses Linear CON-3803.