Environment Management
Manage development environments and configurations
Your saved changes are not published yet. A user with Setup repository Git permission, or Environment Git on this environment, must commit and push them.
This environment's repository is hosted in CoderFlow. Upload your files before you build the environment. The same link is on the Repos tab when you need to add more.
This Draft's configuration hasn't been generated yet. Once your files are uploaded, choose Generate configuration.
Select an Environment
Choose an environment from the tabs above to view and manage its configuration
-
Setup
Configuration not generated yet
Configure this environment
An agent can work in this Draft until its image builds, its app answers and its tests pass, within budgets you set. You review its changes and set the environment Active yourself.
How this environment, its source code, and connected systems fit together.
Where instructions, skills, and memories mention each other and the repositories. Every line is a mention found in the text, not a configured connection, so check each one against its source line.
Environment Information
Loading Fast mode policy…
Child tasksrun as none · depth 3 · up to 10 children · deployments off
Projectsproject branches off
Typed fields shown on every task in this environment. Values are stored per task.
No README content yet.
Portal Access
Applications that Portal users can launch from this environment.
Genie skin Instance default
Drag entries to reorder them or drop them onto a folder. With the keyboard, use Alt+↑ and Alt+↓.
Choose the IBM i libraries and tables Portal users can query from Ask, reports and scheduled questions. People never get more than their own IBM i login allows.
Only Portal queries made with each person’s own IBM i login follow these rules. They don’t limit data scripts, runtime tools, or connections that Ask and report agents use with the connection’s own login, such as SQL Server.
This environment has no IBM i connection with SQL turned on, so there is nothing to set here. Data Access rules only limit IBM i queries made with each Portal user’s own login. Ask and report agents can still use the connections this environment gives tasks, such as SQL Server, with each connection’s own login. To limit what they can reach, give business users a dedicated Portal environment with only the connections they need.
IBM i system libraries (Q*, SYS*) stay closed under Portal rules unless a rule allows them. Saved changes apply to the next query, including reports people already have. Refused queries are written to the server log.
Library lists
When someone names a table without its library, the Portal reads the first copy on their list that the rules above let them query. Business users and the Ask assistant see the list's name, never library names. Lists never give or take away access.
Someone on more than one list uses the first one that applies. Saved changes apply to the next query, including saved and shared reports: each viewer reads the copy on their own list.
Related Settings
Manage environment assignments in Access and shared provider accounts in Server Settings. Data definitions remain in this environment’s Connections tab.
Select a Repository
Select a repository from the sidebar to view details, or add a new one.
App Server
{{origin}}, {{host}}, or {{hostname}} for dynamic resolution
Port-Specific QA URLs
Override the default QA URL for specific ports (e.g., port 3001 → https://production.example.com)
Basic Authentication
Load HTTP Basic credentials from secrets (must have available_for: ['tasks'])
Proxy Headers
Ports
Ports are available only through CoderFlow by default. Private network exposure requires a private IPv4 address assigned to the machine running CoderFlow/Docker (not the calling machine) and applies to newly created task containers.
Protocol the application serves on this container port. Choose HTTPS when the port accepts only TLS, for example a server configured with a certificate; CoderFlow then connects to it over HTTPS.Launch URLs
Mark one URL as Primary to open it when users click the Testing button in tasks.
Feedback Widget
Screen Rendering
Mount host directories, or add persistent Public media storage for final PNG/JPEG files. Keep drafts outside public volumes.
Appended to instructions at task startup
Custom Instructions
Schedule
Automatically rebuild this environment's Docker image on a schedule
The shared base image this image is built on has its own schedule in Settings › Base Image.
Scripts
AdvancedOptional scripts for customizing the build and task lifecycle. Leave blank to use defaults.
Build History
Loading build history...
Secrets
Task access includes access to task credentials. Secrets available for Tasks can be read by people who can run commands or direct the agent in those tasks. In shared tasks, this can include other users. Give tasks only credentials those users are trusted to access.No secrets configured.
Secrets can be referenced in builds, tasks, and deployment profiles and exposed as environment variables or mounted files.
External Connections
No external connections configured.
Add connections to external servers (a SQL Server, PostgreSQL or MySQL database, IBM i, or SSH) to auto-configure containers with database access, SSH keys, and build tooling.
Select a Test
Select a test from the sidebar to view details, or add a new one.
Select a Template
Select a template from the sidebar to edit, or create a new one.
Select a Profile
Deploying:
Select a deployment profile to view details, or add a new one.
Deployment profiles define how to deploy your application to destinations such as QA and Production.
Deployment Script
Reference secrets from the Secrets tab to expose as environment variables or mounted files.
User-provided values prompted when running this deployment.
IBM i Profiles
Import Sources
Build Rules
Agent Memory
Persistent context that carries across tasks. Agents accumulate memories during task execution.
Memory Index (MEMORY.md)
Memory Files
No memories yet. Agents will create memories as they work on tasks.
| Name | Description | Attribution | Actions |
|---|
Agent memory is disabled for this environment. Enable it above to let agents accumulate context across tasks.
Environment Automations
No automations configured for this environment.
Create one to run tasks on a recurring schedule, from a webhook or when an email arrives.
| Name | Trigger | Enabled | Actions |
|---|
| Date | Trigger | Status | Result |
|---|
Webhooks
No webhooks configured for this environment.
Create a webhook to trigger automations from external services.
| Name | URL | Linked Automations | Last Received | Enabled | Actions |
|---|
| Date | Status | Automations Triggered | Payload |
|---|