Skip to main content

Wallu Now Reads Your Code: Introducing GitHub Integration & Deep Search

· 4 min read
Topias
Topias
Wallu's Developer

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.

Most AI support bots work by "semantic search" (RAG). They find a relevant paragraph in your uploaded PDFs or website and summarize it. This works great for general questions, but falls apart when the answer lies in the logic of your application.

Wallu's new Deep Search is different. It's not just a search engine; it's an autonomous investigation agent.

When a user asks a question that your documentation can't answer, but you have added a Git repository as a knowledge base, Wallu can now:

  1. Search your repository for relevant keywords (config names, error codes, class names).
  2. Read the actual code to understand logic, default values, and validation rules.
  3. Trace dependencies to see how one setting affects another.
  4. Synthesize an answer based on how the code actually behaves, not just what the docs say.

Real-World Use Cases​

We built this feature specifically for software projects, game servers with custom plugins, and developer communities.

1. The "Undocumented Setting" Mystery​

User: "I set buffer_size: 5000 but it's still slow." Wallu (investigating): Searches for buffer_size. Finds it in config.py. Sees a line: self.buffer = min(value, 4096). Wallu Answer: "Even though you set buffer_size to 5000, the code actually caps this value at 4096 internally. You might need to adjust the MAX_BUFFER constant if you need higher values."

2. The Specific Error Trace​

User: "I'm getting Error 502: Bad Gateway when uploading large files." Wallu (investigating): Greps for "Bad Gateway". Finds the exception handler in upload_service.js. Notices it triggers when the timeout is reached. Wallu Answer: "This error usually occurs because the upload exceeds the default timeout. The code indicates this happens in the upload service when processing takes too long."

3. Feature Compatibility​

User: "Does the new version support the old permission system?" Wallu (investigating): Checks the permissions/ directory. Finds a LegacyPermissionAdapter class. Wallu Answer: "Yes, it appears the legacy permission system is supported via an adapter layer, so your old configurations should still work."

Privacy & Security First​

We know your code is sensitive.

  • Private Repositories: You can connect private GitHub repos. Wallu accesses them securely with your authorization and includes guardrails designed to prevent outputting sensitive information like secrets (though you should avoid storing sensitive data that it shouldn't use in answers).
  • Safety Guardrails: The agent is instructed to explain how things work or why an issue occurs, without revealing sensitive information.
  • Access Control: You choose exactly which repositories Wallu can see.

How to Get It​

This feature is currently in Beta.

We are rolling it out gradually to ensure it scales well and provides accurate results. If you are a software maintainer, modder, or developer using Wallu for support, this is designed for you. Currently, Wallu uses this feature sparingly to handle complex questions that can't be answered from documentation alone.

You can connect your GitHub repository in the Wallu Dashboard under Your Documents -> Add Knowledge Document.

Note: As this is a beta feature, we're actively tuning the investigation logic. Join our Discord to share your feedback!