Skip to content

For the complete documentation index, see llms.txt.

Context sources

Context sources are integrations that give Promptless read-only access to the tools where your team keeps product knowledge. These include issue trackers, wikis, and shared documents. A code change shows what changed. The issue, spec, or design doc behind it often explains why, and sets the names and limits the docs should use. Promptless reads that material while it drafts a documentation suggestion.

Context sources are optional. Without them, Promptless still creates suggestions from the triggering change and your existing docs.

Each context source answers a question the code change alone can’t:

When the answer lives in…ConnectPromptless then
An issue that records the requirements, such as a 10,000-row import cap or a plan restrictionJira or LinearReads the issue the pull request references, finds related issues, and carries the requirements into the suggestion.
A wiki page of team conventions, such as the pagination parameter names every API endpoint usesConfluenceFinds the page and documents the new feature with the same conventions.
A spec or PRD that settles a feature’s official name, limits, and rationale, such as a “Rate Limiting v2” docNotion, Google Drive, or SliteReads the spec the pull request links to, or finds it by search, and reuses its exact names, numbers, and reasoning.

Each context source page walks through a full example.

When a trigger starts documentation work, Promptless reads the triggering change and any issue, page, or file it links to in a connected source. It also searches your connected sources for related material, then drafts the suggestion with what it finds.

Diagram of triggers and optional context sources feeding Promptless, which proposes updates to your doc collections

Each context source has its own page for connecting and scoping it:

To request another context source, contact help@gopromptless.ai.

Connect each source on the Integrations page. Promptless can read a source as soon as it’s connected, up to everything the connected account can reach.

To narrow a source to specific projects, spaces, teams, databases, drives, or folders, scope it on the Context sources tab of the Configuration page. The tab edits the context_sources section of your promptless.yaml file. A source with no scope, or no entry at all, stays fully readable. Each context source page shows how to scope that source, and the Configuration Reference lists every field.

Context sources follow the same data handling as Promptless’s other integrations. See Data handling and classification.

Real-time queries only

Promptless doesn’t store your organization’s data from context sources. It queries each source’s API when a documentation task needs it, and reads only the information that task requires. Some sources cache results briefly during a documentation session, then discard them.

Secure authentication

Context sources connect through OAuth 2.0, except Slite, which connects with an API key. Every connection:

  • Reads with the permissions of the account that authorized it
  • Encrypts data in transit with TLS 1.2 or higher
  • Uses token-based access that you can revoke at any time