Working with files
Review Slack attachments and save or update files in your Tag workspace.
Your workspace is the folder where Tag works on your files. Upload a brief in Slack and ask Tag to save the open questions there. As you answer them, ask Tag to update the saved file.
This guide uses Codex and assumes you have completed your first Tag task. Claude remains experimental.
Turn a brief into questions you can resolve
Before a launch meeting, attach your existing brief as a text or Markdown file to a Slack message mentioning Tag. Ask it to flag anything you need to settle before launch, then answer its questions in the same thread.
Iris attached launch-brief.txt
Launch: Monday. FAQ: Jules, due Tuesday. Signup testing: Iris, due Wednesday. Support must be briefed before launch. Go/no-go approval is required.
@Iris's Tag review this and save the open questions as open-questions.md in your workspace.
Saved the questions in open-questions.md:
Are the FAQ and signup testing due the week before launch?
Who will brief support, and when?
Who makes the final call to launch?
@Iris's Tag yes, both are due the week before. I'll brief support on Thursday. Update the file.
Tag has updated open-questions.md. One decision remains: who makes the final
call to launch?
Click ↗️ open-questions.md to open the saved file, or 📁 Open folder to browse
its folder. Both open on the computer running Tag. If someone else hosts Tag,
they open on that person's computer.
Uploading the brief lets Tag read it for the request. It does not automatically
save a copy of the brief in the workspace. In this example, you asked Tag to save
open-questions.md.
Files and indexing
Files saved in the workspace are not automatically indexed. However, Tag can still locate and read them using a filename you mention or one already in the conversation. See What Tag knows for how indexed search works.
Find your workspace
The workspace lives on the computer running Tag. If someone else hosts Tag for your team, the folder is on their machine. On the computer running Tag, open a terminal and run:
tag pathsFind the workspace path in the output. On a default macOS installation it is
~/Library/Application Support/Tag/workspace. Other platforms and custom
installations use different locations, so use the path your command reports.
Tag keeps this folder separate from its application releases. Files and local skills stay in place when you upgrade. You can organize it like any working folder:
workspace/
open-questions.md
meeting-notes/
templates/
weekly-report.mdThe workspace is the agent's starting directory. Its actual file and command access depends on the backend's permissions; the folder itself is not a sandbox. See the security policy for the execution model.
Last updated