Skip to content

feat(kilo cloud) Ability to add system message at the top - #5142

Open
St0rmz1 wants to merge 1 commit into
mainfrom
feat/system-message-banner
Open

feat(kilo cloud) Ability to add system message at the top#5142
St0rmz1 wants to merge 1 commit into
mainfrom
feat/system-message-banner

Conversation

@St0rmz1

@St0rmz1 St0rmz1 commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds a static banner at the top of the kilo cloud screen.

Verification

  • [ ]

Visual Changes

Before After

Reviewer Notes

import { Megaphone } from 'lucide-react';

const SYSTEM_MESSAGE_TEXT = 'Important security notice';
const SYSTEM_MESSAGE_URL = 'https://blog.kilo.ai/';

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: Link text promises a specific notice but the URL is the blog root

The visible label is "Important security notice", which sets the expectation of a specific advisory, but SYSTEM_MESSAGE_URL points at https://blog.kilo.ai/ (the blog homepage). Users clicking it land on a generic listing page with no obvious security notice. If this is a placeholder, please point it at the actual post URL before merging.


Reply with @kilocode-bot fix it to have Kilo Code address this issue.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Text and URL pending. this was just a pre PR to push the branch in case someone needs to take over the branch.

@@ -0,0 +1,18 @@
import { Megaphone } from 'lucide-react';

const SYSTEM_MESSAGE_TEXT = 'Important security notice';

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SUGGESTION: Hardcoded message requires a redeploy to change or remove

Because SYSTEM_MESSAGE_TEXT and SYSTEM_MESSAGE_URL are compile-time constants, updating the message (or taking it down once the notice is no longer relevant) requires a code change and a full redeploy. For a system/announcement banner — typically used for time-sensitive comms — consider sourcing these from an env var (e.g. NEXT_PUBLIC_SYSTEM_MESSAGE_TEXT / ..._URL) and rendering nothing when unset, so the banner can be changed or removed via config. Fine to keep hardcoded if this is intentionally a one-off notice.


Reply with @kilocode-bot fix it to have Kilo Code address this issue.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is as per design for now.

@kilo-code-bot

kilo-code-bot Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Code Review Summary

Status: 2 Issues Found | Recommendation: Address before merge

Executive Summary

New topbar system-message banner is safe and leak-free, but its "Important security notice" label links to the blog root and its content is hardcoded, requiring a redeploy to update or remove.

Overview

Severity Count
CRITICAL 0
WARNING 1
SUGGESTION 1
Issue Details (click to expand)

WARNING

File Line Issue
apps/web/src/components/shared/SystemMessageBanner.tsx 4 "Important security notice" links to https://blog.kilo.ai/ blog root instead of a specific notice URL

SUGGESTION

File Line Issue
apps/web/src/components/shared/SystemMessageBanner.tsx 3 Message text/URL are hardcoded constants; consider env-var config so the banner can be changed or removed without a redeploy
Files Reviewed (2 files)
  • apps/web/src/app/(app)/components/AppTopbar.tsx - 0 issues
  • apps/web/src/components/shared/SystemMessageBanner.tsx - 2 issues

Fix these issues in Kilo Cloud


Reviewed by kimi-k3 · Input: 44K · Output: 7.3K · Cached: 394.3K

Review guidance: REVIEW.md from base branch main

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants