Ship an app from Claude Code

Bring an app you built in Claude Code, Claude Desktop or as an artifact to your team. kanman reviews it in the same session, asks before it changes anything, and puts it live on your team's runner.

You built a little tool on a Tuesday afternoon, and now three people want it. Ship it to kanman and it gets an owner, a check, versions and a home on your team’s runner, without you setting up hosting.

Before you start

Ship it

Open the project in Claude Code, or the chat with your artifact in Claude Desktop, and ask:

Ship this project to kanman as an app for IAM Team (use the ship_app tool)

The Apps tab has this line ready to copy, with your team’s name in it (Copy the line for Claude Code).

Within seconds Claude posts a link to the review, for example “Uploaded to kanman as ‘SLA board’ for IAM Team. kanman has started the review”, and then passes on my status lines as I go:

  • kanman has started the review
  • looking for keys and tokens in the code
  • checking which services the app calls
  • checking which data the app reads
  • found your SQLite file
  • checking the page for accessibility

Questions in the same conversation

When I find something, I ask, one subject per question, each with fixed answers. Claude asks you in its own words (or shows a choice dialog where it can) and sends your answer back. Claude never answers for you, and I change no code and no data without your yes.

I found I ask Answers
Keys or tokens in the code Move them to the team’s secrets? The app gets them when it runs, never in its files. Move, Remove
A token for a system your team has connected, such as your Jira Use the connection instead? Use the connection
A call to another host The app calls this host. Allow it? Allow, Block
A route other systems call, such as a webhook Allow it? Allow, Block
A SQLite file the app writes Should I take it over: kept on its own volume, backed up, restorable? Take it over, Start empty
Data your team’s rules keep apart Drop the second source, or ask a lead? Drop it, Ask a lead

Close Claude Code with questions still open, and they move into your kanman chat and your next brief. Nothing waits silently.

The review link opens the same review in kanman: status, the questions (answered or open), what I found and why, the rules for outgoing and incoming calls, and a live preview. Engineers can read it in depth; nobody has to.

When nothing blocks the app any more, it goes live for the team, at its own page under Apps.

Dry run, for code review and CI

Ask Claude for a dry run (“ship this to kanman as a dry run”). You get the full report back as text: what I found, the changes I would make (a secret moved, a connection instead of a token) and the rules for outgoing and incoming calls. Nothing is stored.

Ship a new version

Ship the project again with the app’s name or its short name, and the upload becomes the app’s next version, checked like the first one. If your team keeps apps in repositories, an update opens a merge request in the app’s repository instead, and Claude passes on its link.

For engineers: how your app runs

I pick the simpler of two shapes that works and tell you which one your app is.

Shape When How it runs
Files only, no server Mockups, artifacts, most dashboards: HTML, JavaScript and CSS Served in its own isolated frame. No process to patch or crash.
With a server A project with a backend, a SQLite file, or calls to your own services A container built from your repository’s Dockerfile (or a detected template for Node, Python and others), on your team’s runner, with CPU and memory limits, health checks and a restart on crash.

Data: by default the app reads a table of its own store, which kanman keeps current (fetch("./__kanman/table?name=<table>"), answering {rows: [...]}); it keeps showing its rows when a source is down. For a lookup one viewer makes with their own rights, include <script src="./__kanman/app.js"></script> and call kanman.read(source, read, input): each viewer gets the data their own rights allow. Keep only fixed reference data in the bundle; a file or module of data larger than 64 kB is refused. No connection string or token ever sits in the app.

With a server, the app does not build its own sign-in: kanman checks who may open it and passes the viewer’s identity on. Team secrets arrive as environment variables when the app starts, never in the image. Outgoing calls reach only the hosts you allowed.

Last updated: January 1, 0001

Open kanman