The workspace
Projects
A project gathers every conversation, file, page and piece of code Alias produced for one piece of work, so the output of an assistant stops being a hundred chats you can never find again.
One home per piece of work
Sessions, artifacts and imported repositories sit together under a name you chose, with a history you can scroll back through.
Import a repository
Point Alias at a GitHub repository and it becomes a project, so questions about the code are answered from the code.
A starter for anything visual
The project starter generates images and video inside the project, so the assets live beside the work that needed them.
How it works
- 01
Name the work
Create a project, or let a saved session create one for you.
- 02
Work inside it
Every session you file there contributes its files and its pages to the project.
- 03
Come back to it
Open the project and the whole trail is there, newest first, with everything Alias produced.
Try asking
Summarise everything we decided in this project and what is still open.
Pull the code snippets out of this project and put them in one document.
Compare the latest draft in this project with the one from last week.
Questions
- Is a project the same as a folder?
- Closer to a workspace than a folder. It holds conversations as well as files, and Alias reads the whole project as context when you ask something inside it.
- Can I connect a private repository?
- Yes, through the GitHub connector. Alias only ever reads what the account you connected can read, and nothing is written back unless you ask for it.
- What happens to sessions I never file?
- They stay in your recents and remain searchable. Filing one is how you promote it from a passing question into a piece of work you intend to return to.