Repository navigation
โ๐๐ ๐ผ๐ป๐น๐ ๐ณ๐ฎ๐ถ๐น๐ ๐๐ถ๐๐ต ๐๐ต๐ถ๐ ๐ผ๐ป๐ฒ ๐ผ๐ฟ๐ฑ๐ฒ๐ฟ.โ
Thatโs the kind of Spring Boot bug I want an AI agent to help investigate.
The source code is available. The failing input, live bean state, and SQL behind that request often take more work to uncover.
Today Iโm sharing fully updated ๐ฆ๐ฝ๐ฟ๐ถ๐ป๐ด ๐๐ผ๐ผ๐ ๐ฅ๐๐ฃ๐ ๐ณ๐ผ๐ฟ ๐๐ป๐๐ฒ๐น๐น๐ถ๐ โ a work in progress that brings interactive exploration inspired by Lisp to running Spring Boot applications, with ๐ ๐๐ฃ ๐ฎ๐ฐ๐ฐ๐ฒ๐๐ ๐ณ๐ผ๐ฟ ๐๐ ๐ฎ๐ด๐ฒ๐ป๐๐.
The workflow Iโm building around:
๐๐ฎ๐ฝ๐๐๐ฟ๐ฒ ๐ฎ ๐ณ๐ฎ๐ถ๐น๐ถ๐ป๐ด ๐ฐ๐ฎ๐น๐น โ ๐ฟ๐ฒ๐ฝ๐ฟ๐ผ๐ฑ๐๐ฐ๐ฒ ๐ถ๐ โ ๐ฐ๐ต๐ฎ๐ป๐ด๐ฒ ๐๐ต๐ฒ ๐ฐ๐ผ๐ฑ๐ฒ โ ๐๐ฒ๐ฟ๐ถ๐ณ๐ ๐๐ต๐ฒ ๐ณ๐ถ๐ โ ๐ธ๐ฒ๐ฒ๐ฝ ๐๐ต๐ฒ ๐๐ฒ๐๐.
๐ธ ๐ฆ๐๐ฎ๐ฟ๐ ๐๐ถ๐๐ต ๐๐ต๐ฒ ๐ถ๐ป๐ฝ๐๐ ๐๐ต๐ฎ๐ ๐ฎ๐ฐ๐๐๐ฎ๐น๐น๐ ๐ณ๐ฎ๐ถ๐น๐ฒ๐ฑ.
Capture method inputs and outcomes as DATA snapshots. Inspect the saved data and create variations to explore edge cases.
๐ ๐๐ถ๐๐ฒ ๐๐ต๐ฒ ๐ฎ๐ด๐ฒ๐ป๐ ๐ฎ ๐ฟ๐ฒ๐ฝ๐ฒ๐ฎ๐๐ฎ๐ฏ๐น๐ฒ ๐ฒ๐ ๐ฝ๐ฒ๐ฟ๐ถ๐บ๐ฒ๐ป๐.
Through MCP, Claude or Codex can inspect Spring beans, run permitted Java snippets, and use saved test cases (CASEs) to check expected behavior.
๐ ๐๐ผ๐น๐น๐ผ๐ ๐๐ต๐ฒ ๐ฒ๐๐ถ๐ฑ๐ฒ๐ป๐ฐ๐ฒ ๐ถ๐ป๐๐ผ ๐๐ต๐ฒ ๐ฑ๐ฎ๐๐ฎ๐ฏ๐ฎ๐๐ฒ.
Recorded calls, SQL activity, and Hibernate data help investigate unnecessary queries and potential N+1 problems.
๐งช ๐๐ฒ๐ฒ๐ฝ ๐๐ต๐ฒ ๐ถ๐ป๐๐ฒ๐๐๐ถ๐ด๐ฎ๐๐ถ๐ผ๐ป ๐ฎ๐ ๐ฎ ๐ฟ๐ฒ๐ด๐ฟ๐ฒ๐๐๐ถ๐ผ๐ป ๐๐ฒ๐๐.
Apply supported method-body changes with HotSwap, rerun the case, and export a JUnit test.
For an AI agent, the useful part is the feedback loop: inspect a real example, test a hypothesis, examine the result, and choose the next step.
๐๐๐ฒ๐ฟ๐ ๐ฒ๐ ๐ฝ๐ฒ๐ฟ๐ถ๐บ๐ฒ๐ป๐ ๐ฝ๐ฟ๐ผ๐๐ถ๐ฑ๐ฒ๐ ๐ป๐ฒ๐ ๐ฒ๐๐ถ๐ฑ๐ฒ๐ป๐ฐ๐ฒ ๐ณ๐ผ๐ฟ ๐๐ต๐ฒ ๐ป๐ฒ๐ ๐ ๐ฑ๐ฒ๐ฐ๐ถ๐๐ถ๐ผ๐ป.
๐ ๐โ๐๐ฒ ๐ฎ๐๐๐ฎ๐ฐ๐ต๐ฒ๐ฑ ๐๐ต๐ฒ ๐๐ป๐ด๐น๐ถ๐๐ต ๐ฃ๐๐ ๐ด๐๐ถ๐ฑ๐ฒ with setup instructions, UI walkthroughs, and MCP usage.
Iโd love feedback from Java developers