Get started
How Praxen Inc. works
The loop Praxen Inc. runs on your stack, and the handful of things you will see in the console, from issues and threads to fix runs, escalations and autofixes.
Praxen Inc. connects to your clouds, repositories and observability tools, watches them for problems, and works each one to a verdict and a fix. You read the whole story in threads, from the console, Slack, your coding agent or the terminal.
The loop
- Connect: you connect a cloud, a repository and an observability tool, and Praxen Inc. builds a live map of your system that every agent reads. See Connect.
- Detect: checks built from your telemetry raise issues, impact assessments check each pull request against production, and risky configuration is flagged. See Detect.
- Investigate and fix: one agent works each issue with your real tools, shows its evidence, and opens the fix as a pull request you review. See Investigate and fix.
- Work from your tools: the same agent answers from your editor, terminal, CI or Slack. See Work from your tools.
The primitives
| Primitive | What it is | Where you see it |
|---|---|---|
| Context graph | The live model of your stack that clouds, repositories, and integrations feed, and every agent reads from. | Rendered as the topology. |
| Cloud account | A connected cloud provider whose resources Praxen Inc. syncs, tiers and records every change to. | Clouds in Settings; see Clouds. |
| Repository | A connected code host that agents search, read and open pull requests against, linked to the resources it deploys to. | Repositories in Settings; see Repositories. |
| Integration | A connected observability tool, chat, code host, issue tracker or coding agent that contributes tools agents call and events detection listens to. | Integrations in Settings; see Integrations. |
| Topology | The graph view of your infrastructure: resources as nodes, relationships as edges, each with its properties and change history. | Topology; see Topology. |
| Memory | Markdown files in a git repository per workspace that hold confirmed findings, so the next investigation starts from what you already know. | See Memories. |
| Check | A scheduled evaluation of a resource, built from your providers and saved queries, that raises an issue when it breaches. | A fix run's Lineage panel. |
| Issue | The single detection record: something may be wrong with a resource. A fix run gives it a verdict, confirmed or dismissed. | Its fix run thread; see Issues. |
| Impact assessment | A check of each pull request against the production resources it deploys to, posted as a comment before you merge. | The comment on the pull request; see Impact assessments. |
| Advisory | A per-resource recommendation about misconfiguration, resilience risk or an observability gap, with a fix you can hand to an agent. | The resource's panel on the topology; see Advisories. |
| Thread | A conversation with an agent that has your full context graph, which you can watch, interrupt, share and continue. | Threads; see Threads. |
| Fix run | One agent working one issue from verdict to root cause to pull request, in a single thread. | Threads with the Type filter set to Fix run; see Fix runs. |
| Escalation | One record per thing an agent needs from you, cleared when you handle it. | The Needs you preset under Threads; see Escalations. |
| Autofix | An agent-written code fix that arrives as a pull request in your repository, run by Praxen Inc.'s coding agent or a connected one such as Devin, Cursor, Factory, Conductor, Capy or Amp. | The pull request, and the thread's Lineage panel; see Autofix. |
What agents may do
Agents read by default: a run nobody has written to uses read-only access to your providers, and a cloud account marked Read-only refuses every write call. When you are in a thread, a write call to a provider passes a safety review and then waits for your confirmation before it runs. Code changes land as pull requests in your repository, and the merge is yours.
Related
- Quickstart: connect your stack and watch the first fix run in five steps.
- Threads: every thread type and how to start one from each surface.
- Fix runs: how one issue is worked from verdict to pull request.
- Work from your tools: the write gate as it applies to your coding agent and the CLI.