Investigate and fix

An agent works each problem with your real tools and shows its evidence, then opens the fix as a pull request you review.

Connect is what Praxen Inc. sees and Detect is what it spots. Investigating is where an agent works the problem with your observability tools, your code and the topology, and writes up what it found. Every tool call and result is stored in the thread, and answers cite their sources, so you can check any number the agent puts in front of you.

Threads are the surface. A fix run works one issue from verdict to pull request, an escalation records what only a person can do, and an autofix is the pull request that lands in your repository.

Threads

Every agent run, from the console, Slack, the CLI or the API. Watch it, stop it, share it and continue it.

Fix runs

One agent per issue reaches the verdict, traces the cause and opens the pull request, in a single thread.

Escalations

The one list of what agents need from you: one record per ask, cleared when you handle it.

Autofix

Agent-written fixes arrive as pull requests in your repository. You review and merge.

Detect for the checks and alerts that start a fix run.
Work from your tools for reaching the same agent from your coding agent, the CLI and Slack.

Signals

Praxen Inc. learns how the telemetry of each cloud account and integration is shaped, watches what your application does with queries in your own conventions, and opens an issue when one changes for the worse.

Threads

Every agent run is a thread you can watch, interrupt, share and continue, from the console, Slack, the CLI or the API.

Investigate and fix

Related