Give your agent a job.
Connect your agent below, then choose a task to give it. These prompts do not create agents or grant access to apps.
For Claude Code. Paste into your agent to begin.
- 1Paste into Claude Code
Your agent will handle the setup steps it supports.
- 2Approve the connection
Choose your Monologue feed when sign-in opens. You approve reading and reporting in that feed.
- 3Confirm it’s ready
Ask your agent to check its connection and reporting instructions. It may need one restart.
Already connected? Your agent should reuse its connection and check the reporting instructions.
Review the instructions
Set up Monologue for Claude Code. Use my Monologue instance at https://www.monologue.events. Read and execute https://www.monologue.events/agent-setup. Use https://www.monologue.events as MONOLOGUE_URL for this setup, including approval links and manual-key fallback. This instance replaces the guide's hosted defaults; do not switch to another service if setup fails. Ask me to choose the workspace during connection approval. Keep the connection bound to that workspace. If your client supports secure MCP setup, use https://www.monologue.events/mcp; otherwise use this instance's approval-link flow. Request actions:read and actions:write together in one connection approval. Read and add reports with the same feed access I have in the chosen workspace; access follows my current membership. Reuse an existing connection only for this instance and workspace. Preserve any existing URL/credential pairing. An older limited connection needs reconnection and approval before gaining access; never silently broaden it. Never display credentials. This prompt grants no access by itself. Install the canonical monologue skill using your supported skill manager so the reporting instructions persist in later sessions. Do not duplicate the skill into several rule files. Install for this user across projects, not just the current project, unless I explicitly request project-only setup. Keep one canonical skill installation and use the skill manager’s supported links. Before adding anything, check for a working connection and discoverable skill. Reuse them. Preserve an explicitly configured MONOLOGUE_URL/MONOLOGUE_API_KEY pairing and never switch it to another instance. Do not overwrite unrelated client settings or expose configuration secrets. The existing portable skill installation option is: npx skills add willcheung/monologue --skill monologue --agent claude-code --global --yes. Check the appropriate install scope for my agent; configuration/skill file creation alone does not prove discovery. First check for an existing authenticated Monologue connection, including a connector inherited from my Claude account. Reuse it. If absent, use Claude Code's native MCP commands below. Use the permission policy in the shared setup instructions and preserve existing limited grants until explicitly reapproved. If login requires an interactive terminal, give me one step: run claude mcp login monologue in my terminal, then return here. Do not retry it in a non-interactive tool. The MCP endpoint is https://www.monologue.events/mcp. Only if this connection is missing, the supported configuration/authentication references are: claude mcp add --transport http --scope user monologue 'https://www.monologue.events/mcp' claude mcp login monologue Follow the shared permission policy above: the standard connection requests reading and reporting together in one approval. Older limited grants must not gain access silently. Start authentication when supported, then let me sign in and approve the intended feed; never hard-code a demo or test workspace or approve on my behalf. Confirm the skill is discoverable and the actual reporting tool is available in the execution context. If a restart is required, give one clear restart/resume step and verify afterward. For API-only setup, distinguish configured credentials from a successful report. Do not invent a test action or write a synthetic event to my feed. Finish with a short setup result: instructions available, connection status, granted permissions and any remaining step. After my next authorized external action, report its actual outcome and return the real event ID. Research, drafts, local development and Monologue tool calls stay out.
Manual setup
Use these only when the connection is missing. Keep existing connections and unrelated settings.
claude mcp add --transport http --scope user monologue 'https://www.monologue.events/mcp' claude mcp login monologue
Personal assistant
Help with emails and calendar changes, with a record you can revisit.
Read and execute https://www.monologue.events/agent-setup. Use https://www.monologue.events as MONOLOGUE_URL for this setup, including approval links and manual-key fallback. This instance replaces the guide's hosted defaults; do not switch to another service if setup fails. Ask me to choose the workspace during connection approval. Keep the connection bound to that workspace. If your client supports secure MCP setup, use https://www.monologue.events/mcp; otherwise use this instance's approval-link flow. Request actions:read and actions:write together in one connection approval. Read and add reports with the same feed access I have in the chosen workspace; access follows my current membership. Reuse an existing connection only for this instance and workspace. Preserve any existing URL/credential pairing. An older limited connection needs reconnection and approval before gaining access; never silently broaden it. Never display credentials. This prompt grants no access by itself. Help me with emails and scheduling. First, tell me which apps you can already use, then ask what I want help with. Draft replies and proposed calendar changes for me to review. Keep your existing permissions and approval rules. Ask before any new access or commitment. Research and drafts stay in our chat. After an authorized external action or meaningful attempt, report its actual outcome to Monologue and include a result or receipt URL when available. Never invent an action, receipt, or successful outcome.
Shopping helper
Compare options first. Keep order and booking receipts after you approve a purchase.
Read and execute https://www.monologue.events/agent-setup. Use https://www.monologue.events as MONOLOGUE_URL for this setup, including approval links and manual-key fallback. This instance replaces the guide's hosted defaults; do not switch to another service if setup fails. Ask me to choose the workspace during connection approval. Keep the connection bound to that workspace. If your client supports secure MCP setup, use https://www.monologue.events/mcp; otherwise use this instance's approval-link flow. Request actions:read and actions:write together in one connection approval. Read and add reports with the same feed access I have in the chosen workspace; access follows my current membership. Reuse an existing connection only for this instance and workspace. Preserve any existing URL/credential pairing. An older limited connection needs reconnection and approval before gaining access; never silently broaden it. Never display credentials. This prompt grants no access by itself. Help me compare products, prices, and booking options. Ask what I need and my budget first. Do not buy, book, or start a subscription until I approve the specific item and total cost. Keep your existing permissions and approval rules. Ask before any new access or commitment. Research and drafts stay in our chat. After an authorized external action or meaningful attempt, report its actual outcome to Monologue and include a result or receipt URL when available. Never invent an action, receipt, or successful outcome.
Coding agent
Keep pushes, pull requests, and shared deployments separate from local development.
Read and execute https://www.monologue.events/agent-setup. Use https://www.monologue.events as MONOLOGUE_URL for this setup, including approval links and manual-key fallback. This instance replaces the guide's hosted defaults; do not switch to another service if setup fails. Ask me to choose the workspace during connection approval. Keep the connection bound to that workspace. If your client supports secure MCP setup, use https://www.monologue.events/mcp; otherwise use this instance's approval-link flow. Request actions:read and actions:write together in one connection approval. Read and add reports with the same feed access I have in the chosen workspace; access follows my current membership. Reuse an existing connection only for this instance and workspace. Preserve any existing URL/credential pairing. An older limited connection needs reconnection and approval before gaining access; never silently broaden it. Never display credentials. This prompt grants no access by itself. Help me work on my software project. Ask which repository and task to work on. Local edits, commits, tests, builds, and dev-server restarts do not belong in the feed. Report a remote push, pull request change, or shared deployment as its own action, with the commit, pull request, or deployment URL when available. Keep your existing permissions and approval rules. Ask before any new access or commitment. Research and drafts stay in our chat. After an authorized external action or meaningful attempt, report its actual outcome to Monologue and include a result or receipt URL when available. Never invent an action, receipt, or successful outcome.
You still decide what happens
Review what your agent plans to send, buy, book, or deploy. The prompts preserve its existing permissions and approval rules. Monologue records reported outcomes; it does not authorize the work.
Find setup instructions for your agent →