Explore open-source AI prompts powering Twilio’s Docs AI Buddy. Help writers and engineers draft, refactor, and review technical docs efficiently.

Twilio launches its Partner Advisory Board to shape product strategy with top SI and tech partners across global markets in 2026.

The following is an excerpt from a 200+ page document titled AI-Assisted Data Engineering Development Playbook: How I Set Up a Virtual Server (Virtual Machine) for Modern Data Engineering for sale at DELMSuite.com, but available – free – to paid subscribers of my newsletter: Engineer of Data.

The phrases context fatigue, attention degradation, instruction drift, and maximum context length describe a persistent and nagging problem for LLM and AI users, even in December 2025. In a nutshell, context fatigue occurs as conversations with AI extend over some period. The amount of time that passes before context fatigue starts has increased as Large Language Models (LLMs) and AI engines have gained resources, and as model efficiencies have improved.

Stephen Leonard, AI Engineer at Enterprise Data & Analytics’, built an MCP (Model Context Protocol) server named Durandal to mitigate context fatigue. You can learn more about Durandal, including instructions about how to install Durandal memory MCP Server – by searching for “Durandal MCP server”.

At the time of this writing, the best link to follow is https://www.npmjs.com/package/durandal-memory-mcp:

Navigating to the Durandal site on npm provides additional resources, including a link to the readme file at the GitHub repository for the open source project (https://github.com/Wawtawsha/durandal-memory-bridge#readme):

The readme file at the GitHub repository for the open source project (https://github.com/Wawtawsha/durandal-memory-bridge#readme) includes instructions to:

1. Install Durandal
2. Add Durandal to Claude Code
3. Verify Durandal setup:

To copy the install command for Durandal, click the copy icon:

Open a command prompt (or, as I did here, click the Windows taskbar-pinned “ClaudeCode” we configured earlier) and then right-click to paste the installation command:

Press Enter to execute the install command:

Copy the (architecture- / platform-specific) command to add Durandal to your architecture / platform:

Paste the command and then press Enter to execute the add command:

Copy the Verify Setup command to verify the installation and addition to Claude Code:

Paste the command and then press Enter to verify Durandal exists in your claude MCP list:

Start Claude Code:

When Claude Code starts, check for connected MCP servers by typing the “/mcp” command:

If Durandal is ready to roll, you should see the highlighted message below:

Press the Enter key to view details:

Learn more about how to use Durandal by reading the readme document at the GitHub site (https://github.com/Wawtawsha/durandal-memory-bridge#readme):

Conclusion

Durandal Memory MCP Server mitigates context fatigue with Claude Code.

Need Help Implementing AI-Assisted Enterprise Data Engineering?

Enterprise Data & Analytics stands ready to serve you and your team.

Contact us today!

GitHub will begin charging $0.002 per minute for self-hosted Actions runners used on private repositories starting in March. "At the same time, GitHub noted in a Tuesday blog post that it's lowering the prices of GitHub-hosted runners beginning January 1, under a scheme it calls 'simpler pricing and a better experience for GitHub Actions,'" reports The Register. "Self-hosted runner usage on public repositories will remain free." From the report: Regardless of the public repo distinction, enterprise-scale developers who rely on self-hosted runners were predictably not pleased about the announcement. "Github have just sent out an email announcing a $0.002/minute fee for self-hosted runners," Reddit user markmcw posted on the DevOps subreddit. "Just ran the numbers, and for us, that's close to $3.5k a month extra on our GitHub bill." [...] "Historically, self-hosted runner customers were able to leverage much of GitHub Actions' infrastructure and services at no cost," the repo host said in its blog FAQ. "This meant that the cost of maintaining and evolving these essential services was largely being subsidized by the prices set for GitHub-hosted runners." The move, GitHub said, will align costs more closely with usage. Like many similar changes to pricing models pushed by tech firms, GitHub says "the vast majority of users ... will see no price increase." GitHub claims that 96 percent of its customers will see no change to their bill, and that 85 percent of the 4 percent affected by the pricing update will actually see their Actions costs decrease. The company says the remaining 15 percent of impacted users will face a median increase of about $13 a month. For those using self-hosted runners and worried about increased costs, GitHub has updated its pricing calculator to include the cost of self-hosted runners.

Read more of this story at Slashdot.

Microsoft has begun decommissioning IntelliCode in VS Code, ending free local AI-assisted completions and shifting its developer AI strategy fully to subscription-based GitHub Copilot.

---