Open or reconnect to your terminal
Open a browser terminal from Workspace:
- Join the intended repository Project using your native Forgejo account and confirm that it currently has code-write permission.
- In Workspace, select that Project and choose New terminal for a fresh shell. If a chooser appears, review Project and Terminal name, then choose Create terminal. The full Workspace page can start the new terminal directly for its selected Project.
- Confirm the resulting session is listed for your account and attached to the intended Project. Use Rename terminal in its Terminal actions menu to give it a recognizable name.
The terminal runs under your own Project-local Linux login. Browser development works without an SSH key or AI provider connection.
If the browser disconnects or the result is unclear, select the original terminal entry, confirm its Project and account, and choose Reconnect terminal when offered. Do not use New terminal to recover that shell. If the entry reports that the exact session ended, it cannot be reattached; choose New terminal only when you intend to start a different shell.
A terminal-support or maintenance error needs the host administrator's inspection of the retained Project. A sign-in or permission error needs the corresponding account or repository access corrected. Retry only after the original session state is clear.
Hiding or closing a view detaches it but keeps the session available; splitting adds a view of the same session rather than another shell. Confirmed End stops that terminal's supervised processes; the ended session cannot be reattached, while Project files and independent services remain.
Arrange and navigate session views
The terminal runs as your Project-local Linux login and keeps shell state in the Project. Select a session, split Workspace to add a view, or hide and show a view. Splits create views, not shells. Closing a tab or hiding the terminal detaches its view; reconnect through the retained session entry.
Use Rename terminal in the session actions to give the retained session a useful name, such as “README contribution”. Renaming identifies the same session; it does not create a shell or change its Project or account.
Native Forgejo navigation leaves the live terminal attached to its original Project and account, even while you browse another repository. A view does not change the session's owner or target.
The persistent Workspace panel keeps your Project terminal attached beside a native Forgejo page.
Resolve unavailable terminal states
| Observation | Next action |
|---|---|
| Project stopped | Ask its current owner or the configured operator to Start the same Project, then open a new terminal. Old processes are not revived. |
| Support mismatch | Ask the appliance administrator for the supported same-root terminal maintenance operation. Signing in again does not repair support. |
| Inspection unavailable | Retry inspection of the same Project; ask the operator to inspect if it persists. Do not infer missing data or create a replacement. |
| Maintenance in progress | Wait for administrator completion or recovery of the existing maintenance operation. Do not bypass the admission hold. |
| Sign-in expired or native session changed | Sign in as the intended account or refresh the changed session, then inspect your original terminal entry. |
| Membership or repository permission denied | Confirm repository permission and any Project access hold with the responsible owner; maintenance does not grant permission. |
A connection or support failure freezes input while preserving the original session locator and screen. Inspect that entry before retrying any action with an uncertain result; reconnecting never replays Create.
Observe Factory work
Human session inventory is limited to your own sessions. Current code-write authority permits live observation of Factory sessions, but Factory controls determine pause, cancellation, or takeover. Watching a Factory session never gives you input into its process.
Ended runs expose their candidate, findings, status, and check evidence. Their terminals cannot be reattached, and there is no transcript replay. Use Factory intervention to take over or return work to the normal human workflow.
End a human terminal
Save files and finish or deliberately stop in-process work before End. Unsaved editor buffers, shell state and running jobs in this terminal are lost when its supervised processes stop.
To end a managed human terminal, select End on that session and confirm only when you intend to stop its supervised processes. The confirmed End stops that terminal's processes but leaves files, independent SSH sessions, and Project services in place. Hide, close, and detach only change the view; they are not End.
For terminal-support repair, ask the host administrator to use Project maintenance. You can develop entirely in the browser terminal without SSH keys or an AI provider connection. For an external editor or file transfer, follow Connect and develop; for Project account lifecycle, see Projects and workspaces.