Develop
Your organization's workspace for building, testing and looking after every app, signed in as yourself.
Develop is your organization's own workspace for the code behind its apps. Everybody in the organization opens it as themselves, from the dashboard, with no second account or password. In it you can:
- Talk to your code. Each project's code is read into a graph of what calls, imports and depends on what, which you can search and ask about, and chat about with the AI provider your organization chooses.
- Share one memory between coding assistants. Claude Code, Codex, Cursor and other tools that speak MCP connect to the workspace and work from the same graph, notes and task list, so what one learns the next can use.
- Build and test on every push. Connect a GitHub or GitLab repository to a project, and its pipeline runs on each push.
Every app's page has a Develop button that brings you here.
Turn it on
- Open Develop in the menu.
- Under Where it runs, choose CloudJod's servers or one of your clusters. On your own hardware, your code and pipelines stay on machines you control. A cluster with no servers yet is fine: the workspace starts when the first one joins.
- Press Turn on Develop. An owner or an admin can; anybody else is told who can.
The workspace is one of your organization's apps, called
workspace, in a project called develop. It takes
0.5 CPU, 512 MiB of memory and a 2 GiB disk from your
plan, wherever it runs. It is built from the
platform's own release the first time, which takes a minute or two. Its app
page shows its logs and builds like any other app.
Open it
Press Open workspace. A new tab opens and you are signed in as yourself. Behind it is a sign-in link that works once and only for 90 seconds, so an old link copied from a browser's history gets nobody in. A session in the workspace lasts 8 hours; after that, open it from CloudJod again. API tokens cannot open it: it is for people.
Who can do what
Your role in the workspace follows your role in the organization, and is set again every time you open it:
| In the organization | In the workspace |
|---|---|
| Owner | Owner |
| Admin trusted with every area | Admin: manages keys, providers and repositories |
| Member, or an admin whose areas include apps | Member: builds, tests and runs pipelines |
| Viewer, or anybody limited to areas without apps | Viewer: reads the code, notes and pipeline history |
Removing somebody from the organization, or any change that lowers their role, takes them out of the workspace and revokes every key they made there. If they still belong, they come back with their new role the next time they open it. The Develop page tells each person what they will be.
Inside the workspace
| Projects | Create one for each codebase. Its graph shows how many parts and links it found; Ask the graph searches it, or traces a path from one part to another. |
|---|---|
| Providers | An admin adds your organization's API key for Anthropic, OpenAI, Google, Mistral, DeepSeek, Groq, OpenRouter, xAI, Together, Fireworks, Qwen or Moonshot. Keys are encrypted and never shown again. |
| Connections | An admin chooses a project and presses Generate config to get the MCP configuration for a coding assistant; paste it into the assistant's settings and restart it. Connected tools are listed here. |
| Tasks | What the assistants are working on, and how far each task has got. |
| Admin | The workspace's API keys, its usage and its audit trail. Nobody is invited here: people join your organization on CloudJod's Team page. |
To use a model you run yourself, such as Ollama, give the workspace its
address: on the workspace app's Environment tab set
GFY_OLLAMA_BASE (or GFY_VLLM_BASE,
GFY_LMSTUDIO_BASE) to it, for example
http://ollama.internal:11434 for a private app called
ollama, then restart the workspace.
What to keep in mind
- Pipelines run inside the workspace's own container, as isolated as any app. Anybody who can run a pipeline can read everything in the workspace, so the apps area is for people you trust with your code and its keys.
- Turning the section off deletes the workspace and everything in it (projects, notes, keys and pipeline history). Only an owner can.
Next: Your own servers