| ▲ | e12e 4 hours ago | |
Interesting project - but you need to add some information on where the data goes. As far as I can tell, code goes to some upstream ai provider (for installing, for analyzing). Telemetry goes to some provider or local hosted solution? And then to your upstream ai provider for analysis? | ||
| ▲ | signalbright 4 hours ago | parent [-] | |
Thanks for the feedback! When you're installing Superlog, you can use any coding agent you'd like, including a local model. Your telemetry then goes into our data stores, and right now we have one DC on the US west coast. Whenever there's an error log or trace, Superlog can analyze it and prepare a resolution PR (or a note if something needs to be done manually). This can be turned off and then the incident can be sent to your own models via a webhook. We use one of the frontier models for that (it's an upstream AI provider). We're working on our own fine-tuned version of a SoTA model to minimize dependency on other AI providers. To investigate an incident, we clone the repo in our worker, and pass the repository files to a coding agent in a sandbox. The agent has an MCP that gives it access to the telemetry (logs/metrics/traces) of the project. The coding agent will then investigate the incident and prepare a patch. It hands over the patch via a tool. The worker then deterministically pushes the patch to a branch and opens the PR. This way the agent doesn't have full Git access and can't do anything it's not supposed to do in the repository. | ||