Todoist connector removed from Claude, custom setup required

Todoist connector no longer available in Claude
The official Todoist connector has been removed from Claude's built-in connectors. Users who previously relied on this integration now need to set it up manually as a custom connector.
Custom connector setup steps
To add Todoist back to Claude:
- Step 1: Open Customize in Claude Desktop or on claude.ai (click Customize in the left sidebar)
- Note: You cannot use the Claude mobile app to configure connectors, but you can use the connectors on mobile after configuring them via Desktop or web
- Step 2: Click Connectors in the Customize panel
- Step 3: Click the + (plus) icon, then click Add custom connector
- Step 4: Paste the Todoist MCP URL in the URL field: https://ai.todoist.net/mcp
- Step 5: Click Add to save the connector
- Step 6: Authenticate with Todoist. The connector will appear in your list, but it's not connected yet. Click on the connector to open it. This will launch Todoist's OAuth flow in your browser, where you authorize Claude to access your Todoist account. Grant the permissions and you'll be redirected back to Claude. The connector should now show as connected
- Step 7: Test it. Start a new conversation and try something like "What tasks do I have due today?" or "Add a task to buy groceries." Claude should be able to read and write to your Todoist
Requirements and limitations
You need to be a Claude Pro or Max subscriber to add custom connectors. The setup must be done via Claude Desktop or the web interface at claude.ai - the mobile app cannot configure connectors, though configured connectors will work on mobile.
📖 Read the full source: r/ClaudeAI
👀 See Also

How Small Model Evaluation Prompts Can Mislead and How to Fix Them
A Reddit post explains that small model evaluation prompts often produce misleading results due to triggering the wrong cognitive pathways in transformers, specifically identifying three distinct modes: factual recall, application/instruction following, and emotional/empathic inference.

OpenClaw 4.1 with Gemma 4 Stack: Hybrid Architecture and Setup Fixes
A Reddit post details an optimized local agent stack combining OpenClaw 4.1 with Google's Gemma 4 model, featuring a hybrid architecture, specific configuration fixes for Ollama tool calling, and context window adjustments.

Running a 1 Trillion Parameter LLM Locally on AMD Ryzen AI Max+ Cluster
AMD demonstrates running the Kimi K2.5 open-source model (375GB, 1 trillion parameters) across four Framework Desktop systems with Ryzen AI Max+ 395 processors using llama.cpp RPC. The guide covers TTM kernel modifications for 120GB VRAM per node and provides two setup options: Lemonade SDK pre-built binaries or manual ROCm 7.0.2 installation.

What Breaks When Running Coding Agents on Small Local Models
Real-world failure points from testing multi-file tasks on sub-7B models: markdown fences, structured output reliability, file editing errors, and classification of read vs. write actions.