Evaluation of AI-Assisted Coding and Computational Research Infrastructure

University of Sheffield

The acceleration of computational research through artificial intelligence has transitioned from an experimental capability to a fundamental requirement for institutional competitiveness. For an institution of the caliber of the University of Sheffield, the deployment of these tools necessitates a rigorous evaluation framework that balances researcher productivity with institutional security.

This report provides a multi-dimensional assessment of thirteen leading AI-assisted coding and research tools, specifically analyzed for their suitability within the University’s ecosystem, including the Stanage and Bessemer HPC clusters and health-related data governance requirements.


1. Comprehensive Profiling of AI Coding Assistants

GitHub Copilot and the Microsoft Ecosystem

GitHub Copilot remains the market-leading AI pair programmer. Its “Agent Mode” is particularly relevant for research, allowing for autonomous task completion across multiple files.

CriterionGitHub Copilot Profile Details
Primary FunctionGeneral-purpose AI pair programming and repository-wide reasoning.
Key AI FeaturesInline completions, Copilot Chat, Agent Mode, and PR summaries.
Languages & EnvironmentsPython, C++, Java, Rust, Go; VS Code, JetBrains, Vim/Neovim.
Licensing & CostFree for verified students/teachers; Business (39/mo).
Data Training PolicyNo training on Business/Enterprise data; code is not persisted.
HPC CompatibilityHigh; integrates with Remote-SSH and code-server on Sheffield nodes.
Catalogue StatusApproved - Recommended Standard

Note: Distinct from Microsoft Copilot (Office 365). GitHub Copilot is a technical tool for the software development lifecycle.

Google Gemini Code Assist and Google Colab

Excels in cloud-native development with a massive 128K-token context window.

CriterionGoogle Gemini & Colab Profile Details
Primary FunctionGemini: Enterprise coding assistant; Colab: Collaborative notebooks.
Data Training PolicyCustomer data and prompts are not used to train shared models.
SSO SupportFully supported via Google Workspace for Education and Cloud IAM.
Catalogue StatusApproved for GCP-heavy research and collaborative teaching.

Cursor and the Challenge of AI-Native IDEs

A fork of VS Code that rebuilds the editor’s core for deep, index-level access.

  • Status: Restricted
  • Risk Profile: Identified vulnerabilities (CVE-2025-54135) and telemetry concerns regarding UK GDPR compliance for sensitive research.

Tabnine and Privacy-First Enterprise Deployment

The premier choice for regulated environments requiring maximum data sovereignty.

CriterionTabnine Profile Details
Primary FunctionPrivacy-centric assistant with VPC/On-premises deployment options.
Data Training PolicyEphemeral processing; code is never stored or used for base models.
HPC CompatibilityHigh; natively supports on-premises deployment on cluster nodes.
Catalogue StatusApproved - Recommended for Sensitive Data projects.

Amazon Q Developer (formerly CodeWhisperer)

Deeply integrated into the AWS ecosystem; includes IP indemnification for Pro tier users.

  • Catalogue Status: Approved for AWS-centric research groups.

JetBrains AI Assistant

Deeply integrated for users of PyCharm, CLion, and IntelliJ IDEA.

  • Key Feature: “Zero Data Retention” (ZDR) policy.
  • Catalogue Status: Approved for researchers using the JetBrains ecosystem.

Continue and Ollama: The Open-Source Stack

The state-of-the-art for private, local AI coding.

CriterionContinue + Ollama Profile Details
Primary FunctionOpen-source bridge (Continue) and local model host (Ollama).
Data Training Policy100% private; no data ever leaves the institutional boundary.
HPC CompatibilityHigh; can be deployed on GPU-enabled worker nodes.
Catalogue StatusRecommended Standard for local-first, private development.

2. Research Infrastructure Integration

HPC Integration (Stanage / Bessemer)

The primary mechanism for enabling these IDEs is the vscoderemote_sheffield_hpc repository, allowing code-server to run on worker nodes.

Standardized Remote Access Workflow:

  1. Preparation: Load modules (code-server/4.16.1 on Stanage).
  2. Security: Generate SSL certificates via setup_ssl_ca_server_client.sh.
  3. Connectivity: Spawn Slurm batch jobs via local scripts.
  4. Resilience: Utilize reconnect_info files for persistent sessions.

Data Governance for Sensitive Research

A decision-making framework based on code/data sensitivity:

Sensitivity TierRecommended Governance ModelApproved Tools
Tier 1: ClinicalAir-gapped / Local-OnlyTabnine (Self-hosted), Ollama
Tier 2: SensitiveEnterprise Cloud + Zero RetentionDeepnote (w/ BAA), Gemini Enterprise
Tier 3: PublicStandard Cloud + Policy ControlGitHub Copilot, Google Colab

3. Recommendations and Catalogue Status

Priority Recommendation Table

ToolRecommended StatusPrimary Rationale
GitHub CopilotRecommended StandardMost mature; free academic tier; robust controls.
Tabnine Ent.Recommended (Sensitive)Only viable solution for air-gapped health research.
Ollama + ContinueRecommended (Local)Zero-cost, high-privacy for individual labs.
Deepnote (Edu)Recommended (Collab)Superior real-time collaboration; free for researchers.
JupyterHubRecommended StandardFundamental for institutional reproducibility.
CursorRestricted ApprovalPermitted for individuals; security risks for scaling.

Priority Implementation List

  1. Immediate Standard: Procure GitHub Copilot Enterprise for all centrally-funded RSE and faculty roles.
  2. Privacy Pathway: Establish a “Sensitive Data Toolkit” centering on Tabnine Enterprise and Ollama for NHS/GDPR Special Category data.
  3. HPC Enhancement: Mainstream the vscoderemote_sheffield_hpc scripts through workshops and dedicate high-VRAM GPU nodes (24GB-48GB) for AI inference.