Workspace context

Context chips: workspace root, active repo, and rules count injected at tool time.

Preview — early access. Context chips show scope today; deeper multi-repo context blending is still on the roadmap.

Overview

When you ask Creytix Dev to do something, it doesn't start from a blank prompt — it shows you, as a row of chips, what workspace context is about to feed the request: which workspace root, which active site or repo, and how many of your rules are being injected. You see what the agent is working from before you send anything.

How it works

Before a request goes out, Creytix Dev resolves your active workspace root and site or repo.
It counts and injects the relevant rules for that context.
Chips display this at the top of the chat, so you can check it before you send.

Steps

•
Open a Dev chat
Start a task in Creytix Dev from the Control Panel.
•
Check the context chips
Look at the row of chips showing workspace root, active site or repo, and rules count.
•
Adjust scope if needed
Switch the active site or repo if the chips show the wrong context before sending.
•
Send with confidence
Send the task knowing exactly what context the agent is working from.

Capabilities

Workspace root chip — shows which workspace the agent is scoped to.
Active site/repo chip — shows which specific site or project is in focus.
Rules count chip — shows how many of your workspace rules are being injected into this request.
Pre-send visibility — see context before you send, not just after.

Limits & honest scope

Context chips show scope, not the full literal payload — you get a glance at what's included, not a raw dump of every injected rule.