Joisk
Joisk/Documentation

Joisk documentation

Build with context.
Ship with evidence.

A practical guide to Joisk's browser workspace, Windows Desktop beta, creative Studios, publishing, account usage, and the recovery paths that keep uncertain work from becoming a duplicate.

Open the workspace →Start a projectView usage
New here?

Start with a conversation, then turn the useful part into a saved project.

Read the first-conversation guide →
Already building?

Jump to preview, versions, Studio jobs, publishing, or the account snapshot.

Browse build guides →
Readiness matters.Available, Beta, Partial, and Upcoming labels describe the public boundary. A button or source route alone is not proof that a workflow is ready for every account.

Try “publish”, “usage”, “voice”, or “Windows”. Press Ctrl/⌘ K to focus.

The shortest path: ask a focused question in Chat, move a clear brief into the Builder, inspect the preview, and publish only the version you reviewed.

When an action is still processing or its response is uncertain, use its saved status and the recovery guidance below before submitting it again.

Start here

Available

A first useful session, in one sitting

Joisk is easiest to learn by making one small thing. The workspace, Builder, and Studios share an account context, while the visible controls tell you which actions your current rollout supports.

Ask firstUse Chat to turn a question or rough idea into a clear next step.Build nextGive the Builder a brief and open the first project version.Make an assetCreate one image, clip, sound, or model, then find the saved result.Know how to recoverCheck status before a second submission when a result is slow or unclear.

Before you start

A browser and a Joisk account. Sign in at Sign in when the workspace asks you to save or create.

How to do it

  1. 1Open Chat and start with one concrete question or goal.
  2. 2If the answer becomes a project, open Builder and carry over the brief.
  3. 3Review the result, ask for one focused change, and keep the useful version saved.
Expected visible result
You can see a reply, a project workspace, or a saved Studio result without needing to guess which surface owns it.
If it does not work
If the account or workspace does not load, refresh once after the connection returns. For account-specific failures, capture the visible message and use Help and escalation.

Start here

Available

Start with a conversation

Chat is the broadest entry point: ask, explore, attach context where the UI allows it, and decide whether the next step is an answer, a project, or a creative output.

Before you start

Know what you want to understand or make. A short goal, audience, and desired format are enough; add a reference file only when it helps.

How to do it

  1. 1Open Chat and write the outcome you want, not only the feature name.
  2. 2Include constraints such as audience, tone, device, or a reference format.
  3. 3Read the response, then ask for the next smallest change instead of restarting the whole request.
  4. 4When Joisk offers a Builder or Studio path, follow that visible handoff so the project context stays attached.
Expected visible result
The conversation remains the place to ask the next question. A project or Studio handoff opens with its relevant context when that path is available to your account.
If it does not work
If a reply stops mid-stream or the network drops, wait for the saved status to settle. Do not send the same paid request again until you know whether the first one completed.
Example brief
Create a simple one-page event site for a neighborhood film night. Audience: families and local volunteers. Include: schedule, venue, accessibility note, and a clear RSVP action. Keep the first version calm, readable, and easy to edit.

Start here

Available

Turn a brief into your first website

The Builder creates a project from a plain-language brief. Start small, make the first version visible, and use the conversation to refine it rather than trying to specify every detail up front.

Before you start

A signed-in account and a brief that names the project's purpose. You can also start from a template in Discover when one fits.

How to do it

  1. 1Open Builder and type what the project should help someone do.
  2. 2Choose a project direction when the start screen offers one, or let the brief define it.
  3. 3Press Start building. If sign-in appears, complete it in the inline prompt so the brief can continue.
  4. 4Open the project workspace, inspect the preview, and ask for one targeted change.
Expected visible result
A project workspace opens at its own route with a composer, build status, and preview. Your original brief is not silently discarded during sign-in.
If it does not work
If creation fails, use the visible retry. If the route is unavailable in your rollout, return to Chat and keep the brief there; do not create repeated empty projects.
Attachments at the first prompt are for reference. The Builder currently accepts common image files and text/code files such as .png, .jpg, .webp, .gif, .txt, .md, .csv, .json, .html, .css, and .js through its visible file control.

Start here

Available

Make one creative asset

Use a focused Studio request, then treat the saved result as the source of truth. The Studio history and owner library are more reliable than a browser tab that happened to stay open.

Before you start

A signed-in project context when the Studio asks for one, plus a clear prompt. Decide whether you need an image, video, audio, or 3D result before choosing the tool.

How to do it

  1. 1Open Tools and choose the matching Studio.
  2. 2Describe the subject, intended use, and any reference or duration the control requests.
  3. 3Review the tier, format, and visible estimate before starting a generated action.
  4. 4Wait for the result to appear in the Studio history, then preview or download it from there.
Expected visible result
The Studio shows a saved result with a status, preview, or download action. A project-linked asset can be reused from a compatible workspace.
If it does not work
If the result is still processing, refresh its status. If the response is uncertain, follow Generation recovery and avoid a duplicate paid submission.

Build

Available

Write a brief Joisk can act on

A good brief gives Joisk a job, a person, and a boundary. You can refine visual taste later; the first pass should make the intended behavior inspectable.

Before you start

Name the audience, the primary action, and the smallest version that would be useful. Keep private credentials and real personal data out of the brief.

How to do it

  1. 1Start with the outcome: “Help a visitor book a time,” “Help a team track requests,” or “Help a player reach a goal.”
  2. 2Add the key screens or states, the tone, and any references Joisk should follow.
  3. 3Submit the build and watch the visible activity/status surface instead of assuming a request finished.
  4. 4When the first version is ready, use the preview and ask for a focused edit.
Expected visible result
The workspace shows a project version and an inspectable preview. The conversation remains available for the next edit.
If it does not work
If build status is unavailable, refresh the project before starting another run. A missing response is not evidence that no work was accepted.
Example brief
Build a small internal request tracker. People can create a request, assign an owner, set a status, and filter by open or done. Use a quiet navy interface with a clear empty state and keyboard-friendly controls.

Build

Available

Preview, target, and refine

The preview is where you verify the visible result. Use a targeted instruction when one component is wrong, and inspect the proposed change before applying it.

Before you start

A project with a previewable version. If you know the exact element, use the preview selection control; otherwise describe its label and location in Chat.

How to do it

  1. 1Open Preview in the project workspace and check the primary path at the viewport you care about.
  2. 2Click the relevant element when the preview offers click-to-edit, or describe its label and location in Chat.
  3. 3Read the proposed diff or review state before applying the change.
  4. 4Reopen Preview after the edit and check both the changed path and the nearest unaffected path.
Expected visible result
The change is visible in a new or updated project version, and the review surface tells you what was touched.
If it does not work
If the preview is blank or shows a runtime issue, check build status first, then refresh Preview. Use the project's repair action when it is offered; do not hide the failure by publishing.

Build

Available

Use versions as a safety net

Versions separate experimentation from the last reviewed state. Restore an earlier version when a change moves the project in the wrong direction, then inspect before publishing again.

Before you start

A project with at least one saved build. Keep the version that is currently public in mind; private edits do not become public until you publish them.

How to do it

  1. 1Open the project's History or Versions surface.
  2. 2Compare the candidate with the version you last trusted.
  3. 3Restore the earlier version when needed, then reopen its preview.
  4. 4Make the next edit from the restored version and publish only after review.
Expected visible result
A version row identifies what you are viewing, and restoring gives you a known starting point without erasing the history of the experiment.
If it does not work
If history does not load, keep the current project open and retry the read. Do not delete the project to “reset” it; ask support if versions remain unavailable.

Build

Available

Keep assets reusable and owner-scoped

Uploads and generated results live in an account-aware asset library. A project link tells you where an asset is used; an owner-library result can be reused where the target Studio supports it.

Before you start

A signed-in account and, for project-linked assets, the project you want to work in. Use invented or approved fixtures for disposable tests.

How to do it

  1. 1Open the project's Assets panel or the account Assets view.
  2. 2Upload a supported file or create a result in a Studio.
  3. 3Check the asset label and project association before reusing it.
  4. 4Download or place the asset through the visible control; keep the original when an edit is non-destructive.
Expected visible result
The asset appears with a preview or type, a saved key, and a clear project-linked or owner-library state.
If it does not work
If the library is unavailable, retry after the session is ready. If storage is full, delete only an asset you recognize or move to a plan with more storage; do not assume a failed upload was saved.

Create

Available

Choose the Studio by output

Joisk has separate creative surfaces so each result can show the right inputs, job status, preview, and saved-output behavior. Start from the output you need, not from a model name.

ImageSingle images, variants, comparison, and reusable image assets.VideoPrompt or reference-based clips with queued render status.AudioMusic and voiceover with playable saved results.3DSupported 3D assets and model inspection, with scene-editor boundaries called out.
Quality labels such as Pro, Plus, and Ultra are Joisk tiers. The estimate and current account usage view are authoritative; these labels are not promises of a fixed number of outputs.

Create

Available

Generate and reuse an image

Image Studio lets you make a result, compare it with another option, download it, and carry it into compatible project contexts.

Before you start

A signed-in project context and a prompt. Use a reference asset only when you have permission to use it.

How to do it

  1. 1Open Joisk Image and describe the subject, composition, and intended use.
  2. 2Choose the visible quality tier and review the estimate before generating.
  3. 3Compare saved results, select the one you want, and use its preview or download action.
  4. 4Reuse it from the project or account asset library when the destination supports that type.
Expected visible result
A generated image appears in history with a preview and an owner-scoped asset reference. Cached results can be identified by the Studio's saved state.
If it does not work
If generation fails or the session expires, read the visible error and sign in again if asked. If the request might have started, refresh history before trying another generation.

Create

Available

Follow a video render from queued to ready

Video generation is asynchronous. The important path is submit → status → saved result, not a browser tab that appears to wait forever.

Before you start

A signed-in project, a prompt or supported reference input, and the duration, resolution, and aspect choices the Studio exposes.

How to do it

  1. 1Open Joisk Video and choose text, image, or reference mode.
  2. 2Set the duration, resolution, aspect, and optional camera treatment.
  3. 3Review the estimate and submit once. Watch for Queued, Rendering, Finalizing, and Ready.
  4. 4When the job is Ready, preview or download the saved video from the render history.
Expected visible result
The render history keeps the job and its status. A ready job exposes a saved result URL or download action.
If it does not work
If status is unavailable or the response is lost, refresh the render history. Do not submit a second paid render until the first job is resolved; an uncertain outcome requires reconciliation.

Create

Beta

Edit local media in Video Editor

Video Editor is a local-first beta surface for assembling media on a multi-track timeline. Keep the source files you import; the editor is not a replacement for your originals.

Before you start

Local source media you are allowed to edit. The editor can use local videos, images, audio, and project context; cloud generation is a separate action.

How to do it

  1. 1Open Video Editor and import the local source files you need.
  2. 2Place clips on tracks, trim the in/out points, and adjust the visible audio controls.
  3. 3Play the sequence through the important transition and check captions or text overlays.
  4. 4Save the edit or export through the control the beta surface makes available.
Expected visible result
The timeline shows the imported media and non-destructive changes. The source files remain available on your device.
If it does not work
If browser storage or a local source is unavailable, keep the source file and reopen the project after the browser is healthy. Do not delete the local media to clear an editor error.

Create

Available

Make music or voiceover

Audio Studio separates music and voice modes so the prompt, duration, and playback controls match the output you want.

Before you start

A signed-in project, a short description of the sound, and a duration when the selected mode asks for one. Use a voice or likeness only with the required consent.

How to do it

  1. 1Open Joisk Audio and choose Music or Voice.
  2. 2Describe the sound and set the duration or voice controls the mode provides.
  3. 3Review the tier and estimate, then generate once.
  4. 4Play the saved result, select it for reuse, or download it from the Studio history.
Expected visible result
A playable audio result appears with its mode, prompt, and owner-scoped asset reference.
If it does not work
If playback or the library fails, refresh the saved history and check the connection. If the generation response is uncertain, reconcile its status before submitting again.

Create

Partial

Create a supported 3D asset

3D asset generation and inspection are available in the 3D surface. The separate Engine 2 scene editor is not described here as a generally available workflow.

Before you start

A signed-in project and a clear description of the object or asset. Check the output type shown by the current Studio before planning a scene around it.

How to do it

  1. 1Open Joisk 3D and describe the model or asset you need.
  2. 2Review the visible quality tier and any input requirements before starting.
  3. 3Inspect the saved model result and confirm its asset type before reusing it.
  4. 4Attach it only through a compatible project or Studio control.
Expected visible result
The Studio shows a saved 3D asset or a clear job state. A compatible destination can select it from the owner library.
If it does not work
If a scene-editor control is not visible, treat that capability as unavailable in your rollout. Keep the generated asset and use the visible 3D asset path rather than guessing an Engine 2 URL.

Create

Partial

Games are still in development

Joisk has game routes and an evolving game-building surface, but the complete game workflow is not represented as generally available in this documentation.

Do not plan a release around an unverified game feature. Leaderboards, cloud saves, multiplayer, in-game purchases, store distribution, and full 2D/3D parity require a current rollout and acceptance evidence. A visible Games button is not enough.
  • Safe to say: game projects and a browser game surface exist in the product, and the Builder can offer game starting points.
  • Check first: the current account's Builder or Game Studio controls, the visible save/play path, and the release owner's readiness for any specialist feature.
  • Not promised here: a finished multiplayer backend, game marketplace, or native store package.

Publish

Available

Review before you publish

Publishing makes a chosen project version public. Treat review as a boundary: a private edit should stay private until you deliberately publish it.

Before you start

A previewable project version, an intentional public audience, and a check that you are not including secrets, personal data, or unapproved media.

How to do it

  1. 1Open Review or the publish control in the project workspace.
  2. 2Check the main path, empty states, links, forms, mobile layout, and visible content.
  3. 3Resolve any security, content, or readiness warning the review surface shows.
  4. 4Publish the reviewed version and copy the resulting public link only after it is visible.
Expected visible result
The published URL opens the version you reviewed. Later private edits remain private until you publish again.
If it does not work
If publishing is blocked, read the named capability or content reason and fix that issue first. Do not repeatedly submit a blocked release or treat a staging candidate as public.

Publish

Available

Share with Discover and your public profile

Discover and public profiles are for intentionally shared work. A project does not need a Joisk-run marketplace to be useful or discoverable.

Before you start

A published project and a decision about whether it should be public. Remove private notes and test data before sharing.

How to do it

  1. 1Open Published and choose the project you want to share.
  2. 2Use the visible Discover or profile action and review the preview of the public card.
  3. 3Open the public link in a signed-out or private window to verify what a visitor sees.
  4. 4Update the project and republish when you need the public version to change.
Expected visible result
A visitor can open the public project or your public profile without seeing private workspace history.
If it does not work
If a link shows an older version, confirm which version was published and republish deliberately. If a project should not be public, remove its public sharing through the visible account/project control and verify again signed out.

Publish

Partial

Connect a domain only when the account offers it

Custom domain connection can be plan- and rollout-gated. The Account → Domains panel is the source of truth for the DNS target, verification state, and supported actions.

Before you start

A published site and an eligible account. Do not change DNS until Joisk shows the exact records for your domain.

How to do it

  1. 1Open Account → Domains.
  2. 2Add the domain and select the published site the panel offers.
  3. 3Copy the shown CNAME or verification TXT records to your registrar.
  4. 4Return to Joisk and choose Verify; wait for the certificate/status result before switching traffic.
Expected visible result
The domain row shows Pending, Verified, or a specific setup error. A verified domain can expose the retarget/version controls the account supports.
If it does not work
If Domains is absent, it is not enabled for the account; use the Joisk-hosted public link. If verification is pending, wait and retry the read rather than changing records repeatedly.

Publish

Partial

Use a payment account you control

A project can use your own payment account through a project-scoped Stripe connection when that option is enabled, or through a provider-hosted checkout link. Neither path is the Joisk marketplace.

Before you start

Your own payment-provider account. Confirm its merchant, processing, tax, refund, marketplace, and payout terms before publishing a Buy action.

How to do it

  1. 1In the Builder, ask JoiskBot to “set up payments” or open Add-ons → Payments.
  2. 2If Connect Stripe is available, choose this project's test or live environment and finish Stripe's connection page. Otherwise paste an https checkout link from your provider.
  3. 3Review the button label, price copy, destination URL, and what the buyer receives.
  4. 4Publish only after a safe test confirms checkout and, for a Stripe connection, the expected webhook fulfillment. A connected status by itself is not proof of fulfillment.
Expected visible result
Buyers pay your provider. Your provider controls processing, tax, refund, marketplace, and payout fees; Joisk never holds or routes those payments.
If it does not work
If a provider response or charge is uncertain, check the provider and the Joisk project payment status before retrying. Never create a duplicate paid checkout just because the browser returned an error.
A pasted checkout link can't unlock paid content inside your app on its own because it does not report verified payment back to Joisk. Deliver that purchase through your provider, such as a download, email, or invite.
Project payment links are separate from Joisk subscription billing. The Joisk launch lineup is Starter $9, Plus $27, Pro $97, and Studio $197 USD per month before tax, and remains unavailable until checkout and entitlements are activated together.

Publish

Partial

Export source and understand installability

Joisk-hosted publishing and source export are separate choices. A public web link or installable web app is not the same thing as a store-approved native application.

Before you start

A project with a saved version. If you are exporting for another host, verify any runtime, asset, and environment requirements before leaving Joisk.

How to do it

  1. 1Open the project settings or export control.
  2. 2Choose Export and download the source package when the action is available.
  3. 3Keep the downloaded source and its version information together.
  4. 4For phone access, share the published web link or use the browser's Add to Home Screen / Install action where supported.
Expected visible result
You receive a source download or a web install path. The live Joisk URL remains versioned independently of your local copy.
If it does not work
If export is unavailable, verify that the project has a saved version and that the session is still valid. Do not infer native store availability from an export button.

Across devices

Available

Use the browser workspace as the default

The browser is the primary public surface for Chat, Builder, creative Studios, account controls, and published links. Responsive layouts can change which panels are visible.

  • Chat: use /chat for conversations and context handoffs.
  • Build: use /builder for a new project and /builder/projects for the project list.
  • Studios: use /tools to choose image, video, audio, or 3D.
  • Account: use /account for projects, assets, usage, billing, domains, and settings.
On a phone, open the main navigation button to reach Products, Help, sign-in, and the workspace. The documentation navigation has its own collapsible menu below this header.

Across devices

Beta

Windows Desktop is a beta surface

Joisk Desktop lets you choose a local project folder and review actions that affect it. It is a separate client: its controls and release state can differ from the browser workspace.

Before you start

A supported Windows beta package from the official Download page, a folder you choose, and a signed-in Joisk account.

How to do it

  1. 1Install the current Windows package from Download; check the version shown there.
  2. 2Open or start a conversation, then choose the project folder when the app asks.
  3. 3Read each proposed local action. Commands such as dependency installation, tests, or builds require the app's approval control.
  4. 4Open the preview when it appears and return to the conversation for the next change.
Expected visible result
The app shows the selected folder, a conversation, visible activity, and a preview when files are ready. The local source stays in the folder you selected.
If it does not work
If an action is still running, check its receipt/status before starting it again. If the app cannot connect, keep the folder intact, restart the app once, and use browser Chat while support investigates.

Inside the Windows beta

Your first steps in Joisk Desktop

An annotated view of the desktop app. Choose a step to find the control.

Watch the 25-second tour

Silent, captioned screenshot tour of the Windows beta.

Joisk Desktop Windows beta with conversation navigation, message box, Choose a folder, and Preview controls

Windows beta screenshot. The web workspace and upcoming mobile apps may look different.

Annotated Desktop screenshots and the silent tour are approved fixture material. They illustrate controls; they are not a recording of a successful founder build or proof of hosted/native acceptance.

Across devices

Upcoming

Native mobile clients are not general availability

Published Joisk web projects can be opened on phones and may be installable as web apps. Separate Android and iOS clients, store submissions, and their feature parity have their own release gates.

  • Today: share a published web URL and use the phone browser's install/Add to Home Screen action when the browser offers it.
  • Coming separately: native Android and iOS packages, store availability, and platform-specific feature acceptance.
  • Do not assume parity: a feature working in browser or Windows Desktop is not evidence that the mobile package supports it.
Use Download for the current artifact and platform message. No public store URL is documented here until a release is actually available.

Account & usage

Available

Sign in, recover, and find your work

Your account is the home base for private projects, assets, publishing, usage, billing, and settings. Account data is owner-scoped; a signed-out visitor should not see another creator's work.

Before you start

The email or Google sign-in method you used for the account. Never send a password, reset link, token, or private key to support.

How to do it

  1. 1Open Sign in and use the account method you recognize.
  2. 2If you need a password reset, use the visible reset path and return through the normal sign-in page.
  3. 3Open Account and choose Projects, Assets, Published, Plans & usage, Billing, Domains, or Settings.
  4. 4Sign out before handing the browser or a shared test device to someone else.
Expected visible result
The account header identifies the signed-in account and the selected panel loads only that account's data.
If it does not work
If the account page is blank, refresh after the session resolves. If a second account appears to inherit the first account's data, stop and report it immediately; do not continue browsing.

Account & usage

Available

Read Usage for your weekly allowance

The account Usage view is the authoritative reading for your weekly, cost-backed AI allowance, consumption, reservations, reset state, and infrastructure. The old Credits URL remains a compatibility explanation for historical records.

Before you start

A signed-in account and a connection to the Joisk server. If the server cannot return a current snapshot, treat the state as unavailable rather than zero.

How to do it

  1. 1Open Account → Plans & usage.
  2. 2Check the current plan, weekly window, category quantities, active operations, and the server-confirmed reset time.
  3. 3Read infrastructure separately from AI usage; storage, bandwidth, email, database, compute, and build measurements are not interchangeable.
  4. 4Use the visible refresh or reconciliation action when the panel says a result is pending.
Expected visible result
The Usage panel shows an account-scoped snapshot with available, used, and reserved quantities, plus a reset/overage state when the server provides one.
If it does not work
If Usage is unavailable, refresh once and contact support if it persists. Never treat a blank or stale reading as permission to spend, and never replay a paid operation to “make the balance update.”
The legacy Credits page explains historical transactions. Those balances do not refill the weekly Usage window, though some existing generation routes still consult the separate legacy ledger while their migration continues.
Credit-pack checkout is retired. When a reset is offered, it is a one-time premium purchase that replaces the current weekly AI allowance and requires explicit consent: Free $2, Starter $3, Plus $9, Pro $30, or Studio $60 USD. It does not stack. A completed premium reset starts a fresh seven-day allowance immediately; the regular weekly rollover remains governed by the server's natural reset. Joisk never starts an AI overage charge automatically. Usage shows the current price, eligibility, and monthly cap; unavailable pricing means no reset is offered.

Account & usage

Partial

Plans and billing

The launch lineup is monthly USD pricing, while checkout and entitlements remain gated until the full billing path is verified. Existing subscribers keep their current terms until a separately verified migration.

Before you start

Know whether you are a new account or an existing subscriber. Use the signed-in Billing panel for current subscription status, period end, and payment-method actions.

How to do it

  1. 1Read Plans & pricing for the Starter $9, Plus $27, Pro $97, and Studio $197 monthly lineup and its current checkout status.
  2. 2For an active subscription, open Account → Billing and choose the visible management action.
  3. 3Confirm the price, currency, interval, renewal, and failure state in the account or provider portal before changing anything.
  4. 4Keep included weekly AI allowance, one-time AI resets, and infrastructure resources separate. Infrastructure overages require explicit opt-in, a saved payment method, and a spending limit; AI never bills automatically.
Expected visible result
The account shows the terms that apply to you. The public plan preview does not silently enroll a free account or migrate an existing subscriber.
If it does not work
If a payment, renewal, or checkout result is uncertain, keep the operation visible and reconcile it through the account/provider status. Do not start a second subscription or assume a refund.
The launch lineup is Starter $9, Plus $27, Pro $97, and Studio $197 USD per month before tax. Checkout, entitlements, allowances, and migration must activate together before these plans become a public offer; the current preview does not take payment.

Account & usage

Partial

Watch storage and hosting separately

Asset storage and published-site delivery are different meters. Storage can be a hard cap; infrastructure overages are separate and require explicit opt-in when your account supports them.

  • Storage: open the account Billing/usage surfaces and read the used-versus-included meter before uploading more.
  • Hosting delivery: read bandwidth used, included, forecast, and overage state as a separate resource.
  • Infrastructure extras: enable them only after reviewing the displayed rate, saving a payment method, and choosing a spending limit.
  • When full: keep a local copy, remove only recognized assets, or use the plan action the account provides.
If a usage meter is unavailable, Joisk does not infer zero, unlimited, or free. Refresh the read and wait for a server-confirmed value.

Connect

Partial

Connect only what the account exposes

Optional connectors have their own scopes, secrets, and rollout gates. The supported public guidance here is intentionally narrow: GitHub sync and bring-your-own provider keys.

Before you start

An account you own and the minimum token or key scope shown by the connection UI. A provider subscription is not the same thing as an API key.

How to do it

  1. 1Open the account Settings/connection panel and read the purpose and scope before connecting.
  2. 2Use a fine-grained token or key created for this integration; never paste a production secret into a prompt or support message.
  3. 3Confirm the connected status, then perform only the Push/Pull/Test action you intended.
  4. 4Disconnect from the same panel when you no longer need the integration; revoke the token at its provider too.
Expected visible result
The account shows a connected identity or a clear unavailable/error state. Secrets are not returned to the browser after saving.
If it does not work
A 401 usually means the token is invalid or expired; a 503 can mean the connector is disabled. Fix the provider credential or wait for the rollout instead of pasting a second secret repeatedly.
GitHub syncPush source to your own repository or pull it back as a new project version when the connector is enabled.Bring your own keyUse a provider key you control when the account exposes BYOK; that provider's bill is separate from Joisk usage.

Connect

Upcoming

The API and MCP surface is a preview

The developer route is useful for exploring programmatic workflows, but internal API paths and preview tools are not a stable public contract.

  • Use the preview: read Developer / MCP when it is available in your rollout.
  • Do not depend on internals: routes under /api can be account-gated, rollout-gated, or changed without a public API guarantee.
  • Keep writes explicit: an automated client must preserve the same authorization, readiness, usage, and recovery boundaries as the browser.
No public API reference or stability promise is represented by this documentation page. Use the visible developer preview and wait for a versioned contract before building a production integration.

Reference

Available

Formats the current UI commonly shows

These are the common extensions exposed by current controls. The picker or upload control on the surface you are using remains authoritative for size, duration, and exact support.

SurfaceCommon formatsWhat to check
First Builder attachment.png, .jpg, .jpeg, .webp, .gif, text/code filesUse the visible file picker; keep private data out.
Video assets.mp4, .webm, .movCheck mode, duration, resolution, and reference limits.
Audio assets.mp3, .wav, .ogg, .m4a, .flacCheck the selected Music or Voice mode.
3D assetsUse the supported 3D picker and inspector.Do not assume every model extension or scene editor is available.
When a file is rejected, preserve the original and read the exact control message. Do not rename an unsupported file extension to bypass validation.

Reference

Available

Shortcuts that keep you moving

Keyboard paths are intentionally small and predictable. Controls can vary between browser Chat, Builder, Studios, and Windows Desktop.

ShortcutWhereAction
EnterBuilder promptStart the build when the prompt has content.
Shift + EnterBuilder promptAdd a newline without submitting.
Ctrl/⌘ + KThis documentationFocus the docs search.
EscapeWindows Desktop betaStop or cancel a supported in-progress action when the app shows that behavior.

Reference

Available

Words Joisk uses

A shared vocabulary makes status and recovery easier to read.

TermMeaning
ProjectThe account-scoped workspace that holds a brief, versions, preview, and compatible assets.
VersionA saved project state. Publishing pins a chosen version until you publish another.
AssetAn uploaded or generated file with an owner-scoped saved reference.
JobA work request such as a video render that can move through queued, processing, ready, or failed states.
ReservationUsage held for work in progress. It is not the same as completed consumption.
ReconciliationChecking the durable outcome after a response or provider result was uncertain; it is not an automatic replay.
InfrastructureResources such as storage, bandwidth, email, database, compute, or build delivery measured separately from AI usage.

Troubleshooting

Available

When a result is slow, missing, or uncertain

The safest recovery path is symptom → status → one bounded action → escalation. A lost browser response is not proof that the server did nothing.

Before you start

The project or Studio surface that started the action. Keep any visible request, job, operation, or receipt identifier.

How to do it

  1. 1Read the current status in the original conversation, project, render history, or account Usage panel.
  2. 2Refresh the status or saved history once if the connection has recovered.
  3. 3If the status is ready, use the saved output. If it is failed, read the reason. If it is uncertain, stop and reconcile.
  4. 4Escalate with the visible timestamp and identifier when the bounded recovery does not resolve the state.
Expected visible result
You either use the saved result, see a clear failure that can be corrected, or have a support-ready record of an unresolved operation.
If it does not work
Do not automatically replay a paid generation, payment, reset, upload, or publish request while its outcome is unknown. If the UI says “reconciling,” leave it there and contact support when instructed.
Video still processingFollow Queued → Rendering → Finalizing → Ready in the render history.Usage will not loadRefresh the authoritative snapshot; unavailable is not zero.An edit made things worseCompare and restore a known version, then preview it.Nothing resolves itSend a safe, minimal escalation with what you observed.

Troubleshooting

Available

Help and escalation

Support is most useful when it can reproduce the symptom without receiving your secrets or private content.

Before you start

The route or Studio name, what you expected, what you saw, and the approximate time. Use a marked fixture or disposable account for reproduction where possible.

How to do it

  1. 1Check the relevant guide and retry only the safe, bounded recovery it describes.
  2. 2Open Help for guided topics or Contact for a person.
  3. 3Include the visible error, request/job/operation ID, browser or app version, and whether the result was ready, failed, or uncertain.
  4. 4Leave out passwords, reset links, tokens, private keys, payment numbers, personal documents, and unredacted private conversations.
Expected visible result
The Joisk team can identify the affected surface and choose a safe next check without asking you to repeat a potentially paid action.
If it does not work
For a security issue, stop the affected journey and use Security. If another account's data appears, do not explore further or attach it to a ticket.
Documentation reviewed against local source and fixture evidence on September 15, 2026. Hosted acceptance, native-device acceptance, paid generation, and production deployment are separate release evidence and are not implied by this page.

Missing a guide or found a mismatch? Tell the Joisk team.