Work in projects
For both engineering and non-engineering paths, you organize work in Glean Tau as projects. A project groups related chats and can optionally include local folders or a repository. The agent works with the right context and files each time you return to it.
When you work in a repository or a file directory, every chat belongs to a project. When you choose Don't work in a project, Glean Tau does not group your chats in the left navigation.
Create a project
There are two ways to create a project. Both methods let you chat with Glean Tau the same way.
- Import existing folder links a project to a folder you already have. Non-engineering users typically import a folder of documents. Engineering users typically import a repository.
- Start from scratch creates a project with a folder that Glean Tau manages for you. Use it when you want to organize chats and don't have an existing folder.
Understand how chats and projects interact
- A new chat in a project starts in that project's default working folder, so the agent has the right files in context.
- A project's chats stay listed together in the sidebar. You can pin a project to keep it near the top, and collapse it to hide its chats.
- Projects in Pinned and Chats start in name order. To reorder them, drag a project heading, or right-click it and choose Move up or Move down. Each section keeps its own order.
- You can move a chat between projects, or move chats that aren't in a project to one using Change project in the chat's context menu. The chat switches to the new project's working folder.
- Deleting a project with Delete project doesn't delete any files, and a linked folder stays on disk. Its chats move under No project, or to Archived if you select Move chats to Archived.
A project in Glean Tau is different from a project in Glean Web. A Glean Web project collects cloud files and instructions your team can share. A Glean Tau project is local to your device.
Take action on chat context
Each chat has an Overview. Select Toggle overview to open it. It summarizes what the chat is working with and gives you details on its context and actions you can take.
Overview shows only the sections that apply to the chat. For example, you'll see pull request information if you're working in GitHub. Here's a list of items you might see in Overview:
| Section | What it shows |
|---|---|
| Workspace | The project and the current working folder. |
| Git | The branch, the worktree if you're using one, and a summary of uncommitted changes. |
| Pull request | An open pull request for the branch. |
| Sources and links | Files and pages the agent used, and outputs the chat produced. |
| Agents | Background agents, with anything needing your attention listed first. |
Change the working folder or project
Two actions live in the Workspace section at the top:
- Change the working directory. Select the working folder row to point the chat at a different folder. This affects only that chat, not the project default. Hovering the row shows the full path, and a copy button beside it copies the path.
- Move the chat to another project. Select the project row to move the chat, the same as Change project in the sidebar menu. The chat switches to the new project's working folder. Choosing No project keeps its current folder.
Both actions are unavailable while the agent is running or has queued messages, so the working folder can't change underneath an active turn. Wait for the turn to finish. In a new chat, send a message before changing its project or folder.
If the chat's folder has been moved or deleted, Overview flags it and the pill shows a warning.
Track a pull request
For engineers, the Git and Pull request sections turn Overview into a status check you don't have to leave the chat for.
- Git shows the current branch, or Detached HEAD when the checkout has no branch. If the project's folder isn't a repository, it reads Not configured, and you can select Initialize Git.
- Pull request appears when the branch has an open pull request. It shows the PR number, title, and whether it's Open or Draft. Selecting it opens the PR in your browser.
- Failing checks and unresolved review comments appear as counts, and you can expand the checks to see which ones failed.
The pill surfaces these counts without opening the popover, so a failed check is visible while you keep working. The Git and Pull request sections come from the Git extension and appear only when the chat's folder is a Git repository.
See also
- Agent approval modes — control what the agent can do in a project's folder
- Get started for engineering users — import a repository and review code
- Get started for non-engineering users — set up a local workspace and create artifacts