AI assistants

DRSM ships guide files that teach AI coding assistants its layout, report format and rules, so an admin can ask one to add a host, write a plugin or change the dashboard and get changes that fit. This page shows how to connect GitHub Copilot, Gemini and Claude to an install.

The guide files

File	Read by
`AGENTS.md`	The main guide, read by most assistants
`.github/copilot-instructions.md`	GitHub Copilot
`GEMINI.md`	Gemini CLI and Gemini Code Assist
`CLAUDE.md`	Claude Code
docs/ai/	Task guides: maintain a site, write a plugin, change the dashboard
llms-full.txt	All of it in one file, to paste into a chat

They are in the top folder of the DRSM source. For an install, open the source folder, or copy AGENTS.md and the pointer files to the folder you open (for example the DRSM account's home), so the assistant finds them.

Use approved services only

Host names, addresses, reports and configuration describe your network. Use only AI services your organization has approved, and never paste passwords, tokens or keys. Keep the work on the monitor host, where the assistant reads files instead of you pasting them.

GitHub Copilot in VS Code

Install VS Code with the Remote - SSH and GitHub Copilot extensions, signed in with your organization's Copilot account.
Connect to the monitor host as the DRSM user (Remote-SSH: Connect to Host) and open the DRSM source or home folder.
Copilot Chat reads .github/copilot-instructions.md and AGENTS.md from the open folder. Use agent mode for changes that touch several files.

Gemini CLI or Gemini Code Assist

$ cd ~/git/dr_system_monitor
$ gemini              # reads GEMINI.md, which points to AGENTS.md

Gemini Code Assist in VS Code reads GEMINI.md from the open folder too.

Claude Code

$ cd ~/git/dr_system_monitor
$ claude              # reads CLAUDE.md and AGENTS.md

A chat with no access to the host

Paste llms-full.txt into an approved chat, describe the change, copy back only the code and test it on the host.

Good requests

"Add web2 as a production Linux host with a 90% disk warning, then run it once without alerts."
"Write a plugin in plugins/local that warns when /var/spool/app has more than 500 files, with a test."
"Show the report /opt/scripts/backup_report.txt on the dashboard, stale after 26 hours."
"web3 is Stale since yesterday. Find out why from the logs and cron."
"Post a warning that the mail relay is down until 18:00."

Review the result

Read every change before it is saved. Scripts that change files show a dry run first: check it before --apply.
Run the tests in the source (tests/*.sh) after a code change, and drsm_run.sh -n -H <host> -v after a host change.
Configuration belongs in host, site and config files, not in the DRSM code, so an upgrade keeps it.