<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cursor on Shaharia Azam&#39;s Website | DevOps, Platform Engineering &amp; AI Insights</title>
    <link>https://shaharia.com/tags/cursor/</link>
    <description>Recent content in Cursor on Shaharia Azam&#39;s Website | DevOps, Platform Engineering &amp; AI Insights</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 06 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://shaharia.com/tags/cursor/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Slack CLI for AI Agents — Give Claude Code, Cursor &amp; Codex Read/Write Slack Access in 10 Minutes</title>
      <link>https://shaharia.com/blog/slack-cli-for-ai-agents-claude-code-cursor-codex/</link>
      <pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate>
      <guid>https://shaharia.com/blog/slack-cli-for-ai-agents-claude-code-cursor-codex/</guid>
      <description>TL;DR. One Slack CLI (slackcli), three editors (Claude Code, Cursor, Codex CLI), xoxc/xoxd browser tokens for personal use or xoxb/xoxp for production. Total setup: 10 minutes. Token-efficient JSON output keeps your context window clean.&#xA;If you spend half your day in Slack and the other half in Claude Code, Cursor, or Codex CLI, there&amp;rsquo;s an obvious win: let the AI agent read Slack itself. Don&amp;rsquo;t paste threads into the chat.</description>
    </item>
  </channel>
</rss>
