Description
File and Media Management gives terminal workflows a supported bridge between local files and Dots-managed storage. dots files upload validates local media input and sends the content through the configured API, while dots files sign requests a time-limited access URL for an existing storage object. Media-kind handling keeps file interpretation explicit.
The workflow is designed for operators and coding agents. It uses the same authenticated, company-scoped service contracts as the rest of Dots, so terminal or protocol convenience never creates a second source of truth. Inputs are validated before or at the route boundary, and outputs preserve identifiers and structured details needed for a reliable next step.
Selling Points
- Allows headless agents to attach real files without hand-building multipart requests.
- Keeps uploaded content within the same authenticated company context as its records.
- Uses signed URLs instead of exposing storage buckets or permanent public links.
- Validates media inputs before the network write, producing clearer usage failures.
- Fits file operations into the CLI's standard structured output and error model.
User Story
A research agent uploads a local PDF, captures the returned storage reference, and later signs that object for short-lived downstream access. It can attach the reference to a record without leaking a storage credential or public bucket path. The result is a concrete, inspectable outcome that another person or automation can continue from without reconstructing hidden state.
Extension Surface
The CLI feature is automatable: packages/cli/src/commands/files.ts and packages/cli/src/media-input.ts implement the fixed upload and signing flow. Storage providers are not selected or registered through this command family. The rating reflects the most-open supported seam that is true for this capability, not a transitive implementation detail. The cited path is the operational proof: consumers can use the documented seam, while unsupported changes still require a core release.
Capabilities & Limits
- Capability: Local file upload with media-kind handling.
- Capability: Signed URL issuance for controlled object access.
- Capability: Standard credential, company, error, and formatting behavior.
- Limit: The family does not provide a general file browser, arbitrary bucket administration, or permanent public hosting.
The limit is intentional product truth rather than missing documentation. Calls also remain subject to authentication, tenant selection, schema validation, and the permissions enforced by the authoritative service.
Implementation Map
packages/cli/src/commands/files.tspackages/cli/src/media-input.tsdocs/cli/settings-files-and-human-md-commands.md