Connecting to your repositories
Connect Tessl to your codebase to automatically generate, evaluate, and optimize context!
Apply coding standards for agents across all your repos
Configure and update multiple codebases automatically with GitHub pull requests
Tessl connects directly to GitHub so you can initialize repositories and roll out shared guidance (coding standards, conventions, and agent instructions) across your codebase, automatically through pull requests (PRs).
Without this integration, teams rely on manual edits, onboarding docs, or one-off repo configuration. With the GitHub App enabled, Tessl can use branches and PRs to:
add the configuration files needed to use Tessl (
tessl.json,.mcp.json)update those files as your guidance evolves
apply the same guidance to multiple repositories in a single action
keep every change visible, reviewable, and merge-controlled
Nothing is applied directly to your codebases, every update ships as a PR you review and merge like any other change.
What you can do with Repository Integration
Once GitHub access is enabled, you can perform three core actions:
1. Initialize a repository for Tessl
Tessl generates a PR that may include:
a new or updated
tessl.jsona
.mcp.jsonfile enabling Tessl as an MCP server
You merge whenever you’re ready.
2. Distribute shared guidance across repositories
From the Tessl interface, you can select a guidance resource and generate pull requests across multiple repositories at once. This capability is helpful for rolling out:
coding conventions
architectural patterns
internal standards
agent instructions
3. Remove the integration at any time
Uninstall the GitHub App and remove the connection from Tessl.
What this guide covers
This documentation walks through four workflows:
Enable the GitHub App so Tessl can create pull requests.
Use the Setup action to generate configuration inside a repository.
Distribute tiles across multiple repositories*
Select a resource and generate PRs across the repositories you choose.
Uninstall the GitHub App and remove the connection from Tessl.
*Each workflow ends with a pull request, reviewed and merged through your normal development process.
Last updated

