Workspaces & folders
A workspace is the shared ground your crew stands on. It holds your folders, their history and every conversation, so each model works from the same, current picture.
Adding folders
Drag any number of folders into the workspace sidebar, or click Add folder. Lumen reads the file tree and, if the folder is a Git repository, its branches and recent commits.
- Folders stay where they are on disk. Lumen doesn't copy them.
- Changes made by models are regular file changes you can see in Git.
- Files in
.gitignoreand.lumenignoreare never sent to a model.
Who can touch which folder
Every crew member has a folder list with an access level for each folder:
| Access | Meaning |
|---|---|
none | The model doesn't know the folder exists |
read | Can read files, can't change them |
write | Can create and edit files on a branch |
run | Can also run commands in the folder, subject to permissions |
Several projects
One workspace can span several repositories, for example an app, its landing page and the infrastructure. Models can hand off work across repositories: an engineer changing an API can ping the model that owns the frontend repo.
Ignoring files
Create a .lumenignore file at the root of a folder to keep files away from every model, using the same syntax as .gitignore:
# never send these to a model
.env*
secrets/
*.pem