SessionStart

SessionStart is a hook for Claude Code from microsoft/intelligent-terminal. Its token cost is not measured, scanned A, original, MIT.

A startup hook that runs a shell command when an agent session begins. It checks whether the Windows Terminal command-line tool is available and reports the session start if it is.

In plain words
What is it for?
Starting session checks and sending session-start events to Windows Terminal's agent integration.
Why use it?
It lets the terminal tool notice new agent sessions automatically without manual setup each time.

Hook for Claude Code ✓ vendor

Written for Claude Code: SessionStart hook event.

Part of the wt-agent-hooks plugin — 7 hooks shipped together

One of 7 entries in hooks.json upstream. Installing this one merges just its entry into your config; the other 6 are separate, each on its own page.

Good fit Starting session checks and sending session-start events to Windows Terminal's agent integration.

Compare 6 hooks from other repositories ↓
Install with agentmods
npx agentmods add hooks/microsoft/intelligent-terminal/session-start
About the project

Intelligent Terminal is an experimental fork of Windows Terminal that adds native support for AI agents through the Agent Client Protocol. It is for Windows users who want to manage compatible agent command-line tools alongside terminal tabs, profiles, themes, shells, and keyboard shortcuts, and the catalogue entries provide instructions, skills, hooks, and a plugin for working with it.

microsoft/intelligent-terminal · 2,056 stars · on GitHub · devblogs.microsoft.com

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/microsoft/intelligent-terminal

Made for: Claude Code.

Or install wt-agent-hooks, the plugin that ships this one along with the rest of its 7 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for SessionStart

README.md
[![agentmods](https://agentmods.dev/badge/hooks/microsoft/intelligent-terminal/session-start/github.svg)](https://agentmods.dev/hooks/microsoft/intelligent-terminal/session-start)
Your own site
<a href="https://agentmods.dev/hooks/microsoft/intelligent-terminal/session-start"><img src="https://agentmods.dev/badge/hooks/microsoft/intelligent-terminal/session-start/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for SessionStart

Your own site · 80×15
<a href="https://agentmods.dev/hooks/microsoft/intelligent-terminal/session-start"><img src="https://agentmods.dev/badge/hooks/microsoft/intelligent-terminal/session-start.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

SessionStart scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

tools/wta/wt-agent-hooks/claude/wt-agent-hooks/hooks/hooks.json · 14 lines

What it actually says

{
  "SessionStart": [
    {
      "matcher": ".*",
      "hooks": [
        {
          "type": "command",
          "command": "command -v wtcli.exe >/dev/null 2>&1 && wtcli.exe agent-hook --cli-source claude --event agent.session.start; exit 0",
          "shell": "bash"
        }
      ]
    }
  ]
}
Same file

What else hooks.json configures

This page is one entry in a file that holds 7. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 14 lines scan A 7916a11889e4

Subscribe to this mod's changes

SessionStart is a hook published in the GitHub repository microsoft/intelligent-terminal (2,056 stars, last pushed today), licensed MIT. Its token cost is not measured: a hook is shell that never enters the context. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.