Changelog

Connect a GitLab group, on GitLab.com or self-managed. Praxen Inc. reads its code and links each project to what it deploys in the context graph.

It watches pushes and pipelines, and opens merge requests from investigations, the same way it opens pull requests on GitHub. You can also sign in to Praxen Inc. with GitLab.com. See the GitLab integration.

Praxen Inc. is now an app in ChatGPT and Codex. Ask what changed, read logs and metrics, trace dependencies and investigate issues, all from your own code and infrastructure. Add the Praxen Inc. plugin, sign in, pick a workspace and ask.

Views in the conversation

Answers come back as views in the chat: issue cards, log lines, metric charts, recent changes and dependency graphs. Every resource in the workspace can be drawn as one context graph, with active issues marked, and an active-issues panel sits beside the conversation. Select anything in a view to ask about it next.

Tools named for the job

The plugin gives ChatGPT one tool per question you would ask: what changed, what it logged, what it reaches. ChatGPT picks the right one, and every answer links back to the evidence in Praxen Inc.

A guided first run

The first time you ask, Praxen Inc. confirms the connection, picks your workspace, summarises what is connected and suggests a few first questions.

Issue channels in Slack

An investigation at the severity you choose now opens its own public Slack channel. Praxen Inc. posts milestones there, answers people in threads, names the channel after the issue and bookmarks the issue, the thread and the pull request. You choose who joins, from the Slack integration settings or from Slack itself.

Connect Amp and it can write Praxen Inc.'s fixes. Praxen Inc. investigates and writes the brief, then an Amp agent fixes the code and opens the pull request.

Amp joins Devin, Cursor, Factory, Conductor and Capy. The token is checked with Amp before it's saved, and if a hosted agent fails, Praxen Inc. falls back to its own. See the Amp integration.

Connect an Amplitude project with its API key and secret key. Agents can query its events, funnels and retention during an investigation.

Praxen Inc. also checks the project's event volume once a day, so a drop in tracked events becomes an issue. See the Amplitude integration.

Connect a Braintrust organization with an API key or service token, including organizations on the hosted EU data plane. Agents can search LLM traces, read a trace as a span tree, query logs and evals with SQL, and compare an experiment with its baseline.

Praxen Inc. also watches each active Braintrust project for changes in errors, latency, tokens and cost. See the Braintrust integration.

Connect a New Relic account with one User key. Agents investigate with NRQL, traces, entities and alerts, and Praxen Inc. watches the account on its own.

New Relic alert issues open Praxen Inc. issues, and the resources that report to the account are linked in the context graph.

Praxen Inc. catches issues across your Cloudflare apps, follows the connections between Workers, databases, queues and storage, and finds the root cause using your code, logs and recent changes. When the fix is in your code, it opens a pull request for your review. See Praxen Inc. for Cloudflare.

One read-only token

Connect with a single Cloudflare API token. The create-token link pre-fills every permission Praxen Inc. needs.

Every Worker and everything it binds to

Workers, Durable Objects, D1, R2, KV and Queues land in one context graph, linked by their bindings, so an error in one Worker can be traced to the database or queue behind it.

Every workspace can now connect a Google Cloud project. Setup is one continuous flow and keeps going in the background once you've granted access.

Praxen Inc. investigates Cloud Monitoring alerts as they fire, and maps and monitors load balancers, data services and pipelines alongside the rest of your stack. See the Google Cloud integration.

Hard incidents have more than one lead. Any chat or investigation thread can now become a fleet: a lead agent and a team of member agents work the same production problem in parallel, each chasing a different lead.

A shared board

The agents coordinate on a shared git message board. They claim work, post evidence, and a second agent confirms a finding before it counts. People stay the authority over what the fleet concludes.

Fleets in the console

The thread sidebar has a Fleet section with the lead, every member, their lanes and the board. The threads list shows which threads ran as a fleet.

Fleets are available on paid plans.

Connect incident.io with one API key. Every new incident starts a Praxen Inc. investigation, and the findings are posted in the incident's Slack channel.

Escalations Praxen Inc. can't fix page on-call through incident.io's own alert routing. Praxen Inc. sets up the incident.io workflow for you. See the incident.io integration.

Connect a LangSmith workspace with one service key. Agents can investigate your LLM traces, and LangSmith alert rules open Praxen Inc. issues.

Praxen Inc. also watches each tracing project for changes in errors, latency, cost and tokens. See the LangSmith integration.

Praxen Inc.'s memory is now a git repository of markdown files, one per workspace, with full history. Agents write to it as they work and it syncs at the end of every turn. You can read it, edit it and add to it from the console, the API and MCP.

Browse it like code

Open Memory in the console for a file tree and a markdown reader, with MEMORY.md first. Every memory has its own address, and edits happen in a slideover with Write and Preview tabs.

One home for standing instructions

Slack channel instructions and repository instructions for pull request reviews are now memory files, next to everything else Praxen Inc. knows about your workspace.

Learns from how work ended

A nightly update writes the day's note, removes entries that turned out wrong and rewrites MEMORY.md. It reads how work ended, such as merged or closed pull requests and decisions on issues, and writes a lesson only when a pattern repeats.

Connect a Depot organization with one token. Investigations can read container builds, GitHub Actions jobs and logs on Depot runners, and Depot CI runs, so a failing build is part of the evidence.

Depot projects join the context graph with their own monitoring, and repositories that build on Depot are linked to their project from their CI and build files. See the Depot integration.

Connect a Neon organization and Praxen Inc. adds your projects, branches, computes and databases to the context graph. Every service that reaches a Neon compute is linked to it, so a DATABASE_URL no longer ends at an unknown external host.

Investigations get read-only SQL and query stats. Account checks and per-project consumption charts watch compute, transfer, storage headroom and failed operations. See the Neon integration.

Catch issues before they reach production. Praxen Inc. assesses every pull request against the live infrastructure it touches: config, capacity, dependencies and telemetry. You get one comment with the evidence and a verdict on whether the change is safe to merge. See impact analysis.

Missing observability, as a suggestion

When a change ships code you could not debug in production, Praxen Inc. posts a separate comment proposing the logs, metrics or traces to add, linked to the line. When there is nothing worth adding, it stays quiet.

An honest blast radius

The assessment names the resources it could not assess instead of dropping them, and shows no number when it made no assessment.

Connect a Capy API key and Capy writes the fix. Praxen Inc. investigates the issue and writes the brief, then Capy opens the pull request in the project that holds the repository.

Capy joins Devin, Cursor, Factory and Conductor as a coding agent Praxen Inc. can hand fixes to. When the repository isn't in a Capy project, you get an email and a Slack message saying so.

Keep shipping while Praxen Inc. watches your Vercel apps. Install Praxen Inc. from the Vercel Marketplace and your projects, deployments, domains and logs land in one context graph. Agents catch regressions, find the root cause with evidence, and open a pull request with the fix for your review. See Praxen Inc. for Vercel.

Start in Vercel, finish in Praxen Inc.

An install started on the Marketplace carries through sign-up and workspace creation, and asks which workspace to use when you have more than one.

Clearer token errors

A Vercel token scoped to a single project is rejected with an explanation of the scope Praxen Inc. needs.

Linked accounts

Each member can link their Slack and GitHub accounts from a new Linked accounts tab. Praxen Inc. uses them for message attribution and commit authorship, even when the emails differ.

PostHog error tracking

Praxen Inc. receives PostHog error tracking events for new, reopened and spiking issues through a signed webhook, and watches the numbers on your PostHog dashboards.

Nobody should be on call. Praxen Inc. connects your code, infrastructure and observability data, investigates every issue and opens a pull request with the fix. When code can't fix it, you get the root cause and a recommendation.

A setup thread that connects your stack

New workspaces start in a chat where Praxen Inc. already knows your stack from a scan of your company's domain. It offers one connection at a time: clouds, tools, GitHub, Slack. After each one it takes a first look, showing what runs there and a 24-hour health chart, then suggests what to connect next.

A pull request queue per repository

Each repository has its own queue of open Praxen Inc. pull requests, with a limit you set per repository, so a backlog in one repository never holds up another. Admins can also have new Praxen Inc. pull requests opened as drafts.

Praxen Inc. could already see your Convex deployments, logs and metrics. Now agents can read the production data too: list a deployment's tables, read a table's newest documents, or run a one-off read-only query.

No local MCP server needed: the same reads work from every investigation. See the Convex integration.

Pull requests Praxen Inc. opens now carry a short narrated, subtitled video in the description: the cause, the change, and how it was validated. Review the fix in a minute before you read the diff.

Connect PostHog with OAuth, one project at a time. Investigations read your product analytics through read-only tools, so a spike in errors can be checked against what users actually did.

Every connected project is checked daily for issues in its top events and its pinned dashboard trends, within the project's API budget. See the PostHog integration.

The sidebar lists every pull request Praxen Inc. has open, with line counts, CI and review state, and filters for approved, failing CI and awaiting review. Each pull request has its own page, where you can merge or close it.

Connect Trigger.dev and failing background jobs become Praxen Inc. issues, one per error group per environment. Finished deployments show up as events, so a failure can be tied to the deploy that caused it.

Agents get read-only tools over your runs, limited to what the API key allows. The integration settings show the webhook URL and take the signing secret. See the Trigger.dev integration.

Praxen Inc.'s commits are now authored by the teammate who asked for the change, with Praxen Inc. as co-author. Platforms that only build commits from team members, like Vercel on private team repositories, now build Praxen Inc.'s pull requests too. With no linked GitHub account it falls back to the workspace owner, then the Praxen Inc. bot, and a workspace can choose who Praxen Inc. commits as.

See exactly what the agent read

Every context item under a thread message now opens to show it as the agent read it: issues, cloud accounts, integrations, repositories, memories and resources, with credentials redacted.

Every issue Praxen Inc. finds is now worked by a single agent. It reads the evidence with read-only tools over your telemetry and the context graph, and decides whether the issue is real. When the confirmed cause is a code defect in a connected repository, it writes the fix and opens the pull request in the same investigation.

A clear outcome when there is no fix

When a fix is out of reach, such as an unreachable repository, infrastructure code outside your connected repositories or a cause outside your systems, the investigation records the reason and a plain next step on the issue as an escalation.

Your coding agent writes the fix

With a coding agent connected, the confirmed fix goes to it. If a hosted agent rejects its credential, Praxen Inc. writes the fix itself.

A second look at dismissed issues

A dismissed issue that keeps recurring is looked at again, with a longer wait each time it is dismissed again. A dismissal is refused when its evidence does not rule out an incident, and a person's "no incident" stays final.

Connect Pydantic Logfire and investigations can go from a failing route to the exact span that threw, with read-only SQL for everything else.

Praxen Inc. watches each project's error rate, request volume and p95 latency like the other observability integrations, and names the service behind a rise in errors. See the Logfire integration.

Connect Grafana Cloud, or self-hosted Grafana, with a stack URL and a service account token. Praxen Inc. adds a contact point and a catch-all notification route to the stack, so every existing alert rule, and every rule you create later, reaches it with no per-rule setup. Your own alert delivery stays as it is.

Investigations can query dashboards, datasources, alert rules and annotations. If the contact point or route is removed, Praxen Inc. puts it back. See the Grafana integration.

Connecting AWS used to mean one region per connection. Now one connection covers any set of regions, or all of them, including regions you enable on the account later. Change the regions from the account at any time, with no CloudFormation changes.

CloudTrail and alerts in every region

New connections get a multi-region trail, and each selected region gets its own alert subscriptions. A CloudTrail event resyncs only the regions it touched.

Blast radius on issues and threads

The blast radius from pull request reviews now shows on issues and thread artifacts too, and agents can ask for it. It follows each relationship in the direction a fault travels, so it reaches the consumers two hops downstream that a fault degrades.

Every connection, with its evidence

A Connections tab on every resource lists its edges with the connected resource, the direction, how the link was discovered and the evidence behind it, such as the environment variable that created it.

Connect ClickHouse Cloud with an API key ID and secret, and your organisation's services join the context graph with their state, region and endpoints. Services that reach them through DNS records or environment variables are linked to them.

A check flags unhealthy services, and investigations get ClickHouse tools for the service inventory, live metrics and the audit log. See the ClickHouse integration.

Connect a Convex team with a team access token and its projects and cloud deployments join the context graph, synced every 15 minutes. Services whose environment variables point at a convex.cloud or convex.site hostname are linked to the deployment behind it.

Investigations can read a deployment's function logs. Each read uses a short-lived deploy key scoped to that read, which Praxen Inc. deletes afterwards. See the Convex integration.

Connect Linear with an API key. It's the first issue tracker Praxen Inc. connects to: agents read your teams, projects and issues in any thread.

From an investigation, Praxen Inc. can file a Linear issue with the evidence in its description, update its state, priority or assignee, and comment with findings. Issues filed from a thread link back to it. See the Linear integration.

Connect Turso with a platform API token and your database groups and databases join the context graph, synced every 15 minutes. If the token reaches more than one organisation, you pick which one to connect.

Checks watch your organisation's usage, and the token is validated and can be rotated like every other connection. See the Turso integration.

Resources that report to Datadog, Sentry, Better Stack, Honeycomb or Axiom are now linked to that provider in the context graph, using the provider's own API as evidence. Before, the graph only knew about a provider when a resource carried its URL in an environment variable.

Datadog and Sentry

Hosts, databases, functions and queues that report through the Datadog agent or its AWS integration are linked to Datadog. Resources and repositories that send events to Sentry are linked to Sentry, refreshed every hour.

Better Stack, Honeycomb and Axiom

Resources watched by Better Stack monitors are linked to Better Stack, and resources whose names match a Honeycomb or Axiom dataset are linked to that provider.

Severity on every issue

The issues list has a severity column and filter, and each issue shows its severity in the header. Duplicates are hidden by default.

Connect OpenStatus with one API key. Praxen Inc. adds a webhook channel to your workspace, so every monitor failure, degradation and recovery reaches it as an alert.

Monitors and status pages join the context graph, uptime checks run alongside the other providers, and investigations can read monitors, response logs, status pages, status reports and maintenances. See the OpenStatus integration.

Connect Mixpanel with a service account and Praxen Inc. finds every project the account can reach, so you pick the ones to connect. It's the first product analytics integration: an investigation can check whether signups dropped after a deploy.

Agents can query event volumes, funnels, retention and saved Insights reports, and annotate charts. A daily check watches event volumes for tracking breakages. See the Mixpanel integration.

Connect a Railway workspace with OAuth or a workspace token and Praxen Inc. syncs its projects, environments, services, deployments, volumes and domains into the context graph. Pull request environments are left out.

Deployments are watched through webhooks, service metrics are checked for issues, and investigations can read logs and use Railway tools. See the Railway integration.

Connect GitHub and Praxen Inc. opens a pull request in one of your repositories within about a minute. It adds Praxen Inc.'s instructions to AGENTS.md, CLAUDE.md, Copilot instructions and Cursor rules, and creates AGENTS.md when there are none, so the coding agents you already use know about Praxen Inc.

One per connection

The pull request opens once, for a new GitHub connection, and Praxen Inc. skips archived and empty repositories when it picks where to open it.

Follow it from the console

The console shows the follow-up work after the first pull request as it happens, and you can cancel it.

Ask the agent to watch something

Ask the agent to keep an eye on a CI run or a release and it tells you what it is watching, then ends its turn. When the GitHub event lands, the thread wakes up with the result. Watches expire after a day by default.

Sending a message while the agent was working used to cancel its turn and throw the work away. Now the composer stays live: your message is picked up at the agent's next step and shown in the transcript where the agent read it.

One button to stop or send

Stop and send share one button. Start typing and it becomes send; clear the text and it goes back to stop. Esc stops the turn.

Answers that reach the agent

Answers to the agent's questions and requests are tracked until the agent receives them, so one lost on a dropped connection shows as failed. Delivery receipts appear only when something goes wrong.

A workspace from the first sign-in

Signing up creates your workspace straight away, so you land in Praxen Inc. ready to connect your first provider.

Connect Conductor and it can write Praxen Inc.'s fixes. Praxen Inc. hands over the plan, a Conductor agent works on your repository in a cloud workspace, and the change comes back as a pull request.

Conductor joins Devin, Cursor and Factory. The API key is checked with Conductor before it's saved, and you can make Conductor the workspace's default. See the Conductor integration.

Connect Modal with the token ID and secret Modal issues for CLI login, and your environments, apps, functions, sandboxes, volumes and queues join the context graph. A repository is linked to the Modal app its CI deploys, and Cloudflare DNS records that point at a .modal.run endpoint resolve to the app behind it.

Investigations get Modal tools and a digest of each app's logs. Checks watch error log volume and queue depth against your account's history. See the Modal integration.

Connect a Supabase organisation with OAuth or a personal access token and Praxen Inc. adds every project to the context graph: databases and read replicas, edge functions, branches, storage buckets, auth, realtime and the REST API, synced every 15 minutes. Services that reach a project through a supabase.co hostname in their environment variables are linked to it, and Cloudflare Hyperdrive configs are linked to the database they point at.

Each project gets dashboards, logs and agent tools, with checks on edge 5xx rate, Postgres errors, auth failures, function errors and request volume. See the Supabase integration.

Every issue, investigation, fix and check now knows its neighbours. A lineage graph on the issue's Overview tab draws the chain from the check or change that raised it, through the investigation, to the fix and its pull request.

Every step opens in place

Click any card in the graph to open it in a panel. Duplicate issues point to the root issue that holds the investigation.

In the API, CLI and MCP

The same chain is available for any issue, check, thread, fix or pull request from the API, the CLI and Praxen Inc.'s MCP server.

CI failures become issues

A failing GitHub Actions run on a connected repository now becomes a Praxen Inc. issue with the repository attached. Repeat failures of the same workflow fold into one issue, and a green run resolves it. Praxen Inc. reads the failed jobs, steps and check annotations, and a confirmed failure gets an investigation.

The full analysis, one click from the comment

Review comments open with a link to the full analysis on praxen.page: the complete write-up, interactive charts and full log excerpts. Praxen Inc.'s own pull requests link to their whole run the same way.

Connect Better Stack and its incidents become Praxen Inc. issues. Praxen Inc. sets up the outgoing webhook when you connect, and each incident is investigated with its cause and the monitor's response times by region around the time it fired.

Agents can read your monitors, incidents, heartbeats, status pages and telemetry sources. Checks watch availability, incident volume, response time and monitors that are down. See the Better Stack integration.

Mention Praxen Inc. in Slack and it reacts straight away, shows that it's thinking and streams its reply as it writes. It appears in Slack's Agents tab with suggested prompts.

Live progress

Long turns post one status message and update it as each step completes. If a turn fails, Praxen Inc. says what happened and how to resume.

Joins conversations it can help with

In channels it belongs to, Praxen Inc. replies to messages it can help with even when nobody mentions it. Set a channel to mention-only to turn this off.

Pull requests report back to the thread

When a fix starts from a Slack thread, the thread gets the pull request link, CI failures and their fixes, review replies, and a reaction when it merges.

Duplicate issues share one investigation

Every new issue is checked against the open ones in your workspace. A confirmed duplicate is linked to the original and shares its investigation. Log lines are grouped by their shape, so an unfamiliar ID format no longer opens a new issue or reopens an old one.

Praxen Inc. now reviews every pull request for its impact on production. It follows the context graph from the repository to the resources the code ships to, checks the change against live topology and telemetry, and gives a verdict with the evidence and the affected resources. The verdict lands as the Praxen Inc. production impact check, which you can require in branch protection.

Repositories linked to what they deploy

Praxen Inc. reads Terraform, CloudFormation, Pulumi, CDK and deploy manifests such as wrangler.jsonc, fly.toml, vercel.json and render.yaml to link each repository to the resources it deploys.

Your rules per repository

Steer reviews for a repository with your own instructions. When a later push addresses a flagged concern, Praxen Inc. marks it resolved.

Praxen Inc.'s pull requests take feedback

Comment on a pull request Praxen Inc. opened and it answers or pushes the change you asked for. Reply in the Slack thread where it was announced and it responds there. When CI fails on its branch, it reads the failed checks and pushes a fix. It follows your repository's AGENTS.md, CLAUDE.md and Cursor rules, and the commit message style in your history.

Connect a PlanetScale organisation with OAuth and Praxen Inc. adds your databases and branches to the context graph, for MySQL and Postgres alike. Services that reach a PlanetScale branch are linked to it by their connection host, so an error in a Worker or a container can be followed to the exact branch behind it.

Investigations read Query Insights: query errors, latency and the windows where latency moved. Praxen Inc. never connects to your databases or holds database credentials. See the PlanetScale integration.

Your coding agent can now use the tools Praxen Inc.'s own agents use. Connect Claude Code, Cursor, Codex or any MCP client to Praxen Inc.'s MCP server and ask about production without leaving the editor.

Ask from the editor

Ask what errored in production for the service a pull request touches. The agent reads the context graph across your clouds, runs queries against your connected observability providers and searches your repositories.

Scoped to your permissions

Every tool is checked against your permissions, and only tools Praxen Inc. has listed for outside use are available.

Alerts and detections are one list of issues

Everything Praxen Inc. detects and every alert your providers forward now lands in one place as issues, with one lifecycle. The same problem firing again is one issue with an occurrence count.

Connect Factory and it can write Praxen Inc.'s fixes. Praxen Inc. investigates and writes the brief, then Factory fixes the code and opens the pull request.

Factory joins Devin and Cursor. Paste an API key from Factory's settings and it's validated before it's saved. Set Factory as the workspace's default for fixes. See the Factory integration.

Issue pages now open with what Praxen Inc. saw. Metric cards show each signal's value, its baseline and how far it moved, and a log summary groups the lines that matter by their shape.

Blast radius

Every issue shows the resources around the affected one in the context graph, so you can see what else is exposed before you open the investigation.

Investigations survive deploys and restarts

Investigations now run as durable workflows. A deploy or restart on our side no longer cuts one off mid-turn: it picks up where it stopped.

Praxen Inc. gives every resource a priority: Critical, Standard, Low or Minimal. It's worked out from the resource's connections, traffic and recent changes, and higher-priority resources are checked more often.

Set it yourself

Change a resource's priority from its page. A level you choose stays until you set the resource back to automatic.

Reclassify an account

Re-run the classification for every resource in a cloud account from the account's settings.

Log summaries in investigations

Investigations can summarise a large log result instead of reading every line. The summary gives the severity, the error count, recurring patterns and the most relevant lines, quoted verbatim. It covers Datadog, AWS CloudWatch, Vercel, Fly.io and Render logs.

Each time Praxen Inc. runs a check on a resource, a cloud account or an integration, the result is recorded. Resource pages list their recent evaluations, and the issues page of each cloud account and integration shows the evaluations of its checks.

More of AWS in the context graph

Kinesis streams, KMS keys, Secrets Manager secrets and service discovery services from your AWS accounts join the context graph.

Praxen Inc. now syncs much more of your Cloudflare account into the context graph: zones, load balancers with their pools and monitors, health checks, Access applications, Tunnels, Spectrum apps, Stream live inputs, Images, Turnstile widgets, waiting rooms, certificate packs, Logpush jobs, and Workers routes and custom domains.

DNS across providers

A Cloudflare DNS record that points at a Vercel project, a Fly.io app, a Render service, an AWS load balancer or a CloudFront distribution becomes an edge in the context graph, so a hostname leads to the resource that serves it.

Quieter in Slack threads

Once Praxen Inc. is part of a Slack thread, it replies only to messages meant for it: questions, requests, answers to its own questions and corrections. Messages between teammates and acknowledgements such as "thanks" get no reply.

Connect Cursor and it can write Praxen Inc.'s fixes. Praxen Inc. investigates and writes the brief, then a Cursor cloud agent fixes the code and opens the pull request on your GitHub.

Cursor joins Devin. Paste an API key from Cursor's settings and it's validated before it's saved. Set Cursor as the workspace's default for fixes. See the Cursor integration.

Investigations can now read any endpoint of the GitHub, Cloudflare, AWS, Vercel, Fly.io, Render, Datadog, Honeycomb, Axiom and Sentry APIs. When no dedicated tool covers what an investigation needs, it calls the provider's API directly with the access you already gave Praxen Inc.

Small responses

API responses are trimmed before the investigation reads them. Link fields are dropped, long strings are cut and long lists are capped, so one large response leaves room for the rest of the evidence.

Every fix has its own page

Each fix opens on its own page, with an overview and a timeline of what happened from the investigation to the pull request.

Connect a Kubernetes cluster and Praxen Inc. adds its namespaces, pods, deployments, stateful sets, daemon sets, jobs, services, ingresses, nodes, autoscalers and persistent volumes to the context graph, linked to each other.

Checks watch for crash-looping pods, pods stuck in pending and unhealthy nodes. Investigations get read-only access to the cluster: they can list and describe resources, read their events and fetch pod logs. See the Kubernetes integration.

Issues have a Traces tab. For AWS resources Praxen Inc. pulls X-Ray traces, and for Cloudflare Workers it pulls traces from Workers Observability.

What the tab shows

Trace counts, faults and latency over time, a breakdown by handler or operation, and sample error traces next to the slowest ones.

Checks from your own dashboards

Widgets on your CloudWatch dashboards and your saved CloudWatch Logs Insights queries become checks, and so do saved queries in Cloudflare Workers Observability. Praxen Inc. watches the signals you already chose to look at.

Connect Devin and it can write Praxen Inc.'s fixes. Praxen Inc. investigates and writes the brief, then a Devin session fixes the code and opens the pull request on your GitHub.

Create a service user in Devin's API settings and paste its token. Praxen Inc. detects the organization from the token before it's saved. Set Devin as the workspace's default for fixes when you connect, or change it later in settings. See the Devin integration.

Praxen Inc. watches your connected cloud accounts and integrations and opens an issue when something looks unhealthy. Checks run every 10 minutes against AWS, Cloudflare, Vercel, Fly.io and Render accounts, and against Datadog, Sentry, Honeycomb, Axiom and GitHub. Praxen Inc. leans towards staying quiet: an issue opens only when the evidence is strong and specific.

The evidence on one page

Each issue has its own page with Praxen Inc.'s reasoning, the metrics and logs behind it, a timeline and its properties.

Every issue starts an investigation

A new issue opens an investigation straight away, carrying the issue's summary and the charts that triggered it.

When a thread lands on a change worth making, ask Praxen Inc. to fix it. It writes a self-contained brief from what the thread found, makes the change in a sandbox and opens a pull request on your repository through the GitHub App.

One change per pull request

Each fix covers one logical change. Unrelated fixes from the same thread arrive as separate pull requests.

Investigations follow your repository instructions

Praxen Inc. reads AGENTS.md, INVESTIGATIONS.md and CLAUDE.md from the root of your connected repositories and follows them in every thread.

Fork or rewind a thread

Fork from any reply to start a new thread from that point, or revert a thread to an earlier message to drop everything after it.

Threads can work in your Slack workspace. Praxen Inc. lists the channels it can see, reads channel history and thread replies, posts messages and thread replies, reacts to messages and uploads files such as logs and images.

Replies where the conversation is

Praxen Inc. can read a Slack thread for context and reply inside that same thread, so what it finds lands next to the discussion it came from.

More of Vercel in the context graph

Vercel syncs now bring in each project's aliases, certificates, custom environments, DNS records, firewall configuration, log drains, storage, installed integrations and webhooks, so investigations see how a project is wired up beyond its deployments.

Investigations can query your Cloudflare account through the GraphQL Analytics API. Praxen Inc. searches the schema for the dataset it needs, reads the fields that dataset offers, then runs the query, so it can pull request, error and latency figures for a Worker or zone in the middle of an investigation.