Workspaces
Work with source code on your local PC or directly on IBM i (QSYS or IFS).
Selecting a workspace
IBM Bob Premium Package for i enables you to work exactly where your source code is — whether that is on your local PC or directly on IBM i. Before starting a new task, you can select the desired workspace to tell Bob where this source code lives and where it should work. In some cases, Bob can work outside a workspace or even across multiple workspaces if needed and with the appropriate permissions granted.
In addition to the standard local workspace, IBM Bob Premium Package for i adds two additional workspaces to enable IBM i developers to access source directly on IBM i. An active IBM i connection via Code for IBM i is required to see and use the Library List or Home Directory workspaces.
Local
Work with files and directories in your local workspace
Library List
Work with libraries, objects, and members in your library list.
Home Directory
Work with stream files or directories in your user profile's home directory
Local workspace
The Local workspace is any folder on your local PC which you open in Bob. This is the default workspace Bob will use. For IBM i developers, this could be an IBM i application which has been cloned from a GitHub repository onto a PC.
Even though you have designated Bob to work in a Local workspace, it can still access the IBM i to run CL commands, SQL statements, and PASE commands or even work on other source code in QSYS or the IFS if explicitly told to do so.
Library List workspace
The Library List workspace maps Code for IBM i's User Library List as a Bob task workspace. This allows you to inform Bob to work in a specific set of libraries in QSYS. For IBM i developers, this could be an IBM i application consisting of a set of libraries containing their source or compiled objects.
When using this workspace, Bob can still access other libraries outside the library list if needed. However, the purpose of designating the working set via the library list is to guide Bob on where to focus.
Even though a task is set to the Library List workspace, Bob can also access the IFS if explicitly told to do so. This can be handy when generating markdown or text files that are better stored in the IFS instead of QSYS.
Home Directory workspace
The Home Directory workspace maps your IBM i user profile's home directory (e.g. /home/<username>) as a Bob task workspace. This allows Bob to work on a specific set of stream files and directories in the IFS. For IBM i developers, this could be a set of scripts or documents stored in the IFS.
When using this workspace, Bob can still access other directories outside the home directory if needed. However, just like the Library List workspace, the purpose of designating the working directory to be the user's home directory is to guide Bob on where to focus.
Even though a task is set to the Home Directory workspace, Bob can also access QSYS if explicitly told to do so.
Task History
A task is always mapped to a specific workspace. When accessing the task history, you can filter your previous tasks by workspace to help you locate a specific task you would like to revisit.
Previous tasks mapped to the Library List or Home Directory workspaces will only be visible if connected to an IBM i.
Context mentions
Context mentions are supported across all IBM i workspaces, letting you tag specific items directly in the chat to give Bob precise and scoped context.
Library List workspace
- Libraries in the library list can be tagged directly using
@. - Members within a library can also be tagged, as long as the member is currently open in the editor.
Home Directory workspace
- Stream files and directories in the root of the home directory can be tagged directly using
@. - Other stream files (outside the root or in subdirectories) can also be tagged, as long as the stream file is currently open in the editor.