add vscode and agentic connection docs, first go

docs/merlin7/02-connecting-to-merlin/agentic-tools-bridges.md

@@ -0,0 +1,27 @@
+# Agentic Tools and Bridges
+
+!!! note
+    We're still investigate the impact of using AI agents and similar services
+    on the Merlin cluster. The following documentation can change at any time.
+    Please keep an eye on are [news posts](../../news/index.md) or check out
+    out [mailing lists](../../support/introduction.md) to keep up-to-date
+    with latest developments in this space.
+
+!!! danger "BEWARE"
+    You **MUST NOT DISCLOSE OR UPLOAD** data that is no explicitly for public
+    use. AI tools can not distinguish between private and public data, that is
+    **YOUR RESPONSIBILITY**.
+
+AI tools and services are proliferating rapidly, and are becoming easier to
+use.  Tools like ClaudeCode and CoPilot provide a nice way of orchestrating
+agentic tasks and possibly automatic certain actions and operations.  We know
+that some users are interested in using these on a regular basis, and might
+possibly integrate them into their workflows.
+
+Please have a look at some of the guidelines from PSI:
+
+- AIT CoPilot Guide: <https://intranet.psi.ch/en/computing/copilot>, please take
+  note of the data security concerns. **You must not disclose any data or other
+  PSI documentation unless it is explicit marks as 'public'!**
+- PSI AI Initiative (RAG chatbot) documentation: <https://ai.pages.psi.ch/RAG/>
+

docs/merlin7/02-connecting-to-merlin/connecting-with-vscode-remote.md

@@ -0,0 +1,22 @@
+# Visual Studio Code Remote
+
+The Visual Studio Code editor supports ["remote
+development"](https://code.visualstudio.com/docs/remote/remote-overview) over
+SSH.  This lets users develop and run code on remote systems through their
+local installation of VSCode. The "remote" extension will connect to the remote
+machine over SSH and will install and use the VSCode Server service. This
+service runs in the background and keeps the session alive and responsive. It
+will also perform various other tasks, not limited to checking out projects,
+updating search and code indices, and running user issued remote commands (over
+the terminal in VSCode).
+
+Using VSCode Remote is very useful but it can cause issues on remote systems
+that are shared by multiple users, like the login nodes.  Per the [VSCode
+documentation](../07-software-support/vscode.md) we **strongly** ask that **you
+do not connect to the login nodes using VSCode remote** and instead use an
+[interactive SLURM
+session](../07-software-support/vscode.md#vs-code-via-interactive-sessions).
+
+Additionally we provide some
+[Tips](../07-software-support/vscode.md#tips-and-other-suggestions) on
+improving performance and preventing issues to the cluster.

mkdocs.yml

@@ -125,6 +125,9 @@ nav:
         - merlin7/02-connecting-to-merlin/connect-from-macos.md
       - SSH Key-pairs: merlin7/02-connecting-to-merlin/ssh-keys.md
       - Remote Desktop: merlin7/02-connecting-to-merlin/nomachine.md
+      - Other Clients:
+        - merlin7/02-connecting-to-merlin/connecting-with-vscode-remote.md
+        - merlin7/02-connecting-to-merlin/agentic-tools-bridges.md
     - How To Use Merlin7:
       - merlin7/03-how-to-use-merlin/storage.md
       - merlin7/03-how-to-use-merlin/transfer-data.md