> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/open-safe-private-secure/open-data-workflow-file-storage.md).

# Open Data, Workflow, File Storage

All Your Documents (and Metadata and Settings) Are Belong to You!

### Open Source App

Nimbalyst itself is open source. The full source code is published at [github.com/nimbalyst](https://github.com/nimbalyst) so you can audit how your files, sessions, and settings are handled, build your own version, or contribute back.

### Open Storage of Content and Status in Markdown

<div align="left"><figure><img src="/files/azMYwJsCZCe6pDgVpoqk" alt="" width="375"><figcaption></figcaption></figure></div>

* **Human-readable format**: All plans, documents, tasks, and status tracking use standard markdown files
* **Version control ready**: Plain text files work seamlessly with Git for history and collaboration
* **YAML frontmatter**: Structured metadata stored as YAML at the top of markdown files
* **No proprietary formats**: Edit your files with any text editor, never locked into a specific tool
* **Transparent tracking**: Plan status, progress, and metadata all visible and editable in the markdown source

### Open Storage of Workflow and Config in Coding Agent Commands

<div align="left"><figure><img src="/files/OesaQjOm0jvh1biTx18s" alt="" width="375"><figcaption></figcaption></figure></div>

* **Slash commands**: Custom workflows stored in `.claude/commands/` directory as markdown files
* **Project instructions**: Repository-specific guidance in `CLAUDE.md` checked into your codebase
* **Local configuration**: Settings and preferences stored in standard application directories
* **Portable workflows**: Share your custom commands and workflows by committing them to version control
* **No vendor lock-in**: All configuration uses open standards and readable formats

### Open Storage of Your Files in Your File Tree or Github

<div align="left"><figure><img src="/files/SC3pOrW6MG8YgsAN2fAg" alt=""><figcaption></figcaption></figure></div>

* **File system first**: Local documents are stored directly in your local file system
* **Optional team workspace**: Files explicitly promoted to Nimbalyst Teams gain a shared copy that flows through Cloudflare encrypted in transit and at rest
* **Git integration**: Full support for Git version control and GitHub synchronization
* **Your choice of sync**: Use GitHub, GitLab, Bitbucket, or any Git hosting service you prefer
* **Standard file structure**: Local project content stays in files and folders you control
* **Backup friendly**: Standard file storage works with any backup solution

### Open Storage of your Images

A link to your images is stored in your markdown file

Your image is stored in your project in the .nimbalyst/assets folder


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nimbalyst.com/open-safe-private-secure/open-data-workflow-file-storage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
