Files & projects
Work with selected material in its existing format. Keep versions, import choices and conflicts understandable.
Zeke’s Computer is the companion workspace being developed around the new ZekeChat. The WebLinux direction brings projects, files, applications and authorized execution into a browser-based desktop.
A research answer can become a source-backed project note. A selected file can become a reviewed edit. A plan can become a bounded task with a result, rather than another message describing what ought to happen.
That is the v1.0 engineering direction. It connects the chat to project state, storage, current permissions and verification. It is not established simply by adding an AI panel to a desktop.
Work with selected material in its existing format. Keep versions, import choices and conflicts understandable.
Use a permitted tool or runner for the defined action, with bounded inputs, current authority and cancellation.
Preserve drafts and partial work. Resume uncertain operations carefully instead of replaying every effect after a crash.
Separate a durable reminder from AI execution. A scheduled request still needs an available executor and current scope.
The design calls for server-enforced grants, revocation checks and version fences. Model output cannot grant itself authority or accept its own result. These are implementation requirements; protocol prose alone cannot enforce them.
| Environment | Role | Boundary |
|---|---|---|
| ChatGPT Dot’s computer | The OpenAI-provided environment used by a Dot. | Governed by OpenAI’s capabilities, account settings and permissions. |
| Zeke’s Computer | The independent browser workspace being built. | Its own implementation, storage, connected services and authority model. |
| Authorized runner or sandbox | The place a supported inference or Linux job actually executes. | Must be available, paired or configured, and within the action’s scope. |
It does not mean the browser secretly has a permanent Linux VM, access to your local machine, or every terminal capability. Real Linux jobs and interactive terminals require supported execution backends; simulations must be labelled.
The October v1.0 direction covers shared chat, attachments, research, memory, planning, executor work and durable recovery. The available shared-chat and runner implementation has focused synthetic tests; complete tool execution and end-to-end acceptance remain unfinished in the reviewed snapshot.
No public Computer installer or completed live integration is supplied by this website. Check current releases before treating a capability as available.