Configuration files
Tessl uses two main configuration files that live in your project root:
Project config
The tessl-config.jsonc file in your project directory contains structured configuration for your Tessl project. This file uses JSON with comments (JSONC) format.
You can manage your project config using tessl config commands in your project directory.
Schema
name
string
Tile name
Example
{
"name": "my-project",
}Global config
The ~/.tessl/config.jsonc file in the home directory contains structured configuration for the Tessl CLI. This file uses JSON with comments (JSONC) format.
You can manage the project config using tessl config commands with the --global or -g flag in the project directory.
Schema
shareUsageData
boolean
You can opt out of data sharing as explained in Sharing Usage Data by setting this to false (default: true)
Example
{
"shareUsageData": true,
}AGENTS.md
The AGENTS.md file provides project context to LLMs during code generation. This file is similar to CLAUDE.md and other context files.
After running tessl init, it will be updated to be structured into multiple sections. Some are managed by Tessl and are marked with <!-- tessl-managed -->.
As part of interacting with your agent while getting started with Tessl, context about the project stack, testing commands and the like will be automatically added. If you are not using a coding agent, add these yourself by replacing the "New Project Bootstrapping" section in AGENTS.md.
You are also free to add further details and context about your project as you would typically. The content of AGENTS.md and its links is automatically included in LLM prompts when generating code, helping ensure consistency with your project's patterns and conventions.
Purpose
Gives context to your agent about the Tessl framework
Defines your project's ecosystem and dependencies
Specifies coding conventions and patterns
Sets up project file layout expectations
Linking to Additional Files
AGENTS.md supports linking to other files in your project, and these linked files are automatically loaded and included in the LLM context during code generation. This allows you to modularize your project configuration and keep related information in separate files.
By default Tessl installs some modularized context in .tessl/framework.
Link Format
Use standard markdown link syntax to reference other files:
[link text](./relative/path/to/file.md)Links should be relative paths from the file containing the link.
Init files
When logged out, tessl init creates the following files and directories:
|-- AGENTS.md # Agents directives
|-- KNOWLEDGE.md # Knowledge Index (keeps track of Usage specs)
|-- tessl.json # Usage specs packages config
|-- .tessl # Tessl configuration directory
| |-- .gitignore
| |-- framework # Tessl Framework prompts
| | `-- usage-specs.md
| `-- usage-specs # Downloaded usage specs
| `-- tessl
| `-- <package-name>
| `-- <package-version>
| |-- docs
| | |-- index.md
| | `-- ....
| `-- specs.json
When logged in, tessl init creates the following files and directories:
|-- AGENTS.md # Agents directives
|-- KNOWLEDGE.md # Knowledge Index (keeps track of Usage specs)
|-- tessl.json # Usage specs packages config
|-- .tessl # Tessl configuration directory
| |-- .gitignore
| |-- framework # Tessl Framework prompts
| | |-- agents.md
| | |-- bootstrap.md
| | |-- docs
| | | |-- spec-driven-development.md
| | | `-- spec-format.md
| | |-- plan-files.md
| | `-- tessl-system-prompt.md
| `-- tmp # session information etc
| |-- ...
| `-- usage-specs # Downloaded usage specs
| `-- tessl
| `-- <package-name>
| `-- <package-version>
| |-- docs
| | |-- index.md
| | `-- ....
| `-- specs.json
Last updated