Current Implementation
Streaming Configs (services/chatService.ts)
export type StreamingVersion = 'v1' | 'v1.1'
const STREAMING_CONFIGS: Record<StreamingVersion, StreamingConfig> = {
'v1': {
fetchTimeoutMs: 30_000,
retryOnTransient: false,
retryDelayMs: 0,
},
'v1.1': {
fetchTimeoutMs: 90_000,
retryOnTransient: true,
retryDelayMs: 1_000,
},
}
export const STREAMING_VERSION_LABELS: Record<StreamingVersion, string> = {
'v1': 'Default', // ❌ labeled default but older
Shared architectural context
Your codebase, automatically mapped.
QEEK connects your repos and immediately surfaces how components communicate, what APIs are exposed, and how services depend on each other across your entire system. Context pulled directly from the code.Every engineer, PM, and AI agent works from the same verified map without anyone having to ask for it.
Architect
Last synced: 2m ago
Code wiki
Documentation you can trust
Documentation goes stale the moment it's written. Architecture overviews, directory structures, tech stack, and application flows documentataion is auto-generated and re-indexed on every sync. The whole team reads from the same living source.
Wiki
Living docs from your repos
System Diagram
Acme · generated view
Updated 2m ago
Live sync
Architectural context engine
Stop wasting tokens on discovery
Every AI coding session spends tokens understanding your system before it can do useful work. QEEK provides that architectural context upfront. Your tools spend less time exploring and more time building. Fewer redundant prompts across your team, lower compute costs, better output on the first attempt.
QEEK
AC
/auth-refactor.md
Technical spec