Working with files
How Giga creates, edits, displays, and keeps work product connected to the right place.
Giga can create and edit work product such as documents, code, webpages, reports, and other files. In web Chat, supported visual work can be shown directly in the viewer; in Slack, generated files are uploaded back into the Chat.
Files in a Chat
When a task produces a file, Giga should return it through the supported surface rather than pointing you to an internal path.
- In Giga Web, files and visual artifacts can be shown in the viewer when supported.
- In Slack, generated files, charts, screenshots, and exports are uploaded as actual files.
- For long-running work, files can live with the relevant Track so they remain part of that body of work.
Where should information live?
| Need | Best fit |
|---|---|
| A short plan, note, or narrative artifact | Markdown file |
| A report, draft, code file, or other work product | File in the relevant Track |
| Structured records that will grow and be filtered or aggregated | Database |
| Durable context about ongoing work | Track context and memory |
Video placeholder
Files overview video.
Files are work product
Standing context, memory, and current Track state are separate concepts, even when they relate to the same work.
Related pages
Was this page helpful?