Install and sign in
Get the current package from the download page and verify SHA-256. Sign in to the same account on phone and computer; conversations synchronize without device pairing.
Help center
Start with the conversation binding, owning computer availability, and selected AI kernel, then check network and attachments.
Get the current package from the download page and verify SHA-256. Sign in to the same account on phone and computer; conversations synchronize without device pairing.
A new conversation starts unbound. Connect a local project in conversation settings when computer execution is needed, or choose cloud development. Conversation names and binding state synchronize across devices.
A connected project belongs to the computer that created it. Messages from mobile or another computer route to that device; if it is offline, Dibaci does not start Codex on the wrong machine and instead reports that the owning device must come online.
Pasted desktop images begin pre-upload immediately and the sent message references the prepared attachment. Returned images can be previewed and other files downloaded; historical attachments may become unavailable after the retention period.
The model selector in the composer chooses Dibaci, Codex, or another configured kernel for the turn. Tabs in settings configure each kernel rather than duplicating the active choice.
Cloud development is an SVIP entitlement. The user selects cloud development and the backend assigns and locks an isolated environment; no specific cloud computer is selected. Base workspace capacity is 5 GB. A turn is not interrupted when it crosses the limit, but new data is restricted before the next turn until space is cleared.
FAQ
Not for a normal conversation. A conversation connected to a local project needs the owning computer online; cloud development runs in its assigned environment.
Sign in to the same Dibaci account. Conversations sync through the account without separate pairing.
Yes. Credentials remain on the configured device and model requests go directly from that device to the provider; the credentials are not synchronized to Dibaci cloud.
Skill content is composed in the Dibaci cloud for the current turn. To avoid exposing paid skill source to local or third-party kernels, marketplace skills are available only with the Dibaci kernel.
Files return to the conversation where the task started. Desktop and mobile can preview images and download files.
Delete the account from account settings in the app or use the public web entry. The account is disabled immediately and associated cloud data is normally deleted within 30 days.