Choose a workspace view
Open the global Workspace to see activity across repositories, or open Workspace from a repository to focus its Feed. The persistent Workspace panel shares the same session owner as the full Workspace page.
Repository selection changes the viewing context only. It does not create or start a Project, Join you to it, or authorize Factory work. Use Projects and workspaces for those actions.
Pick up daily work
| You want to… | Open |
|---|---|
| Find work or a question that needs you | Follow Feed evidence, then read and answer the thread |
| Understand why an issue waits | Identify the blocker and its owner |
| Open or return to your own shell | Open or reconnect to your terminal |
| Start or revise a saved request | Describe and save its direction |
| Review a candidate or delivered result | Inspect the candidate and confirm delivery |
| Find a decision or past answer | Search the library and assess its evidence |
| Recover an interrupted operation | Find the recovery procedure |
| Make your first human contribution | First connection |
| Prepare tools before automation | Project preparation |
Keep repository and session targets clear
The repository you are browsing, the repository attached to a saved build request, and the Project and account bound to an existing terminal are separate targets. Changing one does not silently change the others. Before acting, check the repository named on the page or request and the account and Project shown for a terminal.
Native Forgejo navigation preserves the live terminal attachment in the Workspace panel. Browsing another repository never retargets a terminal's Project, Linux account or session. If access expires, sign in again as the same native account and inspect the original workspace entry before retrying an action whose result is unclear.
Find applications and Factory activity
Use the Applications area to discover private applications available on the appliance. Opening the listing or an application link does not install or start an app. Application installation, lifecycle and app-local sign-in are covered in Private applications.
To follow and discuss Factory work, use the Factory Feed. Feed entries and native records require current repository visibility; reading them does not require Project Join. Each linked source or artifact retains its own access checks.
Live Factory terminal observation requires current code-write access. Watching a run does not provide terminal input or takeover authority. Opening your own shell requires explicit Join; People and access explains the separate permissions.
Manage session views
Workspace views do not own the work they display. A split adds another view of the same session, while hiding or closing a panel leaves its shell or Factory run in place. Reconnecting targets the retained session; it does not launch a replacement shell or resume a finished AI conversation. Human terminal inventory is limited to your own sessions.
To open your own browser terminal, follow Workspace terminals. To connect an editor over SSH, see Connect and develop. Those actions keep their own authority and lifecycle; navigating Workspace alone does not perform them.