Terms of use

The rules for using VESPR, the smart development environment (SDE) where people and AI agents work in the same files. VESPR is a prototype today, and these terms are written to say so.

Effective date: [Effective date] · Draft written October 29, 2026

On this page

What these terms cover

These terms cover the hosted VESPR service, the public demo and this website, all run by [Legal entity name] (“we”), [Registered address]. Write to us at [Contact email].

The VESPR source code is separate. It is published under the GNU Affero General Public License v3.0 (AGPL-3.0), and that license, not these terms, governs what you may do with the code, including running your own copy. If someone else runs a VESPR server, these terms do not apply to it.

VESPR is a prototype. Features change, workspaces can be reset, and nothing here promises that the service will be available or that your data will be kept. Keep your own copy of anything you care about. A workspace can be committed and cloned with ordinary git.

Who may use VESPR

By using VESPR you agree to these terms. If you use it for an organization, you confirm you may accept them for it.

You must be at least [minimum age, 13 suggested; confirm with counsel] years old. VESPR is not for children under 13 today. Plans for schools are on Children and schools; none of it is in force yet.

Access and workspaces

Today you get in with an access token or a link from the operator. Keep it private: anyone who has it can act as you. Ordinary accounts with email sign-in and two-step verification are in development and are not part of the demo.

A workspace is shared. Everyone who has access to it can see every file, every chat message and the full session log, and can edit and approve what agents do. Put nothing in a workspace that you are not willing to show those people. Also read Security: anyone with a valid token for a server can currently reach every workspace on that server.

AI agents

Agents are AI helpers that join a workspace like a teammate. They can read and edit files and run commands. How much they may do without asking depends on the permission mode the workspace chose: manual, accept edits, auto, plan or bypass. In the modes that ask, an Approve / Deny card appears for the whole workspace. Anyone in the workspace can answer it, and the first answer decides. You are responsible for what you approve and for the mode you choose.

Your content

You keep ownership of what you put into VESPR. We do not claim it.

You give us, and the providers that help us run the service, a limited license to host, copy, display to the other people in your workspace and process your content (including sending it to the model provider an agent uses), only so we can provide the service you asked for. You confirm you have the right to put the content in.

As between you and us, you own the output an agent produces for you, as far as the law and the model provider’s terms allow. [lawyer to check model provider and open-model license terms on ownership and use of output] We do not use your content to train or fine-tune models.

Acceptable use

Agents run code, so abuse can do real damage. You agree not to:

Commands that run in the agent sandbox share the sandbox’s internet connection. You are responsible for what you and the agents you approve do with it.

We may suspend access, remove content or reset a workspace to protect the service or other people.

Running on your own computer or a teammate’s

A computer can opt in to run jobs for chosen workspaces. Commands then run on that machine, in a temporary folder with time and output limits. Only turn this on for workspaces and people you trust, and only run jobs on a computer whose owner agreed.

Limits and availability

The demo has caps on memory, processes, CPU, upload size and a daily AI token budget. We may change or remove features and limits at any time, take the service down, or reset workspaces. There is no uptime promise and no support promise.

Price and payments

The service is free today. There are no paid plans and we do not collect payment details. Planned If paid plans are introduced, the price, renewal and how to cancel will be shown before you pay.

Our software, name and trademarks

The code is under AGPL-3.0 (see the LICENSE file). The VESPR name and logo are not licensed by the AGPL; they belong to [owner of the name and logo]. Third-party components keep their own licenses, listed in the repository’s THIRD-PARTY file. “VS Code”, “Nebius”, “NVIDIA” and “Nemotron” are trademarks of their owners; VESPR is independent and not affiliated with them.

If you send us feedback, we may use it without owing you anything for it.

No warranty

VESPR is provided “as is” and “as available”, without warranties of any kind, to the extent the law allows. [lawyer to review wording and local consumer-law exceptions]

Limit of liability

To the extent the law allows, we are not liable for indirect or consequential losses, lost data or lost profits, and our total liability for anything related to the service is limited to [amount or formula]. [lawyer to review]

Governing law and disputes

These terms are governed by [governing law]. Disputes go to [courts or arbitration venue]. [lawyer to review, and to add any indemnity or class-action wording if wanted]

Ending access

You can stop using VESPR at any time. We can suspend or end your access if you break these terms or put the service or other people at risk. When access ends, workspace data is handled as described under Privacy. Clone your workspace with git first if you want a copy.

Changes and contact

We may update these terms. If a change matters, we will [how we announce changes] before it takes effect, and the effective date at the top will change. Using VESPR after that means you accept the new terms. Contact: [Contact email]. To report a security problem, see Security.