Admin ConsoleCollaborate

LStack Cloud Agent

Connect your GitHub account so hosted agents can work on your repositories, choose the agent's model, and run agent jobs from the browser.

Open LStack Cloud Agent from the My account group. The page is titled LatentStack Agent and has two tabs: Agent for running jobs and Settings. A badge at the top right reads Ready once a model is chosen, or Setup required. Every signed-in user can use it; the settings are your own.

Settings

The Setup checklist at the top shows whether you have a gateway API key and a model selected.

Card	What it does	Scope
Gateway API key	Your API key, read-only, with a copy button. Agent calls use it, so your tier, budgets and guardrails apply to them.	Your account
GitHub token	A GitHub personal access token used to clone your repositories. It's stored encrypted; once set, only its last four characters are shown. Remove token deletes it.	Your account, in every organization
Allowed repositories	The repositories you allow agent jobs started from this page to use. Select Load repos to list what the token can reach (up to 1,000), then tick the ones to allow.	Your account
Model	The model agent jobs from this page use. Only models your tier allows are listed.	The active organization

Connect GitHub

1
Create a token on GitHub
A personal access token that can read the repositories you want agents to work on.
2
Paste it into GitHub token
The field shows ghp_… as a hint.
3
Select Load repos
The token is saved and your repositories are listed, private ones with a lock icon.
4
Tick the Allowed repositories
Then choose a Model.
5
Select Save settings
You'll see Saved ✓.

To replace the token, paste a new one and save. The old one is overwritten.

Hosted agents (Agents API)

The Agents API uses the GitHub token saved here whenever a session works on a repository. Your token must be able to read each repository the session uses. It's never shared outside LatentStack.

No token saved: sessions on a repository fail with github_not_connected.
The token can't read a repository: repo_not_accessible.
Sessions with no repository don't need a token.

Allowed repositories and Model apply to this page only

The Agents API takes its repositories and model from each API request. It doesn't use the Allowed repositories or Model settings here.

Run a job from the browser

1
Open the Agent tab
If no model is chosen yet, a prompt sends you to Settings.
2
Describe the task
Type it in New Job.
3
Select Run
Or press ⌘+Enter. The job runs in a sandbox and can take a few minutes.

History lists your jobs, newest first. Select one to see its details and result. Job statuses are Queued, Running, Done, Failed and Timeout.

Jobs belong to the active organization and use that organization's tier. Before a job starts, the model is checked against your tier, so a disallowed model fails straight away.

Troubleshooting

"Set a GitHub token first"

Paste a token before selecting Load repos.

"GitHub error: …" when loading repos

GitHub rejected the token. Check it hasn't expired and has access to your repositories, then paste it again.

"No model selected. Pick one in Agent Settings."

Choose a Model on the Settings tab and save.

"Model … is not allowed for your tier"

Your tier in the active organization doesn't include that model. Pick another, or ask an admin to add it to your tier.

"No access tier is assigned for this account"

Ask an admin of the organization to assign you a tier.