Product features
Everything you need to understand and improve your software.
Codeskop connects errors, network activity, user journeys, releases and analytics across mobile, web and backend, so you find issues faster and build better experiences.
- No credit card required
- Set up in minutes
- Works across your stack
Alerts & workflow
From the first alert to the merged fix
Hear about the failures that matter in the channels your team already uses, talk them through on the issue, hand them to the right tracker and, on Growth and above, get a proposed fix as a draft pull request.
- AlertsAlert rules for new crashes, spikes, regressions and slow or failing APIs, sent to Slack, WhatsApp, email or a signed webhook, plus Telegram, Discord and Microsoft Teams on Growth and above.Free (email, 1 project) · Starter (Slack, WhatsApp, webhooks, 1 project) · Growth and above (every project)
- TicketsTurn a crash, error or failing API call into a ticket in Jira, Linear, GitHub Issues, Asana or ClickUp with just a title. Codeskop adds the stack trace, impact and the user's steps.Growth and above
- CollaborationDiscuss every crash, error and failing API call where it lives: comments and @mentions with in-app and email notifications, assignment, status and an activity timeline. Every plan.Every plan, including Free
- Fix with AIFrom any issue, your own AI engine reads the code behind the stack trace and proposes a fix. You review the diff, and only then does Codeskop open a draft pull request. Growth and above.Growth and above (uses your own AI provider)
Alerts
Alerts for crashes, regressions and failing APIs
Rules per project decide what's worth a message: a new crash, a spike, a regression, or an API that's slow or failing. Alerts arrive in the tools your team already uses, with a link straight to the issue.
Plan: Free (email, 1 project) · Starter (Slack, WhatsApp, webhooks, 1 project) · Growth and above (every project)
Critical · Issue spike
NullPointerException in CheckoutActivity
- Events
- 52 in 15 min
- Users affected
- 31
- App version
- 2.4.1
- Environment
- Production
What you get
New issues
The first time a new crash, native crash, ANR or handled error happens, filtered by issue type and minimum severity.
Spikes
One issue happens at least N times within M minutes, for example 50 events in 15 minutes.
Regressions
An issue your team marked Completed happens again.
Slow and failing APIs
An endpoint's average latency or error rate reaches your limit over the window, from network capture.
One message, not hundreds
A cooldown per rule means the same issue or endpoint alerts at most once per period, so a crash loop sends one message.
Delivery you can check
Failed deliveries are retried, Recent alerts shows whether each channel received every alert, and a broken channel is flagged.
Webhooks for your own tools
Send alerts as signed JSON to any HTTPS endpoint: your incident tool, a bot or a test dashboard. Verify each request with its HMAC-SHA256 signature.
How it works
- 1
Connect channels
Owners and admins connect Slack, WhatsApp, email, a webhook and the other channels once, in Settings → Notifications.
- 2
Create rules per project
Choose what triggers an alert, in which environment, and which channels receive it.
- 3
Get told within seconds
New issues and regressions alert as events arrive; spike and API rules are checked every minute.
Channels
| Slack | Starter and above |
|---|---|
| Starter and above, from your own WhatsApp Business number | |
| Every plan, Free included, to the teammates you choose | |
| Webhook | Starter and above, signed JSON to your own HTTPS endpoint |
| Telegram | Growth and above, through your own bot |
| Discord | Growth and above |
| Microsoft Teams | Growth and above |
Questions about alerts
Which plans include alerts?
Every plan. Free sends email alerts for its one project; Starter adds Slack, WhatsApp and webhooks (one project); Growth and Scale alert on every project and add Telegram, Discord and Microsoft Teams.
Which channels can I use?
On Starter: Slack, WhatsApp, email and webhooks. Growth and above add Telegram, Discord and Microsoft Teams.
Can I send alerts to our own system?
Yes, with a webhook (Starter and above). Codeskop POSTs JSON to your HTTPS endpoint, signs every request with HMAC-SHA256 so you can check it came from us, and retries if your endpoint is down.
Will a crash loop flood our channel?
No. Every rule has a cooldown (15 minutes to 1 day, 1 hour by default): the same issue or endpoint alerts at most once per cooldown.
Can I get alerts for slow or failing APIs?
Yes. Slow API and failing API rules use the calls captured by network monitoring, which is included from Starter.
Does WhatsApp cost extra?
Codeskop doesn't add any charge. Alerts are sent from your own WhatsApp Business number, and Meta charges per template message.
Tickets
Turn any issue into a ticket, with the evidence attached
File a crash, error or failing API call in Jira, Linear, GitHub Issues, Asana or ClickUp from the issue page. You type a title; Codeskop writes the rest of the ticket from what it knows about the issue.
Plan: Growth and above
Crash on checkout submit
- Summary
- Crash · critical · 52 events, 31 users · first seen 2 days ago
- Stack trace
- at CheckoutActivity.onSubmit (CheckoutActivity.kt:118)
- Where it happens
- 2.4.1 · Pixel 7 · Android 14
- What the user did first
- CartActivity → checkout_started → POST /v1/orders 502
What you get
Five task managers
Jira Cloud, Linear, GitHub Issues, Asana and ClickUp, with one destination per project.
Just a title
The title starts as the issue's title. Change it if you like, add an optional note, and create the ticket.
The stack trace
The full trace, with the frames in your own code marked, or the endpoint, status and duration for a failing API call.
Impact and where it happens
Events, users affected, first and last seen, and the top app versions, devices and OS versions.
What the user did first
The screens, events and API calls just before the latest occurrence, so the steps to reproduce are already written.
No duplicates
The issue shows a link to its ticket (for example Linear ENG-88), so nobody files it twice.
How it works
- 1
Connect your task manager
An owner or admin pastes a token in Settings → Integrations. It's checked with the tool and stored encrypted.
- 2
Choose where tickets go
Pick a destination for each project: a Jira project and issue type, a Linear team, a GitHub repository, an Asana project or a ClickUp list.
- 3
Create tickets from issues
Anyone on the team presses Create ticket on an issue, and the ticket opens in a new tab.
Where tickets go
| Jira | Jira Cloud: a project, as the issue type you choose |
|---|---|
| Linear | A team |
| GitHub Issues | A repository |
| Asana | A task in a project |
| ClickUp | A task in a list |
Questions about tickets
Which plan includes tickets?
Growth and above. An owner or admin connects the task manager; after that, anyone on the team can create tickets.
Which task managers are supported?
Jira Cloud, Linear, GitHub Issues, Asana and ClickUp.
What goes into the ticket?
Your note, a summary with events and users affected, the exception or failing request, the stack trace with your own frames marked, the top app versions, devices and OS versions, what the user did first, and a link back to the issue.
Do tickets include personal data?
Tickets contain the same data as the issue page: user IDs (never emails or names, which Codeskop doesn't store), device models and stack traces. Choose a destination your whole team is allowed to see.
Collaboration
Discuss issues with your team, right on the issue
Comment on any crash, error or failing API call, @mention a teammate to loop them in, and follow assignment, status changes and tickets in one activity timeline. Developers, QA, product and support work from the same issue.
Plan: Every plan, including Free
- Assigned to Amina
Sam · 2 min ago
Reproduced on the test build after a failed order call. Amina can you take a look?
- Status changed to In progress
- Ticket ENG-88 created
What you get
Comments on every issue
A discussion on each issue, oldest first, so the context stays with the crash instead of in a chat thread.
@mentions
Type @ to pick a teammate. They get a notification in the dashboard bell and an email that opens the issue at the comment.
The assignee hears about it
A new comment on an issue notifies the person it's assigned to, as well as anyone mentioned.
Assignment and status
Assign an issue and move it through Open, To do, In progress, Halted, In review and Completed.
Activity timeline
Comments, assignment changes, status changes and tickets created, in one feed on the issue.
Edit and delete
Edit or delete your own comments; owners and admins can delete any. A deleted comment leaves "Comment deleted" in its place.
How it works
- 1
Open an issue
Every crash, error and failing API call has its own discussion.
- 2
Comment and @mention
Write a comment and type @ to mention a teammate. Cmd or Ctrl + Enter sends it.
- 3
Work it to done
Assign it, move the status along, and create a ticket when it's ready. The timeline keeps the history.
Who can do what
| Every team member | Read the discussion, comment and @mention teammates |
|---|---|
| Comment author | Edit or delete their own comments |
| Owners and admins | Delete any comment |
| Mentioned teammates | A bell notification and an email |
Questions about collaboration
Which plans include comments and @mentions?
Every plan, including Free. Free includes up to 5 team members, Starter up to 15, and Growth and above unlimited.
Who gets notified about a comment?
Everyone mentioned in it, and the person the issue is assigned to, in the dashboard bell and by email. The author is never notified, and nobody gets more than one notification per comment. Each person can turn the emails off in their notification settings; the bell notification always arrives.
Can I mention someone who hasn't joined yet?
No. Only members of your organization can be mentioned, so invite them to the team first. Email addresses are never turned into mentions.
What happens when a comment is deleted?
The thread shows "Comment deleted" in its place, so the rest of the discussion still reads correctly.
Fix with AI
From stack trace to draft pull request
Your AI engine reads the code behind the stack trace and proposes a fix. You review the changes and ask for revisions, and only when you approve does Codeskop create a branch and open a draft pull request.
Plan: Growth and above (uses your own AI provider)
fun onSubmit() {- val total = cart.total!!+ val total = cart.total ?: return showEmptyCart() submitOrder(total) }What you get
Starts from the stack trace
Codeskop finds the files behind the frames in your own code. Add up to five more paths if the fix needs them.
Root cause and a diff
The AI explains the root cause and shows a diff for every changed file, before anything is written.
Ask for changes
Describe what to change and revise the fix as often as you need.
A new branch, a draft PR
On approval, one commit on a new branch and a draft pull request that links back to the issue. Never the base branch.
Your AI, your key
Claude, ChatGPT, Gemini, Grok, DeepSeek or OpenRouter, connected under AI Assist. Your AI provider bills the usage.
Never overwrites newer work
If the base branch changed after the AI read it, Codeskop refuses to commit and asks you to prepare the fix again.
How it works
- 1
Start from the issue
Press Fix with AI, choose your AI engine and model, the repository, the base branch and a new branch name.
- 2
Review the proposal
Usually ready in under two minutes: the root cause and a diff. Nothing has been written to the repository yet.
- 3
Approve
Codeskop creates the branch and opens a draft pull request. Your normal review and CI take over from there.
Repository hosts
| GitHub | The Codeskop GitHub App or a fine-grained token, with write access to contents and pull requests |
|---|---|
| GitLab | A token with the api scope · opens a draft merge request |
| Bitbucket | An API token with repository and pull request write scopes |
Questions about fix with ai
Which plan includes Fix with AI?
Growth and above. You also connect your own AI engine under AI Assist and link the app to its repository with write access.
Does Codeskop merge the fix?
No. Pull requests open as drafts, so they can't be merged by accident. Your team reviews and merges as usual.
Who pays for the AI?
Your AI provider. Fix with AI runs on the engine and key you connect, so usage is billed by them, not by Codeskop.
What code does the AI see?
The issue (exception, message, stack trace, users affected and, for API failures, the request), what the user did first, and up to six files from the base branch: the ones the stack trace points at plus any you add. Nothing else from your repository is sent.
Who can approve a fix?
Only the person who started it can revise or approve it. Teammates can see it on the issue, and every start and commit is in the audit log.
Core features
Powerful tools for a more reliable product.
Everything you need to find, understand and fix issues, with the context to make the fix last.
Platforms
One SDK. Every platform.
Codeskop works across your stack, from mobile and web to backend services. What each SDK captures
- AndroidNative SDK on Maven CentralAvailable
- Fluttercodeskop_tracker on pub.devAvailable
- Web@codeskop/tracker on npmAvailable
- ReactProvider, error boundary and hookAvailable
- ServerPython, Node.js, Go, Java and PHPAvailable
- Kotlin MultiplatformShared Kotlin SDKEarly access beta
- iOSSwift package, built on the KMP SDKEarly access beta
Security & reliability
Built for teams that care about their users.
Your data stays yours. Codeskop is designed with privacy and reliability at its core.
It all connects
From issue to insight, in one production story.
Errors, user journeys, network activity and releases are linked, so you go from symptom to root cause in minutes.
An issue occurs
A crash or error is captured with its full context.
See who it hit
How many users, which devices and which release.
Check the requests
The failing and slow API calls around it.
Check the release
Whether the latest release made it worse.
Investigate and fix
Assign it, ticket it, or get a proposed fix.
Ready to improve your software?
Start building more reliable experiences today.
Free plan, no credit card. Your first crash report can arrive in minutes.