VelonLabs

Skip to content
velonlabs
.dev
EN
…

FiveM development. Step by step.

Your server. Part of your workflow.

Go from an existing resource to its next improvement without manually moving every version of your files. Connect your Linux or Windows server over SSH, open your FiveM project in a workspace and work on its code with AI.

What you can do

Your server supplies the starting point. Edit a separate workspace copy, review the changes and confirm the transfer back. Import, editing and sync become one clear workflow.

Connect your server in Agent Mode

Connect Linux or Windows directly.

Choose “Server” in the Agent Mode source selector. Enter the host, SSH port and a dedicated project user. Windows requires an active OpenSSH Server. Compare the host fingerprint, then select the detected FiveM folder or enter your project path manually.

Work on the project before it goes live.

Import creates a workspace copy of your code and supported UI files. Analyse resources, edit configurations and develop changes with the agent. The saved workspace is available for your next session; reopening it does not copy the server again each time.

Send reviewed changes back.

Sync checks current server files before transferring only the changed files. Conflicts require a fresh decision. Original files are backed up on your server and the last deployment can be rolled back, keeping the move from edited code to server under your control.

For your next task

Improve a server config. See the difference.

Connect your test server, import the garage and update its parking slots in the workspace. Review the diff, test the change and confirm sync. If you need the previous files again, roll back the last deployment.

Check before moving on

  • Use a dedicated SSH user with access to the project folder
  • Enable OpenSSH Server on Windows
  • Check the host fingerprint and detected FiveM path
  • Read the file changes and any conflicts before syncing

Scope and limitations

Server connections are available from Starter. Connecting, discovery and import use no AI credits; Agent tasks use the normal credits. Root and Administrator cannot be used as project users. Video, audio, GTA stream assets, logs, caches and databases stay on the server. File backups do not replace a full server or database backup.

Current plans and conditions →

Common questions

Does this work with Windows and Linux?

Yes. Both connect over SSH; Windows needs an active OpenSSH Server. Your user needs access to the FiveM project folder.

Does AI edit my live files directly?

Editing starts in a separate workspace copy. Only a confirmed deployment writes the intended changes back to the server.

What if files on the server have changed?

Sync detects conflicts. You can cancel or explicitly confirm replacement after reviewing the changes. Further server changes require another review.

Can I undo the last deployment?

Yes. Original versions of affected files are backed up on your server. The last deployment can be rolled back; this is not a full server backup.

For your next step

01

Create FiveM scripts with AI

Plan and create FiveM Lua scripts with VelonLabs. ESX, QBCore, Qbox and Standalone: turn a specific request into editable source code.

See workflow and examples →02

Debug FiveM scripts

Upload FiveM resources and investigate Lua errors with context. VelonLabs helps analyse problems, revise code and compare script versions.

See workflow and examples →03

FiveM Config Editor for Lua, JSON, YAML, TOML & INI

Edit supported FiveM configurations visually and in source view. Review values, understand the structure and download changed files as ZIP.

See workflow and examples →04

FiveM NUI preview

Review FiveM NUI interfaces in the VelonLabs browser preview. Check layouts, appearance and supported interactions before testing in game.

See workflow and examples →05

FiveM Agent Mode

Structure larger FiveM tasks with VelonLabs Agent Mode. Connect your brief, plan, file changes and result review in one development workflow.

See workflow and examples →06

Project knowledge & notes for your FiveM workflow

Keep framework context, project instructions and notes in one place. Organise FiveM knowledge for recurring development tasks with VelonLabs.

See workflow and examples →07

GitHub integration for FiveM

Connect GitHub to VelonLabs.dev. Work on FiveM resources in Agent Mode, review file changes and deliberately sync them back to your repository.

See workflow and examples →08

FiveM teamwork

Build FiveM resources together. Invite members to VelonLabs.dev, share workspaces and repositories, and assign Viewer or Editor roles.

See workflow and examples →10

Create FiveM assets with AI and browser editors

Start with an AI chat prompt, then edit vehicles, clothes, characters, props and textures in the relevant VelonLabs editor.

See workflow and examples →11

FiveM Blueprints

Scripts from the VelonLabs Store come with a personal blueprint. In AI chat or Agent Mode it becomes a new script built to your project rules.

See workflow and examples →12

FiveM Workspace

In the VelonLabs Workspace you connect AI chats, agent tasks, notes, editor projects and blueprints on one board, edit files and work as a team.

See workflow and examples →13

VelonLabs Control

Bring scripts from AI chat and exports from the editors to your FiveM server over SSH, start resources and test in game without copying files by hand.

See workflow and examples →

Your project. Your next step.

Describe your idea or upload an existing resource. Continue working on the source code and test the result on your server.

Open AI chat →