VibeControls
Vibes3 illustrations

Project Workspaces and Notes

Give each piece of work a project context carrying its branch, folder, environment variables, bound agents, sessions and notes.

These images are illustrations of the concept, not screenshots of the actual product.

Overview

A project workspace in VibeControls, called a vibe, is the context a piece of work happens in. It maps to a folder on a machine and carries the things that usually live in several different places: the repository branch, the environment variables, the agents and machines bound to it, the terminal sessions started under it, and the notes people wrote while working on it. This concept covers the list of those project contexts, one of them in detail, and the note editor inside it.

The problem is the setup tax. Returning to a project after a week away normally means finding the right folder, remembering which branch was checked out, re-exporting a set of environment variables and reconstructing what the last person tried. Nothing about that is intellectually interesting, and it is repeated every time context switches. The illustrated design makes the project context itself the object you open, so the setup travels with it.

The project list illustration shows a grid of cards with a count of how many projects are active. A banner explains that a project ties together the agent that runs your commands, along with sessions, notes, schedules and audit history. Search and filters for status and agent sit above the grid, and a bulk selection bar offers to activate or archive several projects at once. Each card carries the project name, a lifecycle badge, a one-line description, the current branch, the folder path, technology tags, member avatars, an environment variable count and an associated target.

The project overview illustration opens one of those cards. Tabs run across the top for overview, configuration, Git, sessions, notes, docs, a scorecard, catalogs, GraphQL, GitOps, security and related items, and an overflow menu exposes pausing, archiving and deleting. The body pairs a folder tree of the project context with a table of bound agents and machines, each showing its status, and beneath it a panel of environment variables, described as injected into every session started under the project, with secret values masked behind a lock icon and edit and delete controls on each row.

The note editor illustration shows the knowledge half of the same idea. A modal opens over the notes tab with an edit and preview toggle, a title field, an optional link to a project, removable tag chips and a markdown body holding headings, a bullet list and a fenced code block. A pin control and a visibility toggle decide whether the note stays at the top and whether the whole workspace can read it, so investigation notes become shared context rather than something lost in a private file.

What this concept shows

  • A project grid with a count of active projects, search, and filters for status and agent
  • Project cards showing lifecycle badges, current branch, folder path, technology tags, member avatars, an environment variable count and an associated target
  • A bulk selection bar for activating or archiving several projects at once
  • A project overview with tabs for configuration, Git, sessions, notes, docs, a scorecard, catalogs, GraphQL, GitOps, security and related items
  • A folder tree showing where the project sits inside a larger repository structure
  • A bound agents and targets table pairing each agent with its host and machine status, plus a control to set a default
  • An environment variables panel injected into every session started under the project, with secrets masked behind a lock icon
  • A markdown note editor with edit and preview modes, tag chips, a project link, a pin control and a workspace visibility toggle

How it works

  1. Open the projects view and scan the cards for lifecycle state, branch and technology tags.
  2. Filter by status or agent, or select several projects to activate or archive them together.
  3. Open a project to see its folder tree, the agents and machines bound to it, and their current status.
  4. Review the environment variables that will be injected into every session started under this project, with secret values masked.
  5. Set a default agent and target so new sessions start in the right place.
  6. Move to the notes tab and write up an investigation in markdown, adding tags and linking it to the project.
  7. Pin the note and decide whether it stays private or becomes visible to the whole workspace.

Who it's for

  • Developers switching between several projects in a week
  • Teams that need shared project setup rather than per-laptop configuration
  • On-call engineers writing up an investigation while it is fresh
  • Team leads onboarding new engineers into an existing codebase
  • Consultants juggling multiple client codebases and environments

Illustrations

3 illustrations of this concept. Select one to view it full size.

Project Workspace Grid

Project contexts as cards, each carrying branch, folder, tags, members and an environment variable count.

This illustration shows the projects view as a grid of cards. The heading pairs the section title with a count of how many projects are active, beside actions to add a project, refresh the list and open an overflow menu. A banner explains that a project workspace ties together the agent that runs your commands along with sessions, notes, schedules and audit history. A search field, a grid toggle and dropdown filters for status and agent sit above a bulk selection bar offering to select all visible items and to activate or archive the current selection, with the number selected shown between them. Six cards follow, each with a folder icon, the project name, a lifecycle badge reading active, degraded, archived, error or idle, a one-line description, the current branch, the folder path, technology tag chips, member avatars, an environment variable count and an associated target. All names are sample data.

Project Overview

One project in detail: folder tree, bound agents and targets, and injected environment variables.

This illustration shows the overview of one project workspace. The header pairs the project name with an active badge and a one-line description, beside controls for an assistant chat, sharing and a split create button, with an open overflow menu offering to pause, archive or delete the project. A wide tab row covers overview, configuration, Git, sessions, notes, docs, a scorecard, catalogs, GraphQL, GitOps, security and related items. The body pairs a project context card holding a folder tree, with the current project highlighted among its sibling folders, against a bound agents and targets table listing each agent with its online state, host machine, a default marker and a target chip carrying its own status. Beneath, an environment variables panel notes that the values are injected into every session started under this project, showing key and value pairs with secrets masked behind a lock icon and edit and delete controls per row. All values are sample data.

Project Note Editor

A markdown note editor with tags, a project link, a pin control and a workspace visibility toggle.

This illustration shows a note editor opening as a modal over the notes tab of a project workspace. The modal header pairs an edit heading with a toggle between editing and preview, plus a close control. A title field holds a sample investigation title, and beneath it sit a dropdown linking the note to a project and a tag field with three removable tag chips and a placeholder for adding more. The body is a markdown editing area showing a summary heading, a short paragraph, a findings heading with a bullet list, and a fenced code block containing a sample log line. A footer carries a checked pin control, a workspace visibility toggle and a save button. Behind the modal, note cards show titles, excerpts, small charts and status labels. The note content and tags are sample data.

Topics

  • project workspace for developers
  • environment variable management
  • masked secret environment variables
  • project context switching
  • bound agents and targets
  • markdown project notes
  • tagged engineering notes
  • repository branch and folder mapping
  • team project visibility
  • archive and activate projects
  • shared incident write up

Related concepts

All VibeControls concepts
Get started freeBrowse all concepts

We use cookies for essential site functions and, with your consent, for analytics to improve VibeControls. We don't use advertising or cross-site tracking cookies. See our Cookie Policy.

Preferences