regenic
Health Uyari
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Uyari
- process.env — Environment variable access in apps/api/src/catalog-probe-cache.ts
- process.env — Environment variable access in apps/api/src/channel-plugins.ts
- process.env — Environment variable access in apps/api/src/customer-business-gateway.ts
- network request — Outbound network request in apps/api/src/customer-business-gateway.ts
- process.env — Environment variable access in apps/api/src/dsh-api.service.ts
- process.env — Environment variable access in apps/api/src/health.controller.ts
Permissions Gecti
- Permissions — No dangerous permissions requested
Bu listing icin henuz AI raporu yok.
Unify work messages across channels and bring them into the AI you already use. Open-source, local-first, with pluggable connectors.
Regenic
Let your AI work across every channel your team talks in.
Work conversations are scattered across Feishu, Slack, WhatsApp, and more. When you want AI to help you catch up or reply, you usually have to dig through each app and paste the history in by hand.
Regenic fixes that. It collects work messages from all your channels on your machine and exposes them to AI tools like Cursor through MCP. Your AI can then search across channels, summarize progress, and draft replies for you.
Regenic is open source and local-first. Sources plug in through connectors: use an existing plugin, or write your own against a shared standard.
Quick start · Connectors · MCP setup · Docs
Use cases
| Use case | Ask your AI |
|---|---|
| Search across channels | “Who mentioned the contract payment date last week?” |
| Catch up on a project | “Summarize this week's updates on the project from every group chat.” |
| Check a customer commitment | “What did we promise this customer? Show me the original messages.” |
| Draft a reply | “Based on our earlier conversation, draft a reply.” |
Your AI only sees conversations you've connected and authorized. Results include where each message came from, so you can check the original.
Features
- One place for every channel. Conversations from different apps are stored and searched together, so you stop switching between them.
- Extensible sources. Connectors follow one standard and support file imports, webhooks, and polling. If no plugin fits, write your own.
- Bring your own AI. MCP clients such as Cursor can query conversations directly; scripts and other tools can use the API.
- Traceable answers. Every result carries its channel, conversation, and message IDs, so you can always go back to the source.
- Sending is opt-in. Reading and sending are authorized separately, and sending also depends on the connector.
- Your data stays local. Messages are stored on your machine and can be exported as Markdown or JSONL. If you use an external AI, retrieved content is sent to that provider.
Quick start
Requires Node.js 20+ and pnpm 9. Run from source:
git clone https://github.com/regenic-ai/regenic.git
cd regenic
pnpm install
pnpm dev:desktop
- Connect a source. For Feishu, install and sign in to
lark-cli, then open Engine → Feishu → Install and choose conversations. - Connect your AI. Follow the MCP setup guide to let your MCP client search and read those conversations.
- Ask about your work. Try “Summarize the latest project updates and cite the messages.”
For DSH, plugin installation, Docker, and CLI commands, see the setup and CLI reference.
Connectors
Feishu, DSH, and Cursor are built in; Slack and WhatsApp ship as separate plugins. Any other source can plug in through the same standard.
| Source | Available through | Scope |
|---|---|---|
| Feishu | Built in | Sync selected groups and DMs; send text using your authorized account |
| DSH | Built in | Read local agent sessions, send prompts, and create sessions in supported modes |
| Cursor | Built in | Read and run local SDK agent sessions; not IDE chat history or Cloud Agents |
| Slack | Separate plugin | Install separately; see the plugin's supported capabilities |
| Separate plugin | Install separately; see the plugin's setup and limitations | |
| CSV / JSONL | CLI import | Import exported messages with a field mapping |
Need another source? Start with the connector guide and example plugins. A connector can be read-only; it does not have to implement a full chat client.
Current scope
Regenic is currently for individual use; team sharing is on the roadmap. What you can read, how it syncs, and whether you can send all depend on the connector and the permissions you grant.
The Context Search MCP is read-only: it does not approve or send messages. Third-party plugins run in the kernel process, so install only plugins you trust. See the roadmap and security notes.
Documentation and contributing
All docs · Setup & CLI · Connector development · MCP · Architecture · Executors
Bug reports, connector contributions, and feedback are welcome in Issues. For implementation PRs, follow the product boundaries and cite the relevant RFC.
Please follow the Code of Conduct. Report security issues through a private advisory.
License
MIT. Methodology in regenic-book remains CC BY-NC 4.0 where applicable.
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi