update docs

Author: binary-husky

ajet/utils/vsdb.py

@@ -3,74 +3,22 @@
 
 """
 Ray Distributed Debugger VSCode Extension (Recommended)
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-1. Starting with Ray 2.39, Anyscale has introduced the `Ray Distributed Debugger <https://docs.ray.io/en/latest/ray-observability/ray-distributed-debugger.html>`_ VSCode extension. Follow the extension’s installation instructions, then add your cluster using the dashboard URL you obtained earlier.
+Starting with Ray 2.39, Anyscale has introduced the
+`Ray Distributed Debugger <https://docs.ray.io/en/latest/ray-observability/ray-distributed-debugger.html>`_ VSCode extension.
 
-   .. image:: https://github.com/eric-haibin-lin/verl-community/blob/main/docs/ray/debugger.png?raw=true
-      :alt: Ray Distributed Debugger VSCode extension screenshot
+1. Install the Ray Distributed Debugger extension in VSCode.
 
-2. Prerequisites.
+2. In AgentJet project:
 
-   Ensure the following are installed (see the extension README for more detail):
+   2-1. In the place your want to set a conditional breakpoint, write
+         `from ajet import bp; bp("TAG_1")`
 
-   - Visual Studio Code
-   - `ray[default]` >= 2.9.1
-   - `debugpy` >= 1.8.0
+   2-2. When launching the training process, add `--debug` argument
+         `ajet --conf your_config.yaml --debug="TAG_1"`
 
-   .. image:: https://github.com/aoshen524/verl/blob/main/docs/start/c7098b755ff689859837773a916c857.png?raw=true
-      :alt: VSCode with Ray prerequisites
+   2-3. Open Tab "Ray Distributed Debugger" in VSCode, and just wait until the breakpoint is hit.
 
-3. Environment Variables.
-
-   To enable post‑mortem debugging, set:
-
-   .. code-block:: bash
-
-      export RAY_DEBUG_POST_MORTEM=1
-
-   .. admonition:: Note
-      :class: important
-
-      Be sure to remove any legacy flags before starting Ray:
-
-      - `RAY_DEBUG=legacy`
-      - `--ray-debugger-external`
-
-4. Configuring BreakpointsSet up breakpoint() in your code, and submit job to cluster. Then the extension will show the breakpoint information.
-
-
-   1. Insert `breakpoint()` calls into your remote functions.
-   2. Submit your job to the cluster.
-
-   The extension will detect active breakpoints and display them in VSCode.
-
-   .. image:: https://github.com/aoshen524/verl/blob/main/docs/start/4ddad74395c79a1402331c0ce73316f.png?raw=true
-      :alt: Detected breakpoint in VSCode
-
-   **Note:** Breakpoints are only supported inside functions decorated with `@ray.remote`.
-
-5. Launching the Debugger.
-
-   Run your job directly from the command line (do not use a `launch.json`):
-
-   .. code-block:: bash
-
-      python job.py
-
-6. Attaching to a Breakpoint.
-
- Once the process hits the first `breakpoint()`, click the Ray Distributed Debugger icon in the VSCode sidebar to attach the debugger.
-
-   .. image:: https://github.com/aoshen524/verl/blob/main/docs/start/4ddad74395c79a1402331c0ce73316f.png?raw=true
-      :alt: Attaching VSCode debugger to Ray process
-
-7. Debugging With Multiple breakpoint().
-
-   For each subsequent task, first disconnect the current debugger session, then click the extension icon again to attach to the next breakpoint.
-
-   .. image:: https://github.com/aoshen524/verl/blob/main/docs/start/6e83c910a62c82fecb89c6619e001cd.png?raw=true
-      :alt: Disconnecting and reconnecting the debugger
 """
 
 def vscode_conditional_breakpoint(tag=None, once=True):