---
title: The setting file
description: Look up the form of .tztrack/config.json, the file that gives the tzTrack space every session in a project uses.
slug: /reference/the-setting-file
order: 2
visibility: public
redirects_from: []
---

# The setting file

The setting file gives the space a project uses, so every session in the project, on every computer, works the same space. This page gives its place, its form, and who writes it.

## Where it stands

The file is `.tztrack/config.json`, at the project's top level. It is for a project without tzTeam.

Only a tool that reads files on your computer, such as Claude Code or Codex, reads the file. The chat in Claude and ChatGPT cannot reach files on your computer, so it never sees the file. In the Claude desktop app, the Code tab can. In the chat, your AI passes the space in its calls, or uses your account's one space.

## Its form

The file holds one member, `space`, the space's id, a lower-case UUID as `create_issue_space` gave it:

```json
{ "space": "6f1c2d9e-4b7a-4c3e-9a51-2d8e7f0b3c64" }
```

The id above is an example. The file holds nothing else, and nothing secret: who may work the space is decided by the account that signs in, never by the file.

## Who writes it

Your AI writes the file once you agree, and you commit it. Every clone of the project then has it, and every session working in the project passes that space in its calls. [Name your space in a setting file](/getting-started/name-your-space-in-a-setting-file) gives the steps.

## Related

- [The tools](/reference/the-tools) says which tools take `space`.
- [What happens without asking](/concepts/what-happens-without-asking) says why writing the file asks you first.