Skip to content

Releases: avinashgaurav/clientlens

Release list

v1.0.0

v1.0.0 Latest
Latest

Choose a tag to compare

View all tags
@avinashgaurav avinashgaurav released this 07 Aug 06:40
v1.0.0
0d6f70e

First tagged release of Project Wingman: an open-source AI sales copilot that lives in your Chrome side panel.

MIT licensed, self-hosted, and it runs on your own LLM keys. There is no Wingman server and no telemetry back to me.

What it does

  • Live meeting copilot. Captures Google Meet tab audio, transcribes with Deepgram, and runs agents on the rolling transcript: sentiment, agenda pacing, a coach that surfaces the next-best sentence, and a validator that fact-checks numbers before you say them. A non-intrusive overlay mirrors the cues on the Meet tab itself.
  • Pitch generation. A four-agent council (retrieval → ICP personalization → brand compliance → fact validation) turns a company name plus an ICP into a structured deck grounded in your knowledge base. Five ICP profiles ship tuned: CFO, CTO, VP Sales, RevOps, General.
  • Objection composer. Right-click any selected text, or use the Generate tab. Returns a 60 to 120 word grounded reply with inline [N] citation chips; hover shows the source quote.
  • Email council. Cold intro, follow-up and re-engage modes, with brand-voice and tone calibration passes.
  • Post-call insights. Structured summary with agenda coverage, sentiment timeline, objections and action items. One click pushes it to Zoho CRM.
  • Bring your own keys. Anthropic, Gemini, Groq, OpenRouter, or any OpenAI-compatible endpoint. The extension never holds a provider key; the backend proxies.

Be clear-eyed about what this is not, yet

  • Authentication is not wired. v1.0 assumes one rep running the backend on their own machine: the sidebar provisions a local admin and the backend runs with DEV_MODE=true. Keep that backend off the public internet. Wiring real sign-in is the top roadmap item and it is what gates a shared team deployment.
  • No Chrome Web Store listing. Load unpacked. Setup is a developer task: clone, run a FastAPI backend, supply your own keys.
  • Zoho is the only CRM wired. HubSpot and Salesforce are on the roadmap.
  • Google Meet is the only meeting surface that works end to end. Zoom and Teams are not implemented.
  • Python 3.11+ is a hard requirement. Dependency resolution succeeds on 3.9 but the backend raises TypeError at import, so it fails late and confusingly.

Notable fixes in the run-up to this tag

  • The side panel rendered blank on first open for every new user: two hooks sat below an early return in App.tsx, so React threw Rendered more hooks than during the previous render and, with no error boundary, the panel unmounted (#128)
  • A fresh clone could not sign in. setup_env.sh collected the OAuth client ID and discarded it, and the backend host placeholder meant MV3 blocked every backend request. Both are now injected into the built manifest at build time, and a production build fails closed on an unresolved backend host (#122)
  • The pitch and email agents asserted ISO 27001 and SOC 2 Type II as pre-approved facts, in a block fed to the very agent meant to catch hallucinations. Those certifications do not exist for this project. Removed; facts now come only from your KB via retrieval (#125)
  • The docs claimed a workspace-domain sign-in gate that was never implemented. Corrected, along with the host_permissions description, the health-check path and the deployment guidance (#122)
  • One identity everywhere. The shipped toolbar icon still read CL from the project's retired working name while other surfaces read PW. All brand assets now come from one generator (#124)
  • npm audit: 8 findings to zero (#130)

Getting started

git clone https://github.com/avinashgaurav/project-wingman-sales-copilot.git
cd project-wingman-sales-copilot
bash scripts/setup_env.sh
cd backend && python3.11 -m venv venv && source venv/bin/activate
pip install -r requirements.txt && uvicorn main:app --reload --port 8000
cd ../extension && npm install && npm run dev

Then load extension/dist/ at chrome://extensions with Developer mode on. Full instructions, including the security posture you should read before deploying anything, are in the README.

No build artifact is attached deliberately: the extension bundle embeds your own backend URL and OAuth client ID, so a prebuilt zip would be wrong for everyone but me.

Contributing

Issues and pull requests welcome, including small ones. CONTRIBUTING.md covers setup and what I will likely say no to. The public backlog with acceptance criteria is #113.

Assets 2
Loading