Architecture

Claude Code
  └── stdio
      └── npx @automattic/mcp-wordpress-remote
              └── HTTPS (Application Password auth)
                      └── WordPress REST API (/wp-json/mcp/...)
                              └── MCP Adapter plugin
                                      └── WordPress Abilities API

Requirements

• WordPress 6.9+
• Node.js (installed via nvm)
• MCP Adapter plugin activated on the WordPress site

Step 1: Install the MCP Adapter Plugin

Via WP-CLI on the server:

wp plugin install https://github.com/WordPress/mcp-adapter/releases/latest/download/mcp-adapter.zip --activate

Or install manually from the GitHub releases page and activate in WP Admin → Plugins. Once active, the following REST API routes should be present:

/wp-json/mcp/
/wp-json/mcp/mcp-adapter-default-server

Step 2: Create a WordPress Application Password

1. Log into WP Admin → Users → Profile
2. Scroll to Application Passwords
3. Enter a name (e.g. claude-code) and click Add New Application Password
4. Copy the generated password — it is shown only once

Step 3: Install Node.js via nvm

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
source ~/.nvm/nvm.sh
nvm install --lts

Step 4: Add the MCP Server to ~/.claude.json

Add the following under mcpServers in ~/.claude.json:

{
  "wordpress": {
    "type": "stdio",
    "command": "/home/user/.nvm/versions/node/v24.x.x/bin/npx",
    "args": ["@automattic/mcp-wordpress-remote"],
    "env": {
      "WP_API_USERNAME": "your-wp-username",
      "WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx",
      "WP_API_URL": "https://yourdomain.com/wp-json/mcp/mcp-adapter-default-server",
      "PATH": "/home/user/.nvm/versions/node/v24.x.x/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
    }
  }
}

Two critical details:

• WP_API_URL must be the full endpoint path, not a bare domain. Passing just https://yourdomain.com triggers legacy mode in the package, which targets the deprecated /wp-json/wp/v2/wpmcp endpoint and returns a 404.
• PATH must include the nvm Node path. Claude Code sessions do not source .bashrc or nvm, so without this, npx fails with env: 'node': No such file or directory.

Note: XML-RPC (/xmlrpc.php) is not used — the MCP Adapter uses the REST API exclusively. It can stay disabled.

Step 5: Restart Claude Code and Verify

MCP servers connect at session startup. After editing ~/.claude.json, start a new session. To verify the endpoint is reachable beforehand:

curl -s https://yourdomain.com/wp-json/mcp/ | python3 -m json.tool

Should list /mcp and /mcp/mcp-adapter-default-server routes. Once connected, WordPress tools will appear alongside any other MCP tools in the session.

Notes

• The @automattic/mcp-wordpress-remote package is downloaded on first use by npx and cached in ~/.npm/.
• For additional WordPress sites, add new entries under mcpServers with different keys (e.g. wordpress-staging).
• MCP servers only connect at session start — always start a new Claude Code session after changing MCP configuration.

Why MCP Instead of CLI

The CLI (mnemosyne store, mnemosyne recall) is a manual tool — you run it yourself and paste results back. The MCP integration makes Mnemosyne a first-class tool Claude can call directly, just like any other tool in a session.

Concretely, with MCP:

• Claude automatically stores and retrieves memories during a conversation without any manual intervention
• Memory reads and writes happen inline, so context is enriched transparently
• No copy-pasting: Claude calls mnemosyne_remember or mnemosyne_recall the same way it calls any other tool

The CLI remains useful for inspection (mnemosyne stats), backup (mnemosyne export), and manual management — but it is not a substitute for the MCP integration when Claude is the one that needs to remember things.

Step 0: Disable Claude Code’s Built-in Auto-Memory

Claude Code has its own file-based memory system that writes to ~/.claude/projects/*/memory/. It runs in parallel with Mnemosyne if not suppressed, duplicating everything. Disable it by adding the following to ~/.claude/CLAUDE.md (create it if it doesn’t exist — this file is loaded in every session regardless of working directory):

## Memory

**Use Mnemosyne exclusively for persistent memory.** Call `mnemosyne_remember` and `mnemosyne_recall` via MCP tools.

**Never write to the file-based auto-memory system** at `~/.claude/projects/*/memory/`. Do not create or edit files there. Do not create or update any `MEMORY.md` index files. That system is not used.

Step 1: Install via pipx

pipx install mnemosyne-memory

This installs the mnemosyne CLI to ~/.local/bin/mnemosyne.

Step 2: Install the Hermes Tool Schemas

The MCP server depends on mnemosyne-hermes for its tool definitions. It must be injected into the same pipx venv:

~/.local/share/pipx/venvs/mnemosyne-memory/bin/python -m pip install mnemosyne-hermes

Skip this and mnemosyne mcp will start and complete the protocol handshake but advertise zero tools — silently broken.

Step 3: Register the MCP Server

claude mcp add --scope user mnemosyne   -e MNEMOSYNE_DATA_DIR=$HOME/.local/share/mnemosyne   -- ~/.local/bin/mnemosyne mcp

This writes the entry to ~/.claude.json, which is where Claude Code 2.x reads MCP server definitions. Do not add it to ~/.claude/settings.json — that file is not used for MCP configuration.

Step 4: Set the Data Directory in Your Shell

So that the CLI uses the same database as the MCP server, add to ~/.bashrc:

export MNEMOSYNE_DATA_DIR="$HOME/.local/share/mnemosyne"

Then run source ~/.bashrc.

Step 5: Restart Claude Code and Verify

MCP servers connect at session startup. After completing the above, start a new Claude Code session, then check:

claude mcp get mnemosyne   # should show Status: ✔ Connected
mnemosyne stats            # confirms CLI hits the right database

Step 6: Install the Mnemosyne Dashboard (Optional)

The Mnemosyne Dashboard is a local-first web UI for browsing, visualising, and maintaining your memory store. It’s intentionally minimal: Python standard library server, static HTML/CSS/JS frontend, no external JS runtime, no cloud calls, and read-only by default.

Install via Hermes

hermes plugins install wysie/mnemosyne-dashboard --enable
hermes gateway restart

Run as a persistent systemd service (Linux)

If you want the dashboard to survive Hermes restarts, run it as a systemd user service instead. Create ~/.config/systemd/user/mnemosyne-dashboard.service:

[Unit]
Description=Mnemosyne Dashboard
After=network.target

[Service]
Type=simple
WorkingDirectory=%h/.hermes/plugins/mnemosyne-dashboard
ExecStart=python3 server.py --host 0.0.0.0 --port 8765 --db %h/.local/share/mnemosyne/mnemosyne.db
Restart=on-failure
RestartSec=5
Environment=PYTHONUNBUFFERED=1

[Install]
WantedBy=default.target

Then enable and start it:

systemctl --user daemon-reload
systemctl --user enable mnemosyne-dashboard
systemctl --user start mnemosyne-dashboard

The dashboard will be available at http://localhost:8765/ (or your machine’s LAN IP if you bound to 0.0.0.0).

Configuration

Config lives at ~/.hermes/plugin-data/mnemosyne-dashboard/config.json. Key fields:

{
  "host": "0.0.0.0",
  "port": 8765,
  "db_path": "~/.local/share/mnemosyne/mnemosyne.db",
  "auth_enabled": false,
  "memory_admin_enabled": false
}

Memory admin (supersede, expire, importance updates) is disabled by default. If you enable it on a non-localhost bind address, password auth is required. Admin actions create a SQLite backup and append to an audit log — no hard deletes or raw overwrites are exposed.

Data Locations

Troubleshooting

MCP server connects but no tools appear

The mnemosyne-hermes package is missing from the pipx venv. Run Step 2 above. You can confirm by checking the tools/list response — if "tools":[], the package is missing.

CLI uses wrong database

The CLI default is ~/.hermes/mnemosyne/data/. Set MNEMOSYNE_DATA_DIR in ~/.bashrc (Step 4) to point it at the same path the MCP server uses.

Tools missing after restart

The config is probably in the wrong file. Claude Code 2.x reads MCP servers from ~/.claude.json, not ~/.claude/settings.json. Run claude mcp get mnemosyne — if it says “not found”, re-run Step 3.

A cleaner alternative, if your machines are already on Tailscale: skip the public internet entirely.

The Problem with Cloudflare and MCP

The @automattic/mcp-wordpress-remote package connects to WordPress via the REST API using HTTP Basic Auth (Application Passwords). Any edge layer that interferes with those REST API calls can silently break the connection. Common culprits when routing through Cloudflare:

• Bot Fight Mode blocking REST API POSTs
• Page caches returning stale or HTML responses on JSON endpoints
• Host WAFs blocking requests based on User-Agent strings
• Security plugins blocking access to the MCP endpoint

The Tailscale Approach

Since Claude Code runs the MCP client locally, it only needs the WordPress server to be reachable from the local machine — not from Anthropic’s servers. If both machines are on the same Tailscale network, you can route traffic directly over Tailscale by pinning the domain in /etc/hosts:

100.x.x.x        yourdomain.com
fd7a:xxxx::xxxx  yourdomain.com

Both IPv4 and IPv6 entries are needed. Without the IPv6 entry, DNS can still return Cloudflare’s AAAA records and route around the pin.

With this in place, yourdomain.com resolves to the Tailscale IP, traffic goes peer-to-peer, and none of the Cloudflare/WAF/cache layers are involved. The SSL certificate remains valid because the hostname matches.

The Plugin

The active WordPress MCP plugin is WordPress/mcp-adapter (not the older wordpress-mcp repo, which is deprecated). The endpoint lives at:

https://yourdomain.com/wp-json/mcp/mcp-adapter-default-server

Authentication is WordPress Application Passwords (Users → Profile → Application Passwords) via HTTP Basic Auth. XML-RPC is not involved.

MCP Client Configuration

In your Claude Code MCP config (~/.claude.json):

{
  "mcpServers": {
    "wordpress": {
      "command": "npx",
      "args": ["@automattic/mcp-wordpress-remote"],
      "env": {
        "WP_API_URL": "https://yourdomain.com/wp-json/mcp/mcp-adapter-default-server",
        "WP_API_USERNAME": "your-wp-username",
        "WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx",
        "PATH": "/home/user/.nvm/versions/node/v24.x.x/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
      }
    }
  }
}

Two critical details:

• WP_API_URL must be the full endpoint path, not just the domain. Passing a bare domain puts the package into legacy mode, where it targets /wp-json/wp/v2/wpmcp — the old deprecated plugin’s endpoint — returning a 404.
• PATH must be set explicitly if Node is installed via NVM. Claude Code’s environment doesn’t inherit your shell’s NVM paths, so without this the npx call fails to find Node.

Result

A successful MCP handshake returns a session ID and server info:

{"protocolVersion":"2024-11-05","serverInfo":{"name":"MCP Adapter Default Server","version":"v1.0.0"}}

No tunnels, no WAF exceptions, no cache exclusion rules — just a direct Tailscale connection to your own server.

Meralco is a utility company. It is not a bank, an e-wallet provider, or a financial institution holding customer funds. The information it needs to protect—customer name, service address, and billing amount—is important, but it does not carry the same risk profile as banking credentials or stored monetary value. The security approach should reflect that difference.

A Bill You Can See but Not Easily Get

When Meralco notifies customers that a monthly bill is available, the notification already displays the bill amount. That means the information is already deemed safe enough to transmit. Despite that, the actual PDF copy of the bill is not included.

To obtain it, customers must log in to the website, navigate through several pages, dismiss pop-ups, and repeat the process for each registered account each month. All this just to download a document that could have been emailed to me in the first place. Encrypt the PDF if you want—I do not care. Just send it.

Login Restrictions That Add Friction, Not Security

The login experience also raises questions about proportionality.

Pasting a password is allowed, but keyboard-based autofill—commonly used by password managers to populate both email address and password—is blocked. This forces manual entry of the email address while offering no meaningful improvement in security. It prevents convenience, not misuse.

Logging in from a different device also requires a one-time password sent to a registered mobile number. This is reasonable for high-risk actions, but for viewing or downloading a bill, it feels misaligned with the nature of the transaction. There are no funds to move—only a balance to view.

Repeating the Same Process, Every Month

For users managing multiple Meralco accounts under one profile, this experience is multiplied. Using the website for account administration is understandable. Being required to go through the same multi-step process every month, for every account, just to download bills is not.

This is a problem with workflow design, not user behavior.

A Simpler, More Balanced Approach

Emailing the monthly bill as a PDF would resolve most of these issues immediately. The website can remain the place for account management and changes. Routine access to a billing document should not require repeated navigation through a heavily restricted interface.

Good digital security should be based on balance—strong where risk is high, and simple where it is not.

Platform	GitHub Stars	Self-hosted	Focus / Best Use Case
n8n	159k	Yes	General-purpose workflow automation with powerful code node. Ideal for complex multi-service automations and ETL tasks.
Activepieces	19.3k	Yes	Low-code/no-code automation with occasional custom JS support. Good for lighter, simpler workflows.
Windmill	15.2k	Yes	Developer-centric automation using scripts (Python/TypeScript/Go). Great for internal tools and backend workflows.
Automatisch	13.4k	Yes	Simplified Zapier-style automation. Best for small, straightforward tasks when ease and self-hosting matter.

Summary: n8n remains the most powerful and versatile, while Activepieces and Windmill offer lighter or more code-centric alternatives. Automatisch is best if you just need simple self-hosted automations.

The whole ecosystem—themes, plugins, and even the support culture—has turned into a marketplace. Everywhere you go, there’s an upsell. Basic features sit behind paywalls. And if you just want to build a straightforward blog, the experience is frustrating.

Finding a minimalist theme with a clean two-column layout, no widget blocks, no theme blocks, no Gutenberg clutter, and no upgrade prompts used to be easy. Now it feels like searching for something that shouldn’t be rare. Most themes are bloated with builders, bundled features, and aggressive pro-version hooks.

The open-source spirit that made WordPress welcoming has given way to commercial noise. WordPress is still free at its core, but the culture around it has shifted. For someone who simply wants a clean, honest blogging theme, it’s hard not to feel like WordPress has lost its soul.

Paying bills has never been easier, thanks to the advent of mobile payment solutions like GCash and Maya. However, my recent experience with GCash highlighted a significant issue that needs addressing.

The Issue with Spam SMS

Recently, I was paying for my Globe Postpaid plan and decided to use GCash for the transaction. However, in the past few days, I’ve been inundated with spam marketing SMS from GCash. The frequency and irrelevance of these messages were frustrating, so I decided to block GCash in my Google Messages app.

The Unintended Consequence

When I attempted to pay my bill via GCash, I didn’t receive the OTP (One-Time Password) required to complete the transaction. It quickly dawned on me that GCash was blocked, preventing the OTP from coming through. I unblocked GCash temporarily, but the OTP still took too long to arrive. This delay was unacceptable, especially when trying to complete a time-sensitive transaction.

Switching to Maya

Frustrated by the inconvenience, I turned to Maya for my payment. The process was smooth, and I received the OTP without any issues. This experience was a stark contrast to the one I had with GCash and highlighted a crucial lesson for businesses: customer satisfaction is paramount.

The Impact of Spam SMS

Spam SMS not only annoy customers but can also lead to significant business losses. When customers are overwhelmed with irrelevant messages, they’re likely to block the sender, missing out on important communications like OTPs. This leads to frustration and can drive customers to competitors, as it did in my case.

A Call to Action for Businesses

For businesses utilizing SMS for marketing, it’s crucial to strike a balance. While reaching out to customers is essential, bombarding them with spam can backfire. One effective strategy is to limit marketing messages to a separate account, distinct from the one used for important communications like OTPs. Additionally:

1. Opt-in Preferences: Allow customers to choose the type of messages they want to receive.
2. Frequency Control: Limit the number of marketing messages sent within a certain period.
3. Relevance: Ensure that messages are relevant to the customer’s interests and needs.

Conclusion

My experience underscores the importance of thoughtful and strategic communication with customers. By respecting customer preferences and reducing spam, businesses like GCash can improve customer satisfaction and retain their user base.

In the end, the key takeaway is clear: respect your customers’ communication preferences, or risk losing them to competitors who do.

In a digital landscape dominated by videos, sometimes simplicity and speed are all you need. Leo Laporte, the Tech Guy, once lamented the frustration of clicking on a video only to wade through minutes of unnecessary intros and prompts to like, subscribe, and hit the bell icon.

Consider scenarios where you’re in a quiet environment or simply prefer to read instructions quickly. Opening a video might not always be practical or preferred. This blog focuses solely on text-based content, ensuring you can access information swiftly and without distraction.

In today’s fast-paced world, efficiency matters more than ever. Whether troubleshooting a tech issue or seeking information, text-based resources offer a streamlined experience. They allow you to dive straight into content, saving time and boosting productivity.

As we navigate a vast sea of online information, the demand for quick, accessible answers continues to grow. Text-based formats complement videos by delivering information promptly and effectively, catering to users who value direct access without unnecessary frills.

In conclusion, this blog is dedicated to text-based content, prioritizing efficiency, clarity, and immediate access to information. Whether you prefer quiet reading or need swift solutions, text-based resources ensure that valuable insights are just a click away.

This behavior can be frustrating, especially if you’re used to seamlessly integrating your browsing experience with your notes. Here’s why this happens and what you can do about it:

Understanding the Issue: Snap Package Peculiarities

Snap packages are known for their sandboxing approach, which aims to enhance security by isolating applications and their dependencies from the rest of the system. While this isolation can be beneficial for security reasons, it also means that applications installed via Snap may behave differently compared to their counterparts installed via other methods like Flatpak or .deb packages.

One notable difference is how Snap handles application interactions with the system, such as opening external links. In the case of Obsidian installed via Snap, opening links from within your notes triggers the opening of your default browser in a separate profile. This ‘Profile 1’ is independent of the profile you typically use for your browsing activities, resulting in a disjointed user experience.

Why You Should Consider Alternatives: Flatpak or .deb

To avoid the inconvenience caused by Snap’s behavior with Obsidian, consider installing the application using alternative methods like Flatpak or downloading the .deb package directly from Obsidian’s official website. Here’s why these alternatives may be preferable:

1. Consistent User Experience: Flatpak and .deb packages generally integrate more seamlessly with the Ubuntu desktop environment, preserving your existing browser settings and profiles. When you open links from Obsidian notes, they will launch in your default browser, maintaining your familiar browsing environment.
2. Ease of Installation: Installing via Flatpak or .deb is straightforward and ensures that Obsidian behaves predictably within your Ubuntu setup. You won’t encounter the profile switching issue that Snap packages may introduce.
3. Community Support and Updates: While Snap packages are officially supported by Canonical (the company behind Ubuntu), Flatpak and .deb packages also receive robust community support and timely updates from Obsidian developers. This ensures you have access to the latest features and fixes without compromising on usability.

Conclusion

While Snap packages offer a convenient way to install applications on Ubuntu, the specific behavior of Obsidian with Snap—opening links in a separate browser profile—can disrupt your workflow. For a smoother and more integrated experience, opting for Flatpak or .deb installation methods is recommended. These alternatives ensure that Obsidian functions seamlessly with your preferred browser settings, avoiding the inconvenience of profile conflicts.

Next time you install Obsidian on your Ubuntu system, consider choosing Flatpak or .deb over Snap to enjoy a cohesive note-taking and browsing experience without unnecessary complications. Your productivity and user satisfaction will thank you for it!

Have you encountered similar issues with Snap packages or found better alternatives for installing applications on Ubuntu? Share your experiences and tips in the comments below!

Introduction

As we eagerly anticipate the release of “House of the Dragon” Season 2, it’s essential to revisit the intricate and dramatic events of Season 1. The series, a prequel to the acclaimed “Game of Thrones,” plunges us into the tumultuous history of House Targaryen, nearly 200 years before the rise of Daenerys Targaryen. Season 1 masterfully sets the stage for the epic civil war known as the Dance of the Dragons, a conflict that threatens to tear the Targaryen dynasty apart. Through political intrigue, personal betrayals, and spectacular dragon battles, the first season captivates and prepares us for the storm that is about to unfold.

Episode 1: “The Heirs of the Dragon”

The series opens with King Viserys I Targaryen sitting on the Iron Throne. He faces the challenge of naming an heir, as his wife, Queen Aemma, is pregnant. However, both Aemma and their newborn son die during childbirth. This tragedy leaves Viserys with no direct male heir. Amidst this turmoil, the king’s brother, Prince Daemon Targaryen, behaves recklessly. Ultimately, Viserys makes the controversial decision to name his daughter, Princess Rhaenyra, as his heir, despite the precedent of male succession.

Episode 2: “The Rogue Prince”

Daemon seizes control of Dragonstone, escalating tensions within the kingdom. Rhaenyra begins to navigate her role as heir, asserting her presence and leadership. Meanwhile, Viserys is pressured to remarry to secure the line of succession. He shocks the court by choosing Lady Alicent Hightower, Rhaenyra’s close friend, over a more politically advantageous match. This decision strains relationships within the court and sets the stage for future conflicts.

Episode 3: “Second of His Name”

Three years later, Viserys and Alicent’s son, Prince Aegon, celebrates his second birthday, intensifying the succession debate. Meanwhile, the Stepstones conflict rages on, with Daemon and Lord Corlys Velaryon struggling against the Triarchy. Rhaenyra feels increasingly sidelined as the focus shifts to her half-brother, Aegon. Daemon takes matters into his own hands, launching a daring and brutal attack that leads to a significant victory, solidifying his reputation as a formidable warrior.

Episode 4: “King of the Narrow Sea”

Daemon returns to King’s Landing, proclaiming himself the “King of the Narrow Sea” after his victories. His relationship with Rhaenyra becomes more complicated as he introduces her to the city’s more unsavory elements. Their night out leads to scandal, as rumors of impropriety spread. To mitigate the fallout, Viserys hastily arranges Rhaenyra’s betrothal to Ser Laenor Velaryon. Tensions continue to rise as old alliances are tested and new ones are formed.

Episode 5: “We Light the Way”

Preparations for Rhaenyra and Laenor’s wedding bring various factions to King’s Landing. The celebration is marred by violence when Ser Criston Cole, a knight who has formed a close bond with Rhaenyra, kills Laenor’s lover, Ser Joffrey Lonmouth, in a fit of rage. This incident heightens the already simmering tensions and casts a shadow over the marriage. Alicent begins to assert her influence more openly, setting the stage for future power struggles.

Episode 6: “The Princess and the Queen”

A significant time jump reveals Rhaenyra and Laenor have had children, though rumors persist about their true parentage. Alicent and Rhaenyra’s rivalry deepens as their respective factions vie for influence. The growing tension between the two women is mirrored by the escalating conflict over the succession. The seeds of civil war, known as the Dance of the Dragons, are sown as the kingdom begins to fracture along these fault lines.

Episode 7: “Driftmark”

The death of Laena Velaryon brings the families together at Driftmark, leading to confrontations and alliances. A violent clash ensues when Alicent’s son, Aemond, claims the dragon Vhagar, leading to a fight with Rhaenyra’s sons that results in Aemond losing an eye. The conflict between the families intensifies, with both sides accusing the other of treachery. Viserys struggles to maintain peace, but the divisions run deep.

Episode 8: “The Lord of the Tides”

Viserys’s health continues to decline, and the question of succession becomes more urgent. The Velaryons seek to secure their position by proposing marriages between their children and Rhaenyra’s. Alicent’s faction, however, maneuvers to place Aegon in a more favorable position. The political intrigue reaches new heights as both sides prepare for the inevitable clash over the Iron Throne.

Episode 9: “The Green Council”

Upon King Viserys’s death, Alicent and her father, Otto Hightower, swiftly move to place Aegon on the throne, circumventing Rhaenyra’s claim. This power grab, known as the Green Council, sets the stage for open conflict. Rhaenyra, unaware of her father’s death, is vulnerable, and her supporters scramble to consolidate their positions. The kingdom teeters on the brink of civil war as the rival factions prepare for battle.

Episode 10: “The Black Queen”

Rhaenyra learns of her father’s death and Alicent’s betrayal. Enraged and determined to claim her birthright, she declares herself queen and begins rallying her supporters. Daemon and Rhaenyra gather their forces, securing key alliances with the Velaryons and other powerful houses. The first major battle of the civil war erupts, marking the beginning of the Dance of the Dragons. The season ends with a sense of foreboding, as the realm braces for the bloody conflict ahead.

Final Thoughts

Season 1 of “House of the Dragon” not only reintroduces us to the grandeur and complexity of George R.R. Martin’s world but also lays a compelling foundation for the conflicts to come. The detailed character arcs and escalating tensions between key players like Rhaenyra Targaryen, Alicent Hightower, and Daemon Targaryen hint at the epic scale of the battles ahead. As alliances shift and rivalries deepen, the stakes are higher than ever for the Iron Throne. With Season 2 on the horizon, fans can expect even more dramatic twists, fierce power struggles, and breathtaking moments as the Dance of the Dragons truly begins. Prepare for a season that promises to be as thrilling and unpredictable as its predecessor.

HBO Max subscribers and Plex users alike can start streaming “House of the Dragon” Season 2 on June 16, 2024, at 9 p.m. ET, which is June 17, 2024, at 9 a.m. PHT for viewers in the Philippines. Each episode will be released weekly, with the season consisting of eight episodes in total.