Your first runtime interaction

Choose the interface your company exposes

Every running company has an authenticated runtime API. A connected coding agent can use that API, and installed packages may contribute a chat, inbox, work view, dashboard, or public app when those interfaces fit the company.

No company-side UI is required. Follow the selected package’s own documentation for any UI it installs; otherwise continue through your connected client and the runtime API.

If your package installs a CEO-style agent

The most useful first conversation isn’t “hi how are you.” It’s telling the CEO what your exocorp is for. This applies when your selected company package installs a CEO-style agent; other packages may expose a different primary interface. Be specific. The agent has read your initial provisioning answers, but those are short. Now is the time for the longer version.

What helps:

• What the company is trying to do — One or two paragraphs. Concrete enough that someone could tell whether progress matches intent.
• Who it’s for — Customers, users, audiences. The shape of the people the company is built around.
• What good looks like — Outcomes you’d be proud of in a month. In a quarter.
• What you’ll personally weigh in on — Which decisions stay yours: brand, big spending, strategic shifts, customer disputes. Give the CEO an explicit picture of where its authority ends.
• Constraints you have in mind — Budget envelope. Tone. Things you don’t want the company to do. Legal/compliance lines.

What the reference-package CEO does with that

In the canonical software-company package, the CEO reads what you said and proposes a starting shape: which teams the company needs, what mandates each one gets, what the company should attend to first. You’ll see this as a proposal in chat — not an action.

Review the proposal:

• Does each proposed team have a clear job — A team without a clear mandate is a team that won’t be accountable. If a proposed mandate is vague, ask the CEO to sharpen it.
• Is anything missing — Often what’s missing is a team that handles a specific operational reality (compliance, support, finance, customer ops). Ask for it.
• Is anything over-built — A new company using this package does not need eight teams on day one. Two or three working teams plus the CEO is plenty to start. You can grow that package-owned structure by adding teams later (see Working with teams).

When you’re ready, approve through that package’s decision interface. The package creates its teams and mandates. This does not change the common runtime into a team or work-item engine.

The first week

For the first week or so, check in daily through the interface your installed packages expose. Review decisions requiring your input and inspect current activity through package-owned tools or the runtime API. This is when you find out whether the company’s interpretation of your direction matches your intent.

Once the rhythm feels right, you can dial back. Most operators settle into a cadence of checking in once a day or every couple of days, with package-owned notifications or a connected agent surfacing the things that genuinely need them.