Axon Shaft is free for everyone right now. Try it out →

Axonpack
7

Axonpack ends the guesswork when things break.

Answers you and your agent can both read. Every request, error, log and stored value is captured on the device. Your agent can read it from the terminal, and mock or send requests from inside the app.

npx skills add axonpack/skills

Then ask your agent: Set up @axonpack/expo-devtools in this app

The skill reads these docs live, so the agent follows the package's current installation page and checks each step.

Agent skillInstall it yourself

my-app
npx devtools network --where state=error --since 10m# network · my-app · iPhone 16 Pro · 1 of 214 matchid                   method  code  state  ms   urlxhr-1762172184120-4  GET     401   error  190  https://api.acme.dev/v1/me# next: --after xhr-1762172184120-4

Axon Shaft: AI code review in your own GitHub Actions

Axon Shaft is a GitHub app that reviews every pull request with Claude. It runs on your repo's own runner with your own Claude key, comments on the lines that need work, and blocks the merge until your checks pass.

  • A check run for each checklist

    Security, tests, known vulnerabilities and the rest each post their own check run, such as Axon Shaft / security. A blocking finding fails it.

  • Merge gates

    Write requirements in plain words, like "A migration has a rollback". Require Axon Shaft / gates and a pull request can't merge until every gate is met.

  • /ask and /fix in comments

    Comment /ask to get an answer about the code, or /fix to have it make the change and push it to the pull request.

Install on GitHubRead the docs

Reading the running app from the terminal

You ask your coding agent why the profile screen is blank. It reads the code and guesses. Then it asks you to open the app, find the request that failed, and paste the response back into the chat.

With Expo Devtools in the app, the agent can ask the app instead. The devtools command comes with the package and finds the running app through Metro. Its replies are plain text, and you can run the same commands yourself.

  1. npx devtools apps

    Lists the apps running on Metro and the device each one is on.

  2. npx devtools topics

    Lists what you can query, such as network, console, storage and crashes, with a row count for each.

  3. npx devtools network --where state=error --since 10m

    Lists the requests that failed in the last 10 minutes. --where, --grep and --since filter any topic.

  4. npx devtools get network <id>

    Prints one row in full. For a request, that is its headers, body and timing.

  5. npx devtools network override https://api.acme.dev/v1/me --status 503

    Answers the app's requests to that URL with a 503 until it reloads. The network topic can also block a URL, or send and replay requests from inside the app. Any method but GET needs --yes.

The CLI tab

It lists what an agent asked or changed, with the reply it got, on the phone and in React Native DevTools. Replies go through your redaction settings, and auth headers and cookies are always masked.

Agent skill

One skill covers every package. Your coding agent loads it, and it has the agent read these docs live, so it always matches the latest release. The agent sets the package up in your app with your own package manager and checks each step before the next one.

npx skills add axonpack/skills

Use with AI agentsAgent skillBlog post on the devtools command

Packages

Each one is versioned and released on its own. This list is read from npm when the site builds, so everything on it is published.

Expo Devtoolsv3.9.0

A tester says the feed is empty on their phone. On your simulator it loads. There is no cable and no log, and the tester can't tell you which request failed.

Expo Devtools runs inside the app. The tester taps a button and sees every request with its headers, body and timing, plus the console, crashes, storage and screens. One flag, enabled, decides whether any of it runs.

Expo Devtools docsnpm8,405 downloadsMIT

app/_layout.tsx
import { Stack } from 'expo-router';
import { DevtoolsProvider } from '@axonpack/expo-devtools';

export default function RootLayout() {
  return (
    <DevtoolsProvider
      config={{ enabled: process.env.EXPO_PUBLIC_APP_ENV !== 'prod' }}>
      <Stack />
    </DevtoolsProvider>
  );
}

React Native Devtools Tabv0.2.1

You want to know who is signed in while you debug. So you add a console.log, reload, read it and delete it. Next week you add it back.

React Native DevTools Tab puts a tab of your own beside Console and Sources. The tab is a component that runs in the app, so it reads your real store and its buttons call your real functions. Behind a __DEV__ guard, a release build carries none of it.

React Native Devtools Tab docsnpm3,590 downloadsMIT

devtools.tsx
import { ReactNativeDevtoolsPanel } from '@axonpack/react-native-devtools-tab';

function Session() {
  const { user } = session.use();

  return (
    <div style={{ padding: 12 }}>
      <p>signed in as {user}</p>
      <button onClick={() => auth.signOut()}>sign out</button>
    </div>
  );
}

ReactNativeDevtoolsPanel.registerTab({ name: 'Session', component: Session });

React Pretty Printv0.1.3

An API answers with a few hundred lines of JSON. On screen it is one JSON.stringify inside a Text, and you scroll past all of it to find one field.

React Pretty Print draws it as a tree that opens and closes, with a preview on every closed node. You pass in your own View, Text and Pressable, so the same component works in React Native and on the web. It has no dependencies and no native module, so it runs in Expo Go.

React Pretty Print docsnpm2,069 downloadsMIT

Example.tsx
import { Pressable, Text, View } from 'react-native';
import { JsonTree } from '@axonpack/react-pretty-print';

const Example = () => (
  <JsonTree primitives={{ View, Text, Pressable }} value={response} />
);

Previewv0.4.0

QA wants to try the login fix from a pull request. The change is only JavaScript, but getting it onto their phone still means a new native build and a wait while it uploads.

Preview publishes one JS bundle per branch to your own S3 bucket. In the app, QA picks the branch from a list, and the app downloads it over the air and restarts into it. Going back to the base build is one tap, and each build lists only the previews made for its native code.

Preview docsnpm1,690 downloadsMIT

Terminal
npx expo install @axonpack/preview expo-file-system
npx preview publish --id task-1-login-fix

In App Updatesv0.1.2

You shipped 2.4.1 with a fix for a crash. A month later the same crash still comes in from people on 2.3.0, who never opened the store to update.

In-App Updates checks the App Store or Play Store for a newer version and opens an update prompt that already looks right, in light and dark mode. Set a minimum version and anything older has to update. It runs in Expo Go, with no native code to install.

In App Updates docsnpm1,422 downloadsMIT

App.tsx
import { UpdatePrompt } from '@axonpack/in-app-updates';
import { Text, View } from 'react-native';

export default function App() {
  return (
    <View style={{ flex: 1 }}>
      <Text>My app</Text>
      <UpdatePrompt />
    </View>
  );
}

Safety and dependencies

What the agent tool can reach, and what the packages add to your app. Each point links to the page that explains it.

  • Queries are filtered in the app

    The devtools command asks the app over Metro's debugger connection. The app runs the filter and sends back only the rows that match.

    Use with AI agents
  • Auth headers and cookies are masked

    The authorization, cookie and set-cookie headers and a page's document.cookie always come back as [redacted]. Your own redaction settings apply as well.

    Redaction
  • Writes to a server need --yes

    send and replay refuse any method but GET without --yes. The app checks the flag itself, so a call that skips the command line needs it too.

    Safety rules
  • Development builds only

    The app answers the command only in a development bundle with the devtools enabled. A release build has nothing it can talk to.

    Production
  • One native module, loaded optionally

    Expo Devtools has one native module, for the readings JavaScript can't reach. In Expo Go a few of those readings go quiet and the rest of the panel works.

    Expo Go or a development build
  • No storage library installed for you

    The Storage tab reads the stores you pass in as adapters, so the package adds no AsyncStorage or MMKV to your app.

    Registering your stores