Create a Pen
A Pen keeps related chats, project instructions and workspace access together. Use one for a codebase, a writing project or a research topic.
Set up the project
- Choose Pens in the sidebar and create a Pen. Give it a recognisable name and colour.
- Add a brief and instructions describing the work. For example: “Write concise Australian English. Preserve the existing visual design.” These become context for chats in the Pen.
- Bind the intended workspace folder, or deliberately create a new one. Review the folder path before using tools. An empty folder is valid.
- Use the Pen’s New Chat action or + button to focus its composer. Select a model, write a request and send it. The saved chat is created on first send, rather than on every click of New Chat.
- Review any permission request before a file change or command runs.
The Pen’s Workspace tab contains its folder, Git status, instructions, additional files and skills. Additional files are references; they are not automatically injected as full chat context. App-managed brief and agent-guide names do not mean matching README or AGENTS files exist in the workspace.
Return to your work
The Pens overview supports Grid/List, search and sorting. Open a Pen to continue its chats or inspect its settings. Folder and Git status describe the local workspace; they do not mean GOAT has pushed anything to a remote repository.
Change access deliberately
File and command grants have separate controls on the Pen page. A grant for the whole Pen can affect existing and future chats. Changing the workspace clears its file grants; moving a chat clears its chat-only file grant. See Manage permissions before broadening access.
Memory is configured separately in the Pen’s Memory tab. It uses the Pen’s selected scope, not an automatic merge with Global memory. See Memory and Pens.