Semantic Search
Search files, symbols, and concepts across the entire codebase graph.
Architecture
Docs & Wiki
Session Timeline
Daily usage & savings
Cache health — sessions that tripped a cache-waste alert
Cache reads cost about a tenth of fresh input, so a session whose cache never engages pays roughly ten times over for the same context. Configure where these alerts are sent in the Notifications panel.
Sessions — per-session action timeline
Token Savings
What Codenous saved vs. a full-file-read baseline. "Hard" is measured; "Estimated" is a documented heuristic.
Breakdown by category
Top files saved by blocked re-reads
Real API cost, time, and tokens — measured per API call from Claude Code transcripts and priced per model from a versioned rate card. Spans all projects, so the sidebar project switcher does not apply here.
Spend
Onboarding
AI Chat
Ask questions about your codebase — answers are grounded in the graph.
Notifications
Where Codenous sends a message when a session trips a cache-waste alert (see the Insights panel's Cache Health section for the org-wide count).
Configured channels (admin)
The shared webhook URL / API token for each channel — set up once per workspace, not per developer.
ClickUp sender token is optional — leave it blank and alerts send using the API token above (your own identity, if that's a personal token). Set it to a dedicated service account's token to send alerts as that account instead.
Your notification target
Choose which of the configured channels you actually want alerts on, and which identifier is yours within it — a Slack/Teams member id to @mention, or your ClickUp email so alerts can be sent to you as a direct Chat message. Nothing is sent on a channel you haven't checked. An admin can set this for you too, if you'd rather ask them.
Admin
Create and maintain per-user API keys and roles.
Departments & teams
Products — group the repos that make up one product
A product is usually several repos — a frontend, a backend, a shared library — each with its own project id, so cost is only ever recorded per repo. Group them under a product and their spend is reported together; each repo keeps its own graph. A repo belongs to at most one product.
Create a key for a new user
Read scope for this key — what they can see, separate from the team above, which is where their usage is counted. Leave everything unchecked to limit them to projects they work in themselves. Granting a product covers every repo in it, including ones added to it later.
Users — click a row to view/create keys
Token pricing — override the default $/1M-token rate for a subscribed or negotiated plan
Applies to usage recorded from now on; a cost already recorded never changes retroactively.