Skip to main content

nimbus chat

Ask questions about your codebase conversationally. Nimbus retrieves context from your indexed codebase and answers with file and line citations.

Usage​

nimbus chat

Or from inside the REPL:

nimbus › chat

How it works​

After launching, you enter a sub-loop:

nimbus chat  ·  ask anything about your codebase · type exit to return

you › how does the authentication middleware work?

╭─────────────────────────────────────────────────────────────────╮
│ The auth middleware is in src/middleware/auth.ts [auth.ts:1-45]. │
│ It checks for a Bearer JWT in the Authorization header, verifies │
│ using jsonwebtoken with the JWT_SECRET env var [auth.ts:12-18], │
│ and attaches the decoded user object to req.user [auth.ts:22].  │
│ Expired tokens return 401. Invalid tokens return 403.           │
╰─────────────────────────────────────────────────────────────────╯

you › where is the JWT secret configured?

╭─────────────────────────────────────────────────────────────────╮
│ The JWT_SECRET is loaded in config/env.ts [env.ts:8]. It's      │
│ required — the app throws on startup if it's missing [env.ts:9].│
│ For local dev, set it in .env. In production it's a Railway env │
│ variable per the CI config [.github/workflows/deploy.yml:31].   │
╰─────────────────────────────────────────────────────────────────╯

you › exit
  returning to nimbus ›

Each answer retrieves the 10 most relevant chunks from your ChromaDB index, reasons over them, and returns an accurate response with [file:line] citations. Follow-up questions use prior context.

Commands​

CommandAction
<question>Ask anything about the codebase
exitReturn to the main nimbus prompt
backAlias for exit

Use cases​

  • Understanding a new codebase on day one
  • Tracing how a feature flows through the system
  • Finding where something is implemented before writing related code
  • Asking "why was this implemented this way?" (Nimbus checks git blame context in memory)