Skip to content

CQLS HPC Agent Terms of Use

Version 1.0 | Oregon State University | 2026-11-19


1. About the service

The CQLS HPC agent service lets AI agents work for you on the CQLS HPC cluster. A harness is the program that runs an AI agent. It sends text to a model and runs the tool calls that the model asks for. Claude Code, Codex and pi are harnesses. The hpcagent command starts a harness in a sandbox on a cluster host, and it adds tools and skills from CQLS. In a session, the sandbox and these tools are part of the harness. For each session it fetches a key for the CQLS AI Gateway, and it mints GitLab project tokens for the projects that you grant to the session. These terms call this "the service".

Oregon State University (OSU) operates the service through the Center for Quantitative Life Sciences (CQLS). The language models are open-weight models that run on CQLS servers. The service does not send your prompts, files, or command output to a commercial AI provider. Section 7 gives the one exception: the web search tool.

The service is in beta. Features change without notice, and the service is sometimes unavailable. Models are added and removed as hardware permits.

For keys that hpcagent fetches and tokens that hpcagent mints, these terms are the complete terms. The CQLS AI Gateway Terms of Service govern the chat site and the keys from the key page. When you use such a key for agent work, these terms also apply.

2. Accepting these terms

You accept these terms with hpcagent gateway enroll on a cluster host. The command shows these terms, asks you to type yes, and asks for your ONID password. Declining costs you nothing except access, and you may enroll later.

The service records your username, the version of these terms, and the time of your enrollment.

OSU will revise these terms as the service develops. When a new version takes effect, your key stops until you run hpcagent gateway enroll again and accept the new version.

3. Your agents act as you

An agent in your session works with your account. Each command that it runs, each file that it changes, and each git push and merge request that it makes is your action. You are responsible for it as if you did it yourself.

The same applies to work that an agent prepares and that you run, for example a Slurm job script that you submit. It also applies when you run an agent outside the hpcagent sandbox. OSU does not support that use, and these terms still apply to it.

Review the work of an agent before you rely on it, publish it, or merge it. Do not give an agent a task that you are not allowed to do yourself.

4. Fair use of HPC resources

Agents and Slurm. In an hpcagent session, an agent can read the state of Slurm through a fixed set of read-only commands (sacct, squeue, sinfo, hqstat, hqavail and hqinfo), at a limited rate. It can check a job with hqsub --check, which submits nothing. An agent cannot submit, change, or cancel a job. You decide which jobs to run, and you submit them yourself, outside the session. Do not give an agent a way to submit jobs, for example a program outside the session that submits what the agent writes.

Many people share the CQLS HPC cluster. Use it fairly:

  • Follow the CQLS cluster policies and the rules of each queue.
  • A Slurm job that you submit is your job, also when an agent wrote it. It counts against your limits and your priority, as every other job does.
  • Do not run heavy work on a login node. Submit it as a Slurm job.
  • Do not hold resources that your agent does not use, for example a GPU or an interactive job that waits for input.
  • Keep within the rate limits of the AI Gateway. Do not work around a limit or a safeguard.

5. CQLS Agentic Coding Policies

The CQLS Agentic Coding Policies are part of these terms: https://docs.hpc.oregonstate.edu/cqls/ai-gateway/agentic-coding-policies/. Follow the version in force. OSU updates the policies separately from these terms. It dates each update and lists the changes at the top of the policies.

The policies hold operational rules for agent work only. OSU makes a change to what the service stores, to who can read it, or to your rights in a new version of these terms, not in the policies.

6. Data that agents send to the models

An agent sends text to the models without asking you before each request. That text includes your instructions, the contents of the files that the agent reads, and the output of the commands that it runs.

The service records each request to a model: the key, the model, the time, the size of the request, and the text of the prompt and the response. OSU keeps these records for 90 days. It uses them to operate the service, to find faults, to enforce these terms, and to plan capacity. The service makes an encrypted backup each night, and OSU keeps backups for 14 days. CQLS system administrators can read the request records. They do so only to operate the service, to investigate a fault or a security event, or to enforce these terms.

The rules below apply to each directory that your session can read, because an agent can send any file in it to a model.

The service is not approved for regulated or confidential data. Do not enter, paste, or upload:

  • protected health information (HIPAA);
  • student education records (FERPA);
  • export-controlled data or Controlled Unclassified Information;
  • data that OSU classifies as confidential, or data under a data use agreement that does not permit this service;
  • passwords, API keys of other services, and other credentials;
  • personal information about other people that they have not agreed to share.

You are responsible for knowing what your data contains. By submitting material you confirm that doing so is consistent with every approval and obligation that governs it, including any IRB protocol, data use agreement, sponsor confidentiality term, or applicable law.

7. The web search tool sends queries outside OSU

The chat site and the API have a web search tool. When a model uses it, the service sends the search query to public search engines, and it fetches the web pages in the results. These requests leave OSU through the campus network. The search engines and the web sites can see the query and the request. Do not use the web search tool for a query that contains sensitive information.

8. Credentials and the sandbox

The service does not write your key to disk on the cluster. Programs in your session hold it in memory, and an agent can read it. The same is true for GitLab tokens. Do not copy a key or a token out of a session, write it to a file, or share it. If you need a key outside a session, for example for a script or another tool, get a separate API key from the key page (https://chat.ceoas.oregonstate.edu/keys).

The service sends your ONID password only to the campus directory service, to confirm your identity. It does not store your password or write it to a log.

The sandbox lowers the risk of agent work. It does not remove it. Do not work around the sandbox. This includes work that your agent does for you. An agent that tries to leave the sandbox, to read a credential that the session does not give it, to submit a Slurm job, or to turn off a control of hpcagent works around the sandbox.

The service can record the tool calls of a session, with the reason that the agent gives for each call. OSU uses these records to improve the service and to find attempts to work around the sandbox. OSU can suspend your access while it investigates an attempt.

9. Model output

Model output can be wrong. A model can state false facts, cite sources that do not exist, and write code that does not work. Check any output before you rely on it, the same way you would check work that a new colleague gave you.

The output is yours to use. OSU claims no ownership of the text and code that the models produce for you. Each model has its own license from its developer. Some licenses set conditions on use. You are responsible for following them.

Follow the rules of your field. Journals, funders, and courses have rules about the use of AI. Follow those rules, and disclose your use of AI where they require it. Students follow the AI policy of each course and the OSU Code of Student Conduct.

10. Usage review

OSU may read the request records, the Slurm accounting records, and the logs of your sessions. It does so to check fair use, to find faults, to improve the service, to find attempts to work around the controls of the service, and to investigate a security event.

11. Revocation

OSU may limit, suspend, or revoke your key, your enrollment, the GitLab tokens that hpcagent minted for you, or your use of hpcagent, at any time, with or without notice. The reason can be capacity or fair use, and not only a breach of these terms.

12. Acceptable use

Use the service for your research, teaching, and OSU work. Specifically:

  • Follow OSU policies on the acceptable use of computing resources.
  • Keep within the rate limits. Do not work around a limit or a safeguard.
  • Use your own account and your own key. Do not share, sell, or transfer access.
  • Do not probe, attack, or overload the service or the systems behind it.
  • Do not use the service to make material that is unlawful, or that harasses or harms other people.
  • Do not use the service for work whose purpose is to cause harm, including biological, chemical, or other weapons information.

OSU may suspend an account or disable a key that it finds outside these terms, and may do so without notice.

13. Retention and public records

OSU is a public university of the State of Oregon, and the Oregon Public Records Law (ORS 192.311 to 192.478) applies to the records it holds. OSU may retain at least one archival copy of material submitted to the service, in accordance with its document retention policies. OSU may keep account records after an account closes. Direct any request to delete data to the address in Section 15. OSU handles such requests at its discretion.

14. No warranty, and limits on liability

OSU provides the service as it is, with no warranty of any kind. No promise attaches to its accuracy, its availability, its fitness for your purpose, or its suitability for publication. Model output may be wrong. The service may be unavailable when you need it. Checking any output you rely on is your responsibility.

To the fullest extent Oregon law allows, OSU is not liable for loss arising from your use of the service, including lost or corrupted data, lost time, or the consequences of any decision made on the basis of its output.

15. Changes to the service, governing law, and contact

OSU may change, suspend, or discontinue the service at any time.

Oregon law governs these terms. Any action arising out of or related to them belongs exclusively in the Circuit Court of Benton County for the State of Oregon, in Corvallis, Oregon, and you consent to that court's jurisdiction and waive any objection to its venue or convenience. If a claim must be brought in a federal forum, it belongs exclusively in the United States District Court for the District of Oregon. OSU retains every defense and immunity available to it, including sovereign immunity, governmental immunity, and immunity under the Eleventh Amendment to the Constitution of the United States.

Send questions about these terms, about your data, or about the service to hpc_support@oregonstate.edu.


CQLS HPC Agent Terms of Use, Version 1.0, 2026-11-19, by Oregon State University.