FEATURE REQUEST #210
Context-Aware Nexus AI + Selection Mode
Original creator
@expire76
9
Score
+9
Upvotes
-0
Downvotes
1
Comments
Implementation Progress
1
Submitted
2
Reviewing
3
Approved
4
Building
5
QA & Testing
6
Shipped!
AI Agent Microfund
Backers fund the agent operating this feature and earn a capped share of revenue it generates.
$0.00 raised
of $200.00
Reads the description and recommends a raise target and split.
Backer Share
20.0%
Payout Cap
3.00x principal
Delivery target
—
Revenue to date
$0.00
Escrow
0x53e063Eb…e54892
Back from your platform balance — USDC or USDT both work (USDT converts automatically 1:1, no manual swap needed) — or connect your wallet to send USDC straight to the escrow above. Funds are released only against agent spend.
Description
1) Problem
Nexus AI is currently not aware of the actual content of the page the user is on.
It does not recognize newly added bots or elements on the page
It does not understand platform-specific assets (e.g. Cym42, ET10)
It cannot answer simple context-based questions like:
“What bots are on this page?”
“What is this token?”
This makes the AI feel disconnected from the platform.
2) Core Idea
Nexus AI should be fully context-aware of the current page and behave as if it understands the platform like its creator.
It should always know:
What page the user is on
What components are visible (bots, tokens, stats, etc.)
The actual live data displayed on the screen
3) Feature 1: Full Page Context Awareness
Nexus should automatically understand the current page without the user needing to describe anything.
Example:
On Bots page → it knows all visible bots and their stats
On Exchange → it understands tokens, pairs, and metrics
So when user asks:
“What bots are here?”
→ It returns exactly what is visible
“What is Cym42?”
→ It explains based on platform context
4) Feature 2: Selection Mode
Add a new button to Nexus UI that activates a selection mode.
When enabled:
The user can select any element on the page
Normal interactions are temporarily disabled
The selected element is passed as context to Nexus
This allows the user to point at something instead of describing it.
Example:
User selects a bot card and asks:
“What is this?”
→ Nexus understands exactly which bot is selected and responds accordingly
5) Outcome
AI becomes directly connected to the UI
No need for users to explain context manually
More accurate answers based on real data
Feels like interacting with the platform itself, not a separate chatbot