Skip to main content
Iris surfaces its findings directly in the editor so you never have to leave your code to understand what needs fixing. Inline Code Lens hints flag problems above the functions they affect, the status bar keeps the current file’s health score always visible, and the detachable panel expands the full analysis into its own editor column when you need more room.

​
Code Lens

Iris adds inline hints above functions that exceed the configured length threshold, and next to specific debug-print patterns. The hints are language-aware so you only see signals that are relevant to the file you are editing.
LanguageWhat gets flagged
TypeScript / JavaScriptEvery @ts-ignore comment and every console.log / console.warn / console.error call
Gofmt.Print* and log.* debug print calls
Pythonprint() calls
Here is an example of how a Code Lens hint looks above a TypeScript function with leftover console.log calls: 
// payment.ts

const stripe = new Stripe(process.env.KEY!);

// Iris · console.log left in · 2 occurrences
export async function processPayment(amount: number) {
  console.log("processing:", amount);
  const charge = await stripe.charges.create({
    amount, currency: 'usd'
  });
  console.log("charge id:", charge.id);
  return charge;
}
To turn off Code Lens hints, add the following to your VS Code settings: 
{
  "iris.enableCodeLens": false
}

​
Status Bar

The Iris status bar item appears at the bottom of the VS Code window and shows three live metrics for the active file: health score, line count, and function count. The item changes colour when the health score or complexity rating crosses a warning or error threshold — giving you an ambient signal that something in the current file needs attention. Here is a typical status bar entry for a TypeScript file with a health score of 64: 
⚠ Iris 64 · 379 lines · 12 fns
The ⚠ icon and yellow/red colouring appear automatically based on the configured thresholds. The status bar works for all supported languages. To turn off the status bar item, add the following to your VS Code settings: 
{
  "iris.enableStatusBar": false
}

​
Detached Panel

Pop Iris out of the narrow sidebar and into a full editor column beside your code. The panel shows the same analysis as the sidebar but with more space — useful when you want to read a full findings breakdown without shrinking your editor.

​
How to open

Click the pop-out icon in the Iris sidebar title bar, or run Iris: Open in Panel from the command palette (Ctrl+Shift+P). Close it the same way to restore the sidebar view.

​
What the panel does

  • Auto-refreshes when you switch files or save — always showing the current file’s analysis
  • Two-column layout at 700 px or wider: file stats on the left, findings on the right; workspace ranked lists go side by side
  • Placeholder in sidebar — while the panel is open, the Iris sidebar shows a placeholder so data is never duplicated across both views
  • Jump-to-line for Pro findings — click any finding to jump straight to that line in the editor
Here is a condensed example of what the panel displays for a file under analysis: 
Iris (Panel) — cancel-order-modal.tsx

Enforcement Snapshot
Needs cleanup before it becomes a gate problem
score 64 · 2 blockers · trend -4

Lines    379    Code  349
Fns       12    Imports  6

Code Smells
  console.log       2
  Magic Numbers     7
  Unused Vars       1
  Unused Fns        0
The detached panel is available on all plans — no Pro subscription is required to use it.