GoLinuxCloud AI Bot

There is an Ask AI button in the bottom-right corner of every page on this site. It opens the GoLinuxCloud AI Bot, which searches the tutorials published here and provides article-based answers with links to supporting guides.

This page explains where those answers come from, how to get a good one, the limits the bot works within, and what happens when it gets something wrong.

Last reviewed: 9 September 2026.

1. Where the answers come from

The bot searches GoLinuxCloud tutorials covering Linux, Kubernetes, Ansible, Python, shell scripting, SQL, networking and security. It can assemble an answer from article passages, use a prepared example, return a cached response, or ask Cloudflare Workers AI to write a summary from selected passages. Generated text can contain mistakes or unsupported statements even when it includes a citation.

That single design decision is what makes the bot useful, and it has two consequences worth knowing about.

  • Article-based answers include source links. Generated answers are checked for recognized citation labels, with exceptions for refusals. Greetings and clarification replies may have no citations. A citation does not establish that every statement is supported; open the guide to check.
  • It is designed to decline weak matches. Relevance checks and fallbacks reduce unsupported answers, but they do not guarantee that an off-topic or incorrect answer can never appear.

The bot also runs its search in your browser rather than on a server, against a static index the site ships. Your question is not sent by the bot until you submit it. Submitted questions and answers can be recorded even when the answer was assembled in your browser. Generated-answer requests also include passage identifiers so the server can re-read those guides. Feedback sends a rating and conversation reference; it does not upload another transcript.

2. How to ask it

Open the panel in whichever way suits you:

  • Click Ask AI in the bottom-right corner of any page.
  • Press the / key anywhere on the site.
  • Type into the ask box in the site header, and your question opens the panel already asked.

Then treat it like a conversation rather than a search box. Full questions work better than keywords, because the bot is matching meaning and not just words. "Why does my pod stay in CrashLoopBackOff" gets you further than "crashloopbackoff".

A few things about the panel that are not obvious:

  • Follow-up questions work. The bot remembers the conversation, so you can ask "and how do I make that permanent?" without repeating the context.
  • The conversation follows you. Open a different guide, or a second tab, and the same conversation is still there. The browser stores up to 14 messages (normally seven question/answer exchanges), subject to a size limit. A saved conversation is discarded when next read after 12 hours since its last save; further activity refreshes that time.
  • The broom clears the browser copy. It does not delete server history, provider logs or the budget cookie. The clipboard beside it copies the whole conversation as text, which is handy for pasting into notes or a ticket.
  • Esc clears what you typed when the box has something in it, and closes the panel when it does not.

3. What it is good at, and what it is not

It is genuinely good at three things: finding the right guide out of thousands when you cannot remember its title, quoting a command that has actually been tested on a real host, and stitching together steps that are spread across two or three separate tutorials.

It is not good at anything outside this site, and it does not know your environment. It has never seen your distribution, your versions, your firewall rules or your cluster. So treat every command it gives you the way you would treat any command from the internet: read it, understand it, and run it in a lab before you run it in production.

4. It can make mistakes

It can, and it will. This is worth being specific about rather than hiding behind a disclaimer.

The bot does not copy the guides word for word. It reads the relevant passages and writes a fresh answer, and something written fresh can go wrong in ways the original does not. It can drop a caveat that mattered. It can flatten a "on RHEL 9 only" into general advice. When a question is ambiguous it can pick the wrong guide and answer confidently from it.

That is why the citations are there, and why they are the most important part of any answer. The linked section is the reviewed, tested version. The answer above it is a summary of that section written seconds ago by a machine.

When something is wrong, use the thumbs down control under Helpful? at the bottom of the panel (or rate when you close the panel). That attaches your rating to the conversation records already held on our servers, so I can review the reported problem. If the guide behind the answer is wrong, I fix the guide, which helps every future reader and not just the bot. If the guide was right and the bot misread it, that tells me something about how answers are being assembled, which is just as useful.

Reporting an error in a tutorial itself, rather than in a bot answer, is covered in the Corrections Policy.

5. Daily limits

Generating an answer costs real compute, and this site runs the bot inside a limited allowance rather than unlimited budget. Keeping it free for readers means keeping it inside a cap, so there are two: one for the whole site each day, and a smaller one per visitor so a single heavy user cannot spend everyone's share before lunch.

In practice you are unlikely to meet either. If you do, here is what you will see:

  • A popular question comes back instantly. Answers are cached, so a question someone already asked costs nothing and returns immediately.
  • When the day's allowance is gone, you still get an answer. The bot falls back to assembling the relevant passages directly from the guides without rewriting them. It reads more plainly, but the content and the links are the same material.
  • Everything resets at midnight UTC.

6. What happens to what you type

When you submit a question, we record question/answer text and operational data in Cloudflare D1. This includes browser/conversation identifiers, page paths and query parameters, selected guide URLs and scores, timestamps, response types, quality labels and ratings. A corrected or expanded version of your question may be sent and stored. Failed or rejected generations can also be logged.

The bot uses a signed browser cookie and an IP-derived label for limits. Some generated answers are cached in Cloudflare R2 and can be reused for another reader asking a matching question. Workers AI processes generated-answer requests; AI Gateway can separately retain prompts, responses and usage metadata when logging is enabled. The chatbot integration does not send chat text, ratings or chatbot-specific events to GA4, although GA4 runs separately on the page.

The panel saves a conversation copy in browser localStorage. Thumbs up/down attaches a rating, time and source to existing server conversation records; it does not send a new transcript snapshot.

D1 history is configured for daily cleanup after 90 days, session summaries after 90 days since last activity, and R2 cache objects after 30 days. Deletion depends on successful cleanup. Budget identifiers use activity-triggered cleanup; provider logs have separate retention. See the Privacy Policy for details and exceptions.

Clearing the panel does not delete server records. To request access or deletion, email admin@golinuxcloud.com. Do not send your signed cookie or credentials.

Details are in Privacy Policy §2.3 and the Cookie Policy. Do not paste passwords, keys, tokens, or confidential data into the bot.

7. Why it says Beta

Because it is, and the label is not decoration. The way questions are matched to guides, the wording of the answers and the limits above are all still changing, sometimes weekly. Answers you get today may be phrased differently next month, and a question that gets declined this week may be answerable once the guide behind it exists.

The bot is designed to help you find and understand these tutorials. Check linked guides and test commands in your own lab before relying on an answer.