Generate tiles from repositories

The "Generate tiles" feature allows users to generate a tile for private or public packages in your workspace. Once a tile is generated, evaluation data is provided to assess the effectiveness of the tile, which will assist in determining if the tile should be published, or not. In addition to individual packages, this feature can support monorepos with multiple packages.

Supported languages and frameworks

  • JavaScript

  • TypeScript

  • Python

Generation time

  • Approximately 15-30 minutes. This is dependant on complexity and size of code. During this time, Tessl analyzes your source code to generate context documentation and evaluation benchmarks that measure how well AI assistants can use your package.

How to generate a tile

  1. Select "Repositories" on the left hand menu.

  2. Click Generate tiles.

  1. Search for, and select, the repository to generate a file for. If the desired repository is not displayed, navigate to Repositories, and update the repositories accessible by the integration. The directory should point to a package/library and is generally not a full application. Tiles work best with reusable packages because they document APIs and patterns that AI assistants can apply across multiple projects, whereas applications typically contain project-specific logic that isn't meant to be reused.

  1. Select the packages to generate a tile for.

    1. You will be given the opportunity to update the metadata for the tile to be generated and for the branch it will be created under. It is suggested to use tessl/ as a branch prefix (e.g., tessl/my-package-tile) to easily identify Tessl-generated branches in your repository and keep them organized separately from your development branches.

    2. Click Generate tiles when ready

  1. The tiles will automatically be shown under the Tiles menu. A status: Generating, Creating evals, Scoring evals , or Complete, will be displayed next to each tile .

  1. Check back in 15-30 minutes for tiles to determine if it has completed generation by the status being set to Complete. Tiles will remain as a draft until published.

  1. Once generation is complete, review the evaluation results to assess the tile's effectiveness. If the results are satisfactory, click Publish next to your tile to make it available for use. See Reviewing a generated tile below for guidance on interpreting evaluation data.

Reviewing a generated tile

When a tile is completed, you may click on the tile name to review eval information, or choose to Publish, Close or Rerun. When deciding whether to publish or not, look for a positive improvement percentage.

When a tile is complete, click the Tile name to review the evaluation data and the tile.

The Overview tab allows you to review the tile or click the Eval Results tab to see the evaluation scenario(s)

Tile files

The tile generated can be reviewed from the Tessl interface from the left hand Evals and Docs menus, or you can navigate to the Git repository. A description of these files can be found in Configuration files.

Create a pull request and merge the code changes and publish the tile if it satisfies your requirements.

Reviewing using the Tessl Interface

Expand docs and evals to review the files

Reviewing from the Git repository

From the Tiles screen, click the repository name, then select the Tessl branch on your repository page to see what was created.

The tile will add markdown files and Configuration files representing the tile.

Publish your tile

Click Publish next to your tile or see Sharing tiles publicly.

Rerun-evals

After making changes, you can rerun an evaluation to determine if the changes were an improvement or not.

Close and delete draft

When creating tiles, you may determine you don't want to use a tile and may want to generate a new one. Click the menu next to your tile and select Close draft to close old drafts.

Private package credentials

From the Tiles screen, if using private packages (NPM , pypi), a popup can allow you to provide the necessary credentials.

Provide a name for the credential, and file with the connection information in the appropriate file type/format.

Troubleshooting

If tile generation fails or encounters issues:

  • Generation stuck or failed — Try closing the draft and regenerating the tile. Ensure the repository is accessible and the selected directory contains valid source code.

  • Poor evaluation scores — Review the generated documentation for accuracy. You can edit the tile files directly in your repository and use Rerun evals to re-evaluate after making improvements.

  • Repository not appearing — Navigate to Repositories and verify the GitHub App has access to the desired repository.

  • Private package errors — Ensure you've configured the correct credentials for NPM or PyPI packages.

For additional help, contact support through the Tessl dashboard or visit our community channels.

Last updated