Outborn Agent Platform · Step-by-step guide

Code workspaces

Use governed coding workspaces and review controls for development tasks.

Before you begin

  • Select the project Space and an authorized repository or coding workspace.

Follow the workflow

  1. 01

    Open the workspace

    Check the connected project, branch or environment, and permitted operations.

  2. 02

    Describe a bounded change

    State the requested behavior and files or area involved, then inspect the proposed plan.

  3. 03

    Review the run

    Read the changed files, output, and any run-control or approval request before accepting the result.

Expected result

The change is reviewable in its project context and any controlled action has the required decision.

If it does not work

Check repository connection, workspace permissions, run controls, and pending approvals.

Applied guidance

Best practices for code workspaces

Recommended

  • Work in the intended repository and branch with a bounded request.
  • Review changed files and run output before accepting or deploying a change.

Avoid

  • Do not infer that a generated plan, successful command, and approved deployment are the same event.

01

Open a coding workspace

Choose the Space and coding workspace that contains the project. Repository access and available operations follow the connected source and product permissions.

02

Run a task

Describe the requested change and inspect the generated plan, file changes, and run output. Keep project and environment boundaries clear.

03

Review controlled actions

Coding workspace run controls and approvals govern operations that require authorization. Review the actual change before accepting an action.

Related documentation

Open Outborn Agent Platform ↗Outborn Agent Platform overviewContact Outborn