How VibeCraft works

The SourceCraft repository is the main source of the project's relevant code and securely saved changes. VibeCraft works with a project using the SourceCraft Spaces remote runtime connected to the project. It holds the repository's working copy the agent uses. The same runtime is used to run the application and generate its preview version.

Processing a task

  1. Before starting a task, VibeCraft updates the working copy to the current state of the target branch.
  2. The agent changes files and runs checks and the application. It uses the Docker Compose configuration from the project to run the application.
  3. After successfully completing the task, the agent creates a commit and sends the result to SourceCraft.

Warning

The result is only considered securely saved if it appears in the SourceCraft repository. Changes left only in the remote runtime may be lost when updating the working copy, as well as after an error, task stop, or when exceeding the execution timeout.

Restrictions and possible issues

Task is complete within 30 minutes

If the agent failed to complete the task within 30 minutes, the result may not be pushed to SourceCraft.

Tip

Break a large task into several subtasks and, after completing each subtask, check its commit in the repository.

Why the agent may overlook a new commit

If you pushed the changes to the repository yourself, write about it in the VibeCraft chat. Specify the commit or changed files the agent should process. Changes only existing in the remote runtime's working copy are not available in the chat.

Changing files in parallel may result in a conflict

Warning

Do not change the same files in the target branch while the agent is implementing the task. Otherwise, you may get a conflict when sending the result, and the agent's changes will not be pushed to SourceCraft. You cannot restore partial changes from the remote runtime.

If a conflict occurred, re-implement the task after making sure the target branch includes all the required changes.

Stopping a task does not ensure a save or rollback

To stop an active task, under the developer section, click Stop.

Warning

It will stop the task implementation, but will not ensure saving a partial result, creating a commit, or rolling the project back.

How to safely work in VibeCraft and via Git at the same time

  1. Before starting a task, push all the required changes to SourceCraft.
  2. Write about the commit you added in the VibeCraft chat.
  3. Do not change the same files in the target branch while the agent is implementing the task.
  4. After completion, make sure the final commit appears in SourceCraft.
  5. Store all the important data in the repository or external storage rather than only in the remote runtime.

If your final commit is missing in SourceCraft, check if the execution timeout has expired and the target branch has been changed in parallel. Then push your current changes to the repository, write about them to the agent in the chat, and re-implement the task.

Technical features

VibeCraft uses the following SourceCraft and Yandex Cloud components:

Note

When associating your own domain a Yandex API Gateway is also created. If the domain management is delegated to Yandex Cloud DNS, a DNS zone and resource records are created as well.

You can manage Yandex Cloud resources from the SourceCraft repository via a secure service connection.

Useful links