Why this exists

Pomodoro timers interrupt your flow. Calendar blocks get ignored. The best time to step away from your editor is a moving target that depends on the weather, the time of day, your streak, and what you're in the middle of — none of which a dumb interval timer knows.

Your AI coding agent already knows when you hit a natural pause. It finished the feature. It's waiting for you to answer a question. The tests went green. That's the right moment to nudge — not every 25 minutes on the dot.

touch-grass turns your agent into a context-aware break buddy. A SessionStart hook feeds it live weather and sunset timing at the top of every session. A skill teaches it tiger-mom tone (warm, specific, never preachy). An MCP server lets it log when you actually went outside. You keep your flow. It keeps you honest.

What it does

Like a Pomodoro timer, but it knows the weather, your sunset time, and your coding streak — and it talks to your AI agent instead of interrupting you.

• SessionStart hook injects live weather, sunset timing, and streak state into your agent's context every time a Claude Code session starts.
• MCP server exposes four tools your agent (Claude Code, Cursor, Claude Desktop, Codex) can call on demand.
• Skill teaches the agent when to nudge, when to stay quiet, and what tone to use (tiger mom, not preachy).

It's a Claude Code pomodoro replacement for people who'd rather have their coding agent tell them to go outside than have a screen-blocking timer break their flow.

Install

Claude Code (full experience — hook + MCP + skill):

/plugin install nalediym/touch-grass

That's it. Open a new session — the hook fires, the context drops in, your agent takes it from there.

git clone https://github.com/nalediym/touch-grass
cd touch-grass/plugin/mcp-server && npm install

{
  "mcpServers": {
    "touch-grass": {
      "command": "node",
      "args": ["/absolute/path/to/touch-grass/plugin/mcp-server/index.mjs"]
    }
  }
}

How it works

flowchart LR
  A[Claude Code<br/>session starts] --> B[SessionStart hook fires]
  B --> C[ip-api.com<br/>location]
  B --> D[open-meteo.com<br/>weather + sunset]
  B --> E[~/.touch-grass/state.json<br/>streak + sessions]
  C --> F[Context injection]
  D --> F
  E --> F
  F --> G[Agent<br/>decides when to nudge]
  G -.calls.-> H[MCP tools]
  H --> E

On session start, a hook script runs. It detects your location from your public IP (cached 24h), fetches current weather and sunset time from open-meteo, reads your local streak file, and synthesises a short context block for the agent. The agent reads it, sits on it, and at a natural pause — feature done, bug fixed, waiting for input — nudges you outside with language that matches the actual conditions.

When you confirm you went outside, the agent calls log_touch_grass via the MCP server, which increments your streak in the local state file.

MCP tools

All four are callable from any MCP-compatible agent. In Claude Code, the agent mostly uses them via the context the hook injects — you rarely need to call them manually.

Example prompts

The plugin works ambiently, but these phrasings work well if you want to bring it up yourself:

• "Should I touch grass right now?"
• "What's my streak?"
• "Remind me to go outside before sunset."
• "I just went for a walk, log it."
• "Is it nice out?"

Privacy

Everything is local-first.

• Stored on your machine: ~/.touch-grass/state.json (streak, session counts, last touched date) and ~/.touch-grass/config.json (cached location, weather threshold).
• Leaves your machine: your public IP is sent to ip-api.com once every 24 hours to resolve city coordinates, and those coordinates are sent to api.open-meteo.com on each session start to get weather and sunset.
• Never leaves your machine: your streak, your activity notes, your coding schedule, your prompts, anything from your Claude Code session.

No accounts. No API keys. No telemetry. No analytics. No auth. If you want to disable network access entirely, pin "location" manually in ~/.touch-grass/config.json and the IP lookup never fires.

Configuration

{
  "location": {
    "lat": 40.7128,
    "lon": -74.0060,
    "city": "New York",
    "timezone": "America/New_York",
    "fetchedAt": 9999999999999
  },
  "niceWeatherThresholdC": 15,
  "breakIntervalHours": 2,
  "enabled": true,
  "customActivities": [
    { "label": "walk to the corner store", "emoji": "🛒" },
    { "label": "sit on the fire escape", "emoji": "🪜" }
  ]
}

Troubleshooting

node plugin/hooks/session-start.mjs

{
  "location": {
    "lat": 40.7128,
    "lon": -74.0060,
    "city": "New York",
    "timezone": "America/New_York",
    "fetchedAt": 9999999999999
  }
}

/plugin uninstall touch-grass
rm -rf ~/.touch-grass

Development

git clone https://github.com/nalediym/touch-grass
cd touch-grass/plugin/mcp-server && npm install

# Test the hook directly (outputs JSON context)
node ../hooks/session-start.mjs

# Test the MCP server with the inspector
npx @modelcontextprotocol/inspector node ./index.mjs

Three moving parts:

• plugin/hooks/session-start.mjs — zero-dep Node script. Called by Claude Code on session start. Outputs JSON to stdout.
• plugin/mcp-server/index.mjs — MCP server. Uses @modelcontextprotocol/sdk. stdio transport.
• plugin/lib/grass.mjs and plugin/lib/nudge.mjs — shared logic (weather, sunset, state, nudge text).

The hook and the MCP server read from the same state file, so they stay in sync.

Related

• Claude Code plugin docs
• Model Context Protocol
• open-meteo.com — free, keyless weather API
• ip-api.com — free, keyless IP geolocation

License

MIT · Built in the shade.

Support

touch-grass is free and MIT-licensed. If it's helped you step away from the screen, consider supporting it:

Support on Polar → — $9 one-time. Your name goes in the supporters list, you get priority issues, and you unlock custom activity lists in config.

Supporters

Be the first. Support on Polar →