VelonLabs

Skip to content
velonlabs
.dev
EN
…

FiveM development. Step by step.

Your repository. Your next step forward.

Your FiveM project does not start from scratch. Connect GitHub directly to VelonLabs.dev and build on the code you already have. Agent Mode brings your task and repository files together, from a focused config fix to an extension of an existing resource.

What you can do

Spend less time moving files and more time building: select a repository, describe a specific task and review the changes in your workspace. You choose which changes go back to GitHub.

Connect GitHub in Agent Mode

Connect GitHub. Choose your project.

Open the source selector in Agent Mode and connect your GitHub account. Authorise the repositories you want to use with the GitHub app, then choose your project. Refresh the list when new repositories become available. It shows approved projects your GitHub account can access.

Build on your existing code.

Describe the change in the context of your resource: framework, affected files and expected behaviour. Extend a garage configuration, investigate an error or revise a NUI. The workspace keeps the files, task and result together, while the diff view shows what changed.

Review, then sync.

Read the changes and test the affected workflows. Publishing creates a separate branch and a pull request in GitHub, where your team can review and merge the result. Editing in the workspace does not automatically write to your main branch. Repository permissions still apply.

For your next task

Turn an existing garage into your next feature.

“Extend the QBCore garage in this repository with configurable parking slots. Keep the existing events and data structure. Then show me the changes to the config, client and server.”

Check before moving on

  • Authorise the repository for the GitHub app
  • Describe your framework and project conventions
  • Review file changes in the diff view
  • Test affected features before publishing

Scope and limitations

A connected GitHub account, appropriate repository permissions and Starter or higher for Agent work are required. Repository limits and available Agent features depend on your plan. GitHub does not replace testing the resource on your FiveM server.

Current plans and conditions →

Common questions

Can I use a private repository?

Yes, when you authorise it for the GitHub app and your connected account has the required permissions. Connecting does not make the repository public.

Are changes published automatically?

Work starts in your workspace. Review the diff, then publish the changes as a pull request. Merging happens in GitHub.

Can my team work on a repository?

Member management supports shared repositories. GitHub identity and repository permissions are checked in addition to the workspace role.

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 →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 →09

Connect your FiveM server

Connect your Linux or Windows FiveM server to VelonLabs.dev. Edit a workspace copy and sync reviewed files with backups and deployment rollback.

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 →