---
title: Name your space in a setting file
description: Write .tztrack/config.json at your project's top level so every session in the project, on every computer, works the same tzTrack space.
slug: /getting-started/name-your-space-in-a-setting-file
order: 2
visibility: public
redirects_from: []
---

# Name your space in a setting file

Prompt:

> Make every session in this project use the same tzTrack space.

Also works: "Save which issue space this repo uses." "Set this project up so every session uses one tzTrack space."

## What your tool does

- Checks whether `.tztrack/config.json` is already at the project's top level, and reads its space if it is.
- Finds the space's id: the space your account holds, or the one `create_issue_space` makes once you agree.
- Writes the id into `.tztrack/config.json` once you agree, and asks you to commit the file.
- Passes that space as `space` in every later call from a session working in the project.

## What you need

- A connection signed in to Turn Zero Track (tzTrack) ([Connect your AI tool](/getting-started/connect-your-ai-tool)).
- A project folder you commit, so every clone has the file.
- A tool that reads and writes files on your computer, such as Claude Code or Codex. The chat in Claude and ChatGPT cannot reach files on your computer, so it never reads the setting 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.

## Before your AI starts

This section is for your AI coding tool: what it checks and gathers before it begins. You don't need to do these steps yourself.

- Whether `.tztrack/config.json` is already at the project's top level. If it is, the project already has its space: read it and write nothing.
- Whether the account holds a space. Where `raise` refuses and points to `create_issue_space`, it holds none: ask your person before making one.
- Your person's yes before you write the file. The file is theirs to commit.
- Whether you can write files in the project. Where you cannot, as in a chat app, write no file: pass the space in each call instead.

## Steps

### 1. Find the space

Where the account holds exactly one space, every tool uses it when `space` is left out. Where it holds none, ask your person, then call `create_issue_space`; its answer gives the new space's id.

### 2. Write the file

Write the space's id as the file's one member, `space`, in `.tztrack/config.json` at the project's top level:

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

The id above is an example. The file holds nothing else.

### 3. Ask your person to commit it

Tell your person to commit the file. Every session in the project, on every computer, then reads the same space from it.

### 4. Use it

A session working in the project reads the file at the start of its work and passes its `space` in every call.

## Expected result

`.tztrack/config.json` holds the space's id, and a `find` naming that space answers its open issues.

## Refusals

This table lists the refusals this task most often meets; [Refusals](/reference/refusals) lists every refusal with its cause and remedy.

| Refusal | Status | Cause | Remedy |
| --- | --- | --- | --- |
| `space_mismatch` | 403 | The space the file names is not one your account owns or is a member of. | Check the id in the file, and sign in with the account that holds the space. |
| `invalid_request` | 400 | The `space` value is malformed or missing. | Correct the member the detail names. |
| `credential_required` | 401 | The call carried no sign-in, or the sign-in did not finish. | Sign in again through your tool. |

## Related

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