Structured records
Give each record meaningful fields instead of burying the information in another document.
Your project has
more than code.
Orbit brings its environment, services, and structured knowledge into view. Start with the built-ins. Create the modules your project needs next.
Orbit · Pulse
| Event | When it fires | Area | Status |
|---|---|---|---|
share_link_created | A new link is created | Sharing | Implemented |
share_link_opened | A client opens the link | Sharing | Implemented |
share_link_expired | An expired link is opened | Sharing | Planned |
| Variable | Value | File |
|---|---|---|
APP_URL | http://localhost:3000 | .env.development |
SHARE_LINK_TTL_DAYS | 7 | .env.development |
DATABASE_URL | •••••••••••• | .env.development |
Stripe
Payments and billing. Find its dashboard and documentation.
Sentry
Error monitoring. Get to the service from the project.
Vercel
Hosting and deployments. Keep the dashboard within reach.
Interactive example with illustrative records. Analytics is an event inventory, not live traffic.
Find the setting.
Find the service.
Bring environment files and detected integrations into project views. Find a variable, inspect the service your app uses, and get to its dashboard or documentation.
- Find and edit environment variables.
- Inspect detected services and integrations.
- Keep the view scoped to the current project.
Environment · Pulse
| Variable | Value | File |
|---|---|---|
APP_URL | http://localhost:3000 | .env.development |
SHARE_LINK_TTL_DAYS | 7 | .env.development |
DATABASE_URL | •••••••••••• | .env.development |
Your workflow.
Your own module.
Some information deserves more structure than a doc. Define the fields, create records, and organize a view around what your project needs to keep track of.
Start from a template or a blank module. Reuse the definition in another project and give that project its own records.
Orbit settings · Analytics
Give useful information a shape.
Module fields
Event nameText
When it firesText
AreaSelect
StatusSelect
Keep the inventory
with the implementation.
Ask an agent to work with an Orbit module as part of a task. It can read the relevant records and update them alongside the code, so the project view reflects the work you asked for.
For example: implement an analytics event and add its matching inventory record. This describes your instrumentation; it does not report live analytics traffic.
Agent · add a sharing event
Added share_link_created
The event fires when the link is created.
The event fires when the link is created.
Updated the event inventory
The matching record explains when it fires and where it belongs.
The matching record explains when it fires and where it belongs.
Analytics updatedOne record added · implementation and inventory together
Views that fit
Organize and group records around the way you use the module.
Reusable modules
Define the structure once, then add it to the projects where it belongs.
A few things
to know.
Visit the help center Is Orbit a live analytics dashboard?
The Analytics example is an inventory of events in your codebase. It tracks the events and their definitions, not incoming traffic or live usage metrics.
Can I create my own module?
Yes. Start from a template or a blank module, define its fields and instructions, and add it to a project.
Can agents update Orbit automatically?
When you explicitly invoke a module for an agent task, the agent can read and update that module for the task. Module access is scoped to the project and invocation.
How does Orbit differ from project docs?
Docs are suited to briefs and explanations. Orbit is suited to structured records and project views you want to inspect, organize, and use in agent work.
There is more to Choro
Explore MobileGive the rest of your
project a place.
A native workspace for your Mac.