Test Trajbl in your own AI app in minutes.

You are my coding agent. Safely prepare a Trajbl integration for this chat app backend.

Goal:
Add Trajbl as an optional, fail-open context-compression step immediately before the app sends chat messages to its LLM provider.

This module works with apps that use OpenAI-style chat message arrays, including OpenAI, Gemini adapters, Ollama OpenAI-compatible endpoints, OpenRouter, LiteLLM, vLLM, LM Studio, LocalAI, and similar backends.

Strict safety rules:
- Do not call a real LLM provider during setup.
- Do not send private app data to Trajbl during the first smoke test.
- Do not print, log, commit, screenshot, or hardcode the Trajbl API key.
- Keep the API key in a server-side/local environment file only.
- Keep the integration OFF by default until I explicitly approve it.
- If Trajbl fails, times out, returns invalid JSON, or changes protected hard context, pass the original messages through unchanged.

Step 1: Inspect read-only first.
Find the narrowest point where final chat messages are sent to the provider. Do not edit files yet.

Expected integration shape:
app builds messages
-> optional Trajbl wrapper
-> POST https://api.neurobiz.me/v1/compress
-> provider receives compressed messages
-> app receives provider response

Step 2: Prepare environment configuration.
Find the existing .env or local environment config. If it exists, append missing variables without overwriting existing values. If it does not exist, propose the safest local env file.

Add this placeholder, then tell me exactly where to paste the API key value I received from the Trajbl page:
TRAJBL_PROXY_ENABLED=0
TRAJBL_API_URL=https://api.neurobiz.me
TRAJBL_API_KEY=PASTE_TRAJBL_KEY_HERE
TRAJBL_COMPRESSOR=stable
TRAJBL_COMPRESSION_MODE=adaptive
TRAJBL_TIMEOUT_MS=3000
TRAJBL_FAIL_OPEN=1
TRAJBL_LOG_CONTENT=0

Step 2b: Prepare local metrics.
Create a local project folder named .trajbl if it does not exist.
Configure the wrapper to append one JSON line per Trajbl attempt to:
.trajbl/metrics.jsonl

The metrics file must not contain prompt text, user messages, retrieved documents, API keys, or provider responses.
Only write numeric/status fields such as timestamp, enabled, raw_input_tokens, compressed_input_tokens, token_savings_percent, compression_latency_ms, fallback_used, fallback_reason, compression_mode, hard_context_preserved, client_id if available, and provider name if safe.

Step 3: Verify safely.
After I paste the API key locally, run only safe checks:
- GET https://api.neurobiz.me/health
- GET https://api.neurobiz.me/v1/usage with the Bearer key
- POST https://api.neurobiz.me/v1/compress with a tiny synthetic dummy payload
- use a fake downstream provider for any OFF vs ON smoke test

Step 4: Report before implementation.
Give me a short report:
- API reachable: yes/no
- Key valid: yes/no
- Compression works on dummy data: yes/no
- Savings metric visible: yes/no
- Local metrics path created: yes/no, exact path
- No secrets exposed: yes/no
- Proposed files to change
- Rollback plan
- Exact command or setting to turn Trajbl ON later

Do not implement permanent integration until I write exactly:
APPROVE TRAJBL INTEGRATION