For developers

Build software under
Blackstar command.

Coding, testing, debugging and deploy sit on the existing SDK and portal. External writes stay on the approval gate.

command.ts agent running
import { blackstar } from "@blackstar/runtime"
const agent = await blackstar.agents.create({
name: "Command-layer builder",
tools: [code, terminal, browser, git, deploy],
route: "workspace-default",
knowledge: repo.context(),
})
await agent.run("ship behind approval")
Illustrative sample — not a published npm package

Capabilities

The developer stack already in Blackstar

Coding agents, deploy rails and MCP — reuse what exists. Do not invent extra providers.

AI Coding

Agents write, review and refactor code in your repo.

Agent SDK

Build custom agents in code with the existing tool runtime.

API

REST + webhooks to run agents, models and workflows already in product.

Developer Portal

Keys, usage, webhooks and live API explorer.

Terminal

Run commands in a sandboxed agent terminal.

Browser Preview

See your app live as agents edit and ship.

Git

Branches, PRs and commits managed by agents.

Deployments

Ship to staging and prod on the existing deploy rails.

MCP

Model Context Protocol servers already wired in Blackstar.

Tools

Code execution, file access and integrations.

Models

Routed models with tool use. No invented provider names.

Workflow

Build → Test → Debug → Deploy → Automate

Agents work the lifecycle alongside you. Governance is not optional.

Phase 1

Build

Describe a feature and agents scaffold the project on the existing workspace.

  • Generate features from a prompt
  • Edit existing files with context
  • Compose UI, API and data together

Phase 2

Test

Agents generate tests, run them in the sandbox and fix what breaks.

  • Unit and integration generation
  • Run tests and read failures
  • Iterate until green

Phase 3

Debug

Triage errors, inspect logs and let agents propose patches.

  • Live error and log analysis
  • Reproduce from stack traces
  • Propose fixes for approval

Phase 4

Deploy

Ship on the existing preview and deploy rails.

  • Staging and prod
  • Preview URLs per PR
  • Rollback on the same path

Phase 5

Automate

Trigger agents on git events, schedules and webhooks already in product.

  • Review on PR
  • Scheduled maintenance
  • Webhook-driven workflows

Ship on the command layer

Use the existing developer portal and runtime. No fabricated endpoints.