Skip to content

Creatives Kit / Windows x64

Agents, assets and outputs. One workspace.

Work with coding agents in Project Chat, arrange media on a board and follow jobs from engine to output on Windows.

Agent accounts, API usage and compute cost extra.

Project Chat, Media Board and Explorer
Actual interface with demo data. Chat, machine statistics and jobs are synthetic, not a live provider session.

FROM CONTEXT TO OUTPUT

Start with a project. Follow every step.

  1. 01

    Open a project

    Choose a folder and gather the assets you need.

  2. 02

    Work with an agent

    Bring context into Project Chat through your own coding CLI.

  3. 03

    Follow the work

    Agents submit media work through MCP; check the queue and status.

  4. 04

    Review the result

    Open your media, inspect it and choose the next step.

PROJECT CHAT

Keep the conversation beside the work.

Projects have their own chat tabs and history. Choose a coding agent, model and configuration, read its explanation and follow tool activity inside the workspace.

Explorer opens a folder tree and file previews so you can check context. Switch to Terminal when you need the command line. Agents use installed CLIs and your sign-in; you control file-editing permissions.

See your assets. Keep their context.

The Media Board canvas and tree share your selected folder. Choose light, dark or system appearance.

Media Board, Project Chat and Explorer in light mode

Actual interface with demo data. Chat, machine statistics and jobs are synthetic, not a live provider session.

View original image

Arrange and compare

Move and resize media on the canvas. Select a file to locate it in the tree; use Storage boards and Moodboards for assets and references.

Inspect before deciding

Preview images, play video or audio and open detailed inspection in the desktop app. Local editing tools preserve originals; file edits by a coding agent follow the separate permissions you grant.

Know where work stands and which engines are ready.

Jobs from queue to result

Actual interface with demo data. Chat, machine statistics and jobs are synthetic, not a live provider session.

View original image

Jobs from queue to result

Follow queued, running, succeeded or failed work in the console. Review results and errors before continuing.

Configure your chosen services

Actual interface with demo data. Chat, machine statistics and jobs are synthetic, not a live provider session.

View original image

Configure your chosen services

See enabled engines, models and missing dependencies. Bring your own accounts and check setup before submitting work.

Have your own engine? Start with Add your Engines.
Add your Engines dialog with a demo brief

Actual interface with demo data. Chat, machine statistics and jobs are synthetic, not a live provider session.

View original image

Describe an engine or provide its repository to prepare the adapter structure and input/output checks. Review its source and trust before installation. This onboarding flow does not require editing or rebuilding Creatives Kit.

New engines are installed disabled. Configure your account and check provider usage rights before enabling one; adapter checks are not security or commercial-rights certification.

Your workspace. Your accounts.

Use Windows x64 and follow the release setup guide. Install and sign in to your chosen coding CLI; setup only offers Antigravity when Claude Code, Codex and Antigravity are absent.

You can choose a runtime drive other than C by following setup guidance. The app price excludes API usage, compute and agent subscriptions; cloud engines receive the inputs you submit for their jobs.

APP ACCESS

Start in your Creatives Kit library.

Sign in to check trial eligibility and downloads available to your account. Review pricing and terms before choosing paid access.

Free trial · 0 VND

  • No card needed for a free trial
  • One PC, with device transfer support
  • API usage, compute and agent subscriptions cost extra

Common questions

What is Project Chat for?

It is an interface for coding agents through CLIs installed on your machine, using your own sign-in. Agents can read and edit files with your permission; media jobs go through MCP to configured engines.

Do I need to use a terminal?

Project Chat is the default workspace mode. Switch to Terminal when you need your familiar command-line workflow. Your coding CLI still needs to be installed and signed in.

Does the product price include AI usage?

No. API usage, compute, quotas and coding-agent subscriptions are separate costs, depending on your chosen services. You manage your accounts and connection details.

Where are my files processed?

The board browses media in local folders. Cloud engines receive the inputs you submit for their jobs. Review engine settings and agent permissions before running work; not every operation is offline.

Can I add my own engine?

Add your Engines helps prepare, check and install an adapter. New engines are installed disabled; review the source and configure your account before enabling one. Adapter checks do not grant provider access or usage rights.

Where do I download the app and manage access?

Open the Creatives Kit library to check trial eligibility and releases available to your account. A license covers one PC, with transfer and recovery support. Your saved files remain yours after expiry.

Begin with your project.