Run context
Keep an artifact connected to the build and step that produced it.
Product capability · build resources
Review and download available Xcode Cloud build artifacts.
Artifacts make more sense when they stay attached to the build and step that produced them. Tazuki keeps that relationship visible while respecting provider availability.
See how it worksWhat it is
A contextual view of available build artifacts.
Build Detail can expose artifact name, file type, size when the provider supplies it, and a path to request a download. Tazuki refreshes short-lived provider URLs when needed; App Store Connect remains the source that decides whether the artifact is available.
At a glance
The useful shape of this capability.
On demand
Request a download when an artifact is available instead of assuming a permanent local copy.
Provider-led
Respect the availability, metadata, and short-lived URLs supplied by the source.
Attached to the run
Keep Xcode Cloud artifacts tied to the build and step that produced them.
An artifact is more useful when you can answer which build and step produced it. Tazuki keeps that resource in the same context as the run rather than presenting it as an unrelated file list.
- Build and step relationship
- Artifact name and type when supplied
- Size when supplied by the provider
Request a download
Request an artifact download when the provider still makes it available.
The artifact flow is request-based. Tazuki can refresh a short-lived provider URL and ask the source for a current download path when the underlying artifact remains available.
- Short-lived URL refresh
- On-demand download request
- Provider availability check
Clear expectations
Treat artifacts as provider-backed resources, not permanent local archives.
Tazuki helps you find an available artifact in the build context. It is not a permanent artifact vault, and it cannot make an expired or unavailable provider resource available again.
- Contextual resource view
- No automatic permanent backup
- Source availability remains decisive
A useful boundary
Artifact context is not permanent artifact storage.
Tazuki can display and request available artifacts through provider-supplied URLs. It does not claim to archive every artifact forever or override App Store Connect and Xcode Cloud availability.
- No permanent artifact backup promise
- No guarantee every artifact remains downloadable
- No replacement for provider storage and retention
Questions, answered
A capability with clear edges.
How do I download Xcode Cloud build artifacts in Tazuki?
When a synchronized artifact is still available from the provider, Tazuki can request a current download URL and keep the artifact connected to the build and step that produced it.
What are Xcode Cloud artifacts in Tazuki?
They are provider-supplied files associated with a build or step, shown in the build context when they are available to Tazuki.
Does Tazuki permanently back up artifacts?
No. Tazuki can show or request an available artifact download, but it does not promise that all artifacts are permanently stored locally.
Why can an artifact download stop working?
Artifact URLs are short-lived provider URLs and may need to be refreshed. App Store Connect and Xcode Cloud availability still determine whether a download can be made.
Tazuki · macOS 14+
Keep the useful context close.
Tazuki is available on the Mac App Store. Download it free and unlock remote synchronization with Pro.
Download on the Mac App Store