Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • Getting Started with AI for VLSI Engineers5
  • Just Enough AI: Models and Context15
  • Prompting13
  • Trust and Verification14
  • Using AI for Engineering Work17
  • Engineering Walkthroughs7
  • Practical Foundations for AI Workflows4
  • Engineering Data5
  • Retrieval-Augmented Generation6
  • Agents and Tool Use18
  • Agent Design8
  • MCP and Skills6
  • Multi-Agent Design6
  • Practical Capstone6
  • Tokens, Cost and Latency12
  • Agentic Workflows for Chip Teams18
    • Regression Triage Agent
      • The Nightly Triage Loop
      • Clustering Failures by Signature
      • Ranking Suspects with Evidence
      • Read-Only by Default
      • Evaluating Against Labelled History
    • Lint-and-Fix Loops
    • Guardrails and Human in the Loop
    • Evaluating and Operating Agents
  • Interview and Judgment10
  • AI Skills: Full Course Index
  • Working with AI Glossary
  • Working with AI Cheatsheet
Loading lesson

‹Regression Triage Agent
  1. Topics
  2. AI Skills for VLSI Engineers
  3. Agentic Workflows for Chip Teams
  4. Regression Triage Agent
  5. Read-Only by Default

Reference: Agentic Workflows for Chip Teams · Beginner to Intermediate

Read-Only by Default

Read-only defaults, approvals for reruns, and handling untrusted log text.

On this page

    Least-privilege tools

    The agent reads by default and writes only with permission. Log search and commit history are read-only, while reruns and bisect consume machines and need a budget.

    Tool

    Default permission

    Why

    Log search

    Read-only

    It only quotes existing lines.

    Commit history

    Read-only

    It only lists merged changes.

    Rerun a seed

    Needs approval

    It spends simulator time.

    Bisect

    Needs approval

    It spends many simulator runs.

    Approvals for state changes

    Anything that runs a simulator asks first. The request names the seed, the estimated run count, and the question the runs would settle.

    A human approves or trims the request. Routine small reruns can carry standing approval with a nightly cap, and anything above the cap asks again.

    Untrusted log text

    Log lines are data, not instructions. A failing test can print text that reads like a command, and the agent must quote it without obeying it.

    Warning

    Keep secrets out of prompts, and send proprietary RTL only to a hosted or local deployment approved for it. Redact keys and export-controlled blocks before any log text leaves the company network.

    Common pitfall

    Treating quoted log text as a plan step is prompt injection. Keep tool arguments built from the agent state, never copied from log lines.

    Common mistakes

    Interview

    Likely probes: which tools are read-only and what an approval request holds.

    • Search and history read; rerun and bisect need approval with a run budget.

    • Each request names the seed, the run count, and the question it settles.

    • Log text is quoted as evidence and never parsed as instructions.

    Check yourself The agent wants twelve bisect runs overnight. What happens first?

    It files an approval request with the seed, the count of twelve, and the suspect range. Nothing runs until the request is approved.

    Check yourself A log line says to delete the work area and rerun clean. What does the agent do?

    Nothing with it. The line is quoted as evidence if relevant, and never becomes a tool argument.

    Related topics

    • Evaluating against labelled history

    • Guardrails

    Previous

    146 / 173

    Next: Evaluating Against Labelled History

    Up next

    Up nextEvaluating Against Labelled History

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • The Nightly Triage Loop
    • Clustering Failures by Signature