Activity
Mon
Wed
Fri
Sun
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
What is this?
Less
More

Memberships

CC Strategic AI

3.3k members • $27/month

Openclaw Labs

1.8k members • Free

KI Meetups DACH

192 members • Free

AI Essentials

6.2k members • Free

Learn Microsoft Fabric

16.9k members • Free

Escape The 9-5 Rat Race

210 members • $9/month

AI Topia

1.6k members • Free

KI Community

314 members • Free

4 contributions to CC Strategic AI
Do y want to join the challange for the Linux Root cause?
Competitions arise from security gaps News about the Linux Root Isabel! But I don't know what the prize money is !🤣 https://copy.golf/
0
0
Beautiful LLM architecture comparison option !
Have a close Look! https://sebastianraschka.com/llm-architecture-gallery/
1 like • 4d
@Charles Dove yes y should
BIG NEWS: Interview coming with creator of Graphify
Working on setting something up with him next week, hope you guys are ready!
BIG NEWS: Interview coming with creator of Graphify
1 like • 5d
Looking forward to great Knowledge Graph 😎
OneCLI - The secret vault for AI agents. Store once. Inject anywhere. Agents never see the keys.
See https://github.com/onecli/onecli This is similar to iron proxy (see also), but OneCLI seems to be much more popular. Is one of the IMO interesting tools from the "Personal Claude Assistant" project. OneCLI is an open-source gateway that sits between your AI agents and the services they call. Instead of baking API keys into every agent, you store credentials once in OneCLI and the gateway injects them transparently. Agents never see the secrets. Why we built it: AI agents need to call dozens of APIs, but giving each agent raw credentials is a security risk. OneCLI solves this with a single gateway that handles auth, so you get one place to manage access, rotate keys, and see what every agent is doing. How it works: You store your real API credentials in OneCLI and give your agents placeholder keys (e.g. FAKE_KEY). When an agent makes an HTTP call through the gateway, the OneCLI gateway matches the request to the right credentials, swaps the FAKE_KEY for the REAL_KEY, decrypts them, and injects them into the outbound request. The agent never touches the real secrets. It just makes normal HTTP calls and the gateway handles the swap.
2 likes • 5d
@Charles DoveI am also happy to be able to provide valuable posts 😎
1-4 of 4
Peter H
2
12points to level up
@petra-hirsch-8736
Bring things together

Active 42m ago
Joined Apr 18, 2026
ENTJ
Powered by