Ask Oynix
Four ways to ask. One memory.
The same graph answers everywhere you already work. Trace it in the visualizer, ask it in plain English, mention it in Slack, or let your own AI agent read it over MCP. The answer carries its sources every time. Three run on your engine with an API key. The fourth runs inside the agent you already use.
Graph askThe visualizer
Free · AI explanation optionalAsked: how does login work
OynixTrace
MapOverviewCross-repoclick = details · double-click = expand · scroll = zoom
Nodes
Function
Service
Class
API endpoint
Table / column
External service
How it wires up
“how does login work” · from the graph
POST /api/login routes to LoginHandler, which calls AuthService. AuthService reads the users table, checks the password through verifyPassword (a bcrypt compare), then mints a session in SessionStore.
Key pieces
LoginHandler — internal/http/login.go:24
AuthService.verify — internal/auth/service.go:88
SessionStore — internal/auth/session.go:16
Read straight from your code. Free, no AI, no key.
● graph read from your code7 nodes · 6 edgesfree · no AI
The graph is read straight from your code, so tracing it is free. No AI, no API key. Ask for a written explanation and that one part runs on your engine with your model key. Everything else stays free.