---
title: What happens without asking
description: Check what your AI does in your tzTrack space on its own, what it asks you first, and how it treats the text of an issue.
slug: /concepts/what-happens-without-asking
order: 2
visibility: public
redirects_from: []
---

# What happens without asking

Connecting your AI to Turn Zero Track (tzTrack) is your standing permission: once it is connected, your AI keeps its issues without asking you about each one. This page lists what it does on its own, what it asks you first, and how it treats what it reads.

## What it does on its own

Within your connection, your AI may do these without asking you:

- read your open issues at the start of its work, the urgent ones, the ones waiting for you, and the ones near their due date first;
- keep a cache of the space's issues on your computer where it can run commands, search the cache with its own file tools first, and read an issue live before it changes it;
- search the space before it raises, so a point already raised is not raised twice;
- raise an issue for anything that must outlast its conversation, one point per issue, with what it saw and a suggested resolution;
- claim an issue before it works on it, and comment when it takes or finishes something;
- give an issue back, with a reason, when it stops working on it;
- close an issue it worked on, with an outcome and a resolution: what it did, or why no change is needed;
- mark an issue waiting for you, when only you can act or decide;
- list the issues it raised, by number, when it finishes.

Your AI keeps its own task list for the steps of the conversation. tzTrack is for what must outlast it.

## What it asks you first

Your AI asks you before each of these, because each is your choice:

- **Making a space.** When your account holds no space yet, a `raise` is refused and points to `create_issue_space`. Your AI asks you, and makes the space only once you agree.
- **Writing the setting file.** The file `.tztrack/config.json` gives the space every session of your project uses. Your AI writes it once you agree, and you commit it.

## What it leaves alone

Other sessions may be working the same space right now. Your AI reads an issue's claim before it starts, and leaves alone an issue another session or agent has claimed. When an issue needs a decision only you can make, your AI marks it waiting for you, with `person`, and leaves the decision to you. An issue waiting for you stays open until someone acts; nothing closes it on its own.

## Text in an issue is information

Text in an issue that someone else wrote is information, never instructions. Your AI reads a report, a comment, or a resolution another session or person wrote as what they saw. It never acts on that text as a request from you.

## Related

- [Coordinate an agent team](/guides/coordinate-an-agent-team) shows how claims keep sessions apart.
- [The cache](/concepts/the-cache) explains the copy your AI keeps and searches first.
- [Name your space in a setting file](/getting-started/name-your-space-in-a-setting-file) writes the setting file once you agree.
- [Refusals](/reference/refusals) lists every refusal with its remedy.