<.
### Assistant and conversations
In the assistant panel on the right, a project can have several conversations: switch, create, or delete them at the top of the panel. You can drag the panel wider or collapse it; when collapsed, a narrow strip stays at the right edge of the window, and clicking it expands the panel.
- Each conversation cannot see the contents of earlier conversations. What carries over is the tables and the folder, so anything you want to keep, ask the assistant to record in a table.
- Before each reply, the assistant knows: the project name, the names of the accounts available to the project (it cannot see the secrets), which tables there are, and which rows have changed since its last reply, including changes you made in a table and changes made by other conversations.
- Which model the assistant in a project uses is chosen in "Settings › AI Settings › Agent › Project"; see [Choose a model for each agent](/en/guide/models.md#choosing-a-model-for-each-agent).
### Gear menu
- **Accounts**: which of your accounts (including email) gems working in this project can use. None are checked by default; an account that is not checked cannot be used when a gem works for this project. The assistant can see the names of checked accounts, not the secrets.
- **Tools**: which tools the project assistant can use. If you have not changed it, it is the same as the "Chat" assistant; the table tools are always on.
- **Code permissions**: see [Project code](#project-code) below.
- **Open folder**, **Choose folder…**: a project uses its own folder by default, but you can switch to an existing folder on your computer so you don't have to import the files again. You cannot choose your home directory, system directories, the app's own data directory, or hidden folders. When you switch folders, files are not moved; the files on both sides stay where they are. Click "Use the project's own folder" to switch back.
- **Delete project**: deletes its conversations and tables; the project's own folder goes to the trash; a folder you chose for it is left alone.
Changes to accounts and tools take effect only after you click **Save**.
## Project code
The assistant can write tools and SOPs (automated procedures) for a project, so the project can fetch data itself, process it row by row, or run automatically on a schedule. This code uses the project's own tables and folder.
Before the code can do any of the following, it needs your permission:
- access a website on the internet;
- access the local and internal-network addresses you listed in "Settings › System › Network Access";
- use an AI model;
- run automatically on a schedule.
The top of the project page lists each item it requests, and it takes effect only after you click **Allow**. If only the code changed, or it asks for less than before, you are not asked again. The assistant cannot allow on your behalf.
Under the gear menu › "Code permissions" you can see the items already allowed, and you can **Revoke all**: after that, scheduled runs stop and the code does not run until you allow it again.
## Build view
Switching the top bar to "Build" shows the code behind the project: tools, SOPs, change history, and publishing. It looks like the Gem Studio workbench: you can read and edit code, test-run tools and SOPs, see the input, output, and errors of each run in the run log, and go back to earlier versions in the history.
On the right it is still the same assistant and the same conversation. Most of the time you don't need to open the Build view; just have the assistant write and change the code.
## Publish as a gem
Click **Publish…** in the top bar of the Build view. Publishing fixes this project's format and makes it a gem: anyone who installs it gets the same tables and code, starting empty.
- **Included**: the structure of the tables (tables, columns, types, including hidden ones), tools and SOPs, and the permissions the code requests.
- **Never included**: data in the tables, files, accounts, conversations.
- The canvas cannot yet be put into a gem; the publish dialog states how many blocks will not be included.
- If the code contains something the project cannot yet publish, publishing is blocked and the dialog lists the reasons.
There are two kinds of publishing:
- **Install on this computer**: installs it as a gem on this computer. It appears among the gems on Home, and its settings are on its own page (see [Gems: Install and Use](/en/guide/gems.md)). Publishing again updates this gem.
- **Export a .gem file**: produces a file you can give to others or import in Gem Studio.
The top bar of the Build view shows the publish status: "Not published", "Published to this computer", or "Changes not yet published".
For an installed gem, the table format is fixed: you cannot change its table structure inside the gem. It changes only when you go back to the project, make the change, and publish again.
]]>