Skip to main content

Code

Code is the technical surface of Ship — the page where your repositories, recent commits, tests, deployments, and production monitoring all live behind one tab strip. It's at /<workspace>/code and is visible to technical roles by default.

📷 Screenshot: Code page with the five tabs (ChangeLog · Codebase · Tests · Deployments · Monitoring).

The page is organized into five tabs. The first two — ChangeLog and Codebase — are documented here. Tests, Deployments, and Monitoring each have their own dedicated page in this section because they have enough surface area to deserve it.

Connecting GitHub​

The Code page is gated on having at least one GitHub repository connected to your workspace. If you arrive without a connection, you'll see the GitHub setup flow inline — a single "Install GitHub App" button that walks you through the standard GitHub OAuth + app-install handshake. After install, pick which repositories the workspace can see; you can edit that selection later from Settings → Integrations → GitHub.

If the connection lapses (token revoked, app uninstalled), an in-page banner appears with a Reconnect action that drops you back into the same flow.

ChangeLog tab​

The default tab. A reverse-chronological feed of commits that landed on your repos' default branches, with each entry classified by an AI agent into a category — feature, bugfix, enhancement, refactor, infrastructure, performance, security, test, docs, chore. The chips are color-coded so you can scan a week of work at a glance and tell what shape it had.

The filter bar lets you narrow by classification, repository, or date range. Clicking an entry expands it to show the commit detail, the AI-written change summary, and a link out to the PR.

This is the surface that feeds Launch — the Communication page reads ChangeLog entries when drafting changelogs, customer announcements, and release notes, so the higher the quality of the AI classification here, the better your downstream copy.

Codebase tab​

The structural view of every repository connected to the workspace. Repos are grouped by domain (frontend, backend, infrastructure, integrations, etc.) so a polyglot monorepo stays scannable instead of flattening into one long list.

Each repo is an accordion. Expanding one shows:

  • Repo metadata — branch, default branch, last analyzed timestamp, primary language.
  • AI-generated documentation — high-level overview the platform writes by analyzing the code; refreshes on a cadence and can be triggered manually with the "Re-analyze" action.
  • Quick links — open the GitHub repo, browse the file tree, jump to recent agent runs scoped to this repo, or open a chat with the repo pinned as context.

A workspace section at the top of the tab summarizes counts (repos · features · agents touching code) and links to workspace-level settings.

Browsing files​

Click into any file path or the Browse action on a repo to land on /<workspace>/code/<repoID>/<filePath> — a Monaco-based file viewer with syntax highlighting, agent-aware navigation (jump to symbol, jump to caller), and the same chat panel docked on the right so you can ask questions about what you're reading. It's read-only by design — edits happen through agents and PRs, not through the docs site.

Recent agent activity​

When an agent is working in code — opening a PR, running tests, reading the codebase to plan an implementation — its run shows up under the relevant repo's accordion in the Codebase tab, and as a chip on any related ChangeLog entry once the PR merges. There's no separate "agent activity" tab; the activity is rendered in-place beside the artifact it touched.

What's on the other tabs​

  • Testing — repo-by-repo test suites, the agent-run tester, last-green tracking.
  • Deployments — environments, canary status, rollback controls, deployment timeline.
  • Monitoring — logs, metrics, error reports, and the agent that triages incidents.