5 posts tagged with "feature"

If you're a developer, there's a good chance an AI agent already sits in your terminal or editor - Claude Code, Cursor, Codex, whatever you've settled on. Wallu now has a remote MCP server, which means that same agent can manage your Discord support bot directly: read and change settings, update FAQs and documents, and test answers through the real pipeline.

No SDK, no custom integration code. One API key and a config snippet.

Wallu doesn't answer every message, and that's on purpose. You can tell it to only speak when mentioned, to stay quiet around staff, to wait a few minutes for a human first, to keep out of certain channels, or to only talk to verified members. On top of that, it sometimes just doesn't recognize that a message was a question it could have handled.

So you end up with this situation a lot: someone asks something, Wallu stays silent, and you - the staff member - know for a fact the answer is sitting in your documentation. The setup guide, the refund policy, the "why is my thing not connecting" steps. It's all there. Wallu just didn't say it this time.

Your old options were: type it out yourself, or dig up the doc and copy-paste it. Both are annoying, especially when the answer is long or has links in it.

Managing a high-volume support server often leads to a sidebar cluttered with generic channel names like #ticket-4821, #ticket-5930, and #ticket-2104. While functional, these names don't provide much context for staff members trying to prioritize their workload.

To help with this, we've introduced AI Ticket Renaming—a feature that allows Wallu to rename ticket channels based on the topic of the conversation.

Setting up a support bot shouldn't feel like a part-time job. Usually, it involves jumping between Discord and a web dashboard, copying IDs, and trying to figure out which setting does what.

We wanted to change that. Today, I'm excited to introduce the Wallu Setup Agent (currently in Beta).

If you maintain software, a mod, a plugin, or an open-source library, you know that documentation rarely covers everything. Users often ask questions that require you to open your IDE, search for a config key, trace where it's used, and figure out exactly how a specific edge case is handled.

"What is the default value for max_connections?" "Why does the on_join event fire twice?" "Does the legacy API still support XML?"

Your documentation might not say. But your code does.

Today, we're introducing GitHub Integration and Deep Search – a new capability that lets Wallu investigate your codebase directly to answer complex support questions.