How the agent uses JRebel¶
When the application is running with JRebel attached, the agent uses the running instance as its primary feedback loop. Instead of packaging and restarting the application after each change, the agent compiles the affected code, waits for JRebel to reload the change, and verifies the result in the running application.
Tip
For the underlying public skill reference, see workflow.md.
When the skill is configured correctly, the agent should:
Change only the files needed for the task.
Run the smallest compile step that validates the change.
Wait for the running application to load the update.
Verify the result by checking the live application (for example, via an HTTP request).
Repeat the workflow until the change is complete.
Important
For this workflow, compiling is the normal validation step. Packaging and full restarts are not included.
Use the workflow