ArchAstro

Developer Docs

Developer Portal

Manage what you've built: agents, their runs and memory, the app's data stores and automations, and your org's settings.

Overview

Developer Portal at https://developers.archastro.ai is where you manage everything you've built with ArchAstro. Authoring lives in the CLI or your coding agent; the portal is where you look at what's running, fix what's off, and manage access.

The portal is scoped to one app at a time. Sign in and you land on the app list; pick one and every screen underneath, from agents to storage to settings, belongs to that app. The topbar keeps an app switcher and an org switcher next to each other so you can jump between apps and, within one, between the orgs it serves.

Next to those, the topbar has a sandbox switcher. It defaults to Production. Pick a sandbox instead and everything you see, agents, threads, data, is scoped to that sandbox's own copy of the app's runtime data. A "Manage Sandboxes" link in that same menu takes you to the full sandbox list. See Sandboxes.

Settings live behind the account menu in the top right, not in the sidebar. Personal settings (profile, security, notifications, billing) and, if you're an org admin, your org's sign-in and SSO settings, are all there. See Settings below.

The top item in the sidebar, Overview (/overview), is the app's analytics dashboard: charts on agent activity, filterable by org and by agent. Developers and org admins see it; other users see a plain landing screen pointing them at the sidebar.

The rest of this page walks the sidebar top to bottom, then the agent detail page, then Settings.

App

The App section covers the app's own configuration, the things every agent and user in it share.

  • API Keys (/keys). Publishable and secret keys for this app.
  • OAuth (/oauth). Configure sign-in providers and manage third-party OAuth client registrations.
  • Integration Providers (/integration-providers). Bring your own GitHub App and install it once for app automations, organizations, and agents.
  • Domains (/domains). Register domains the app can use for email sending.
  • Webhooks (/webhooks). Configure Slack and GitHub webhooks. For custom integrations, use the Webhooks API with a lookup_key to create generic endpoints.
  • Notifications (/notifications). Tell the platform what URL shape a notification type should link back to (a "new message" email needs a link to the thread it's about). Sends for a type are blocked until it's set up here.
  • Mobile (/mobile). Register the native apps that receive push notifications for this app.
  • Members (/members). Manage who has developer access to this app.
  • Env Variables (/env-vars). Encrypted key-value pairs available to workflows and integrations at runtime.
  • Integrations (/integrations). Connect outside services like Cloudflare (D1 databases, R2 buckets) to the app.

Organizations and Organization

If you're a developer, Organizations (/orgs) lists the customer companies using this app, with their access policies. If you're signed in as a member of one of those companies, you instead see Organization (/my-org): your own org's details and administrators, plus, for org admins, an Env Variables sub-page (/my-org/env-vars) for org-scoped key-value pairs. See Organizations.

Users and Teams

Users (/users) and Teams (/teams) list the people and teams inside this app, the ones your app signs in and your agents work with. Not to be confused with your own developer teammates under Members.

Tasks

Tasks (/tasks) shows user- and team-owned work: assignments, subtasks, comments, and activity.

Agents

Agents (/agents) is where you view and manage the agent identities in this app. Open one to land on its detail page, described below.

Underneath Agents, three sidebar items give you the same views across every agent in the app, instead of one at a time:

  • Sessions (/sessions). Every agent session execution across the app.
  • Routines (/routines, landing on /routines/list). Every event-driven routine across every agent, with a Runs sub-tab for their run history.
  • Extensions (/extensions, landing on /extensions/tools). Every tool, skill, and computer attached to any agent, with a filter to narrow to one.
  • Knowledge (/knowledge, landing on /knowledge/installations). Every installation, source, integration, ingestion, item, and credential across every agent.

Each of these pages can be filtered down to a single agent, and the same screens exist scoped to one agent from its detail page.

Threads

Threads (/threads) lists the conversations for this app: who owns each one, when it last updated, and a link into it.

Storage

Storage groups the app's own data stores, landing on Custom Objects by default:

  • Custom Objects (/storage/objects). Browse and manage the custom object schemas and records you've defined. See Custom Objects.
  • Files (/storage/files). Browse and manage files uploaded to the app.
  • Key-Value (/storage/kv). Browse and manage per-user key-value entries; search matches user email or name. See Key-Value Storage.

Automations

Automations groups the repeatable, project-wide logic you've written:

  • Workflows (/workflows). Multi-step flows for approvals, handoffs, and branching work. See Workflows.
  • Scripts (/scripts). Custom logic used by workflows and routines, plus their ScriptTest files. See Scripts.
  • Skills (/skills). Reusable skill packages available to agents. See Skills.
  • Configs (/configs). Configuration files for the app. See Configs.

Agent detail

Opening an agent from the Agents list takes you to its detail page, with a tab bar for Overview, Sessions, Memory, Routines, Extensions, Knowledge. Routines, Extensions, and Knowledge here are the same screens described above, scoped to just this agent.

Overview is the tab to start on when an agent is misbehaving or you want the full picture of it. It holds, in order:

  • Agent Details. Lookup key, email, phone, default model, identity text, the user and team it belongs to, and its org.
  • Health Profile. A score and a set of checks (identity, model, routines, tools, installations, computers, recent failures, activity), each with a status and, when something needs attention, a direct link to fix it. Below the checks, a setup checklist walks through the install-time actions the agent still needs (an env var to set, an installation to connect, an integration to authorize) before it's fully working.
  • Schedules. The agent's upcoming and recent scheduled runs.
  • Threads. The conversations this agent is a member of, with a link to view them all.
  • Environment Variables. This agent's own encrypted env vars, listed with masked values, editable and deletable right on this page.
  • Working Memory. The most recent entries the agent has stored, with a link to the full list on the Memory tab. See Agent Memory.

Settings

Open the account menu (top right) and choose Settings for account and org preferences. Profile, Security, and Notifications are available to everyone. Developers and org admins also see Billing.

Org admins additionally get:

  • Sign-in methods (/dashboard/settings/sign-in-methods). Choose which authentication methods members of your organization can use to sign in.
  • 2FA policy (/dashboard/settings/2fa-policy). Decide whether two-factor authentication is required for everyone in the org.
  • SAML SSO (/dashboard/settings/saml). Configure your identity provider. SAML also needs to be enabled under Sign-in methods for the button to appear at login.

What to do when something looks wrong

  1. Open the agent's Overview tab. The Health Profile and setup checklist tell you what's off and what to do about it.
  2. If a specific run failed, check the agent's Sessions tab, or the app-wide Sessions page, for the run record and its error.
  3. If a tool call is failing, check the agent's Extensions tab to confirm the tool is enabled, and its Environment Variables section on Overview for a missing credential.
  4. If the agent can't reach an outside system, check its Knowledge tab for the installation's status and what it needs next.