Skip to content

docs: refine target discovery terms #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
zongqichen merged 1 commit into from
Sep 24, 2026
Merged

docs: refine target discovery terms #32

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .agents/skills/cfs/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: cfs
description: Safely select an existing cfs Cloud Foundry context and route CF CLI commands in cfs-managed workspaces, including parallel terminal or coding-agent workflows. Use for workspace-default or named-context selection, not for general Cloud Foundry deployment guidance.
description: Use cfs when parallel terminals, projects, Git worktrees, or coding agents need independent Cloud Foundry CLI sessions and targets without shared CF_HOME conflicts. Safely discover and select existing workspace-default or named contexts; not for general Cloud Foundry deployment guidance.
---

# Use cfs contexts
Expand Down
4 changes: 2 additions & 2 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,8 @@ contract may still change while cfs is pre-1.0.

### Changed

- Clarified multi-session discovery and documented how `cfs` differs from
manual `CF_HOME`, cf-targets-plugin, and cfctx workflows.
- Clarified multi-session and Agent Skill discovery, including how `cfs`
differs from manual `CF_HOME`, cf-targets-plugin, and cfctx workflows.

## [0.3.1] - 2026-09-24

Expand Down
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@
[![Release](https://img.shields.io/github/v/release/zongqichen/cloud-foundry-cli-contexts?include_prereleases&sort=semver)](https://github.com/zongqichen/cloud-foundry-cli-contexts/releases)
[![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)

Run multiple independent Cloud Foundry CLI sessions in parallel without shared
targets or `CF_HOME` collisions.
Run multiple Cloud Foundry CLI sessions and targets in parallel without
`CF_HOME` conflicts.

The official `cf` CLI keeps its active API, organization, space, and
authentication state in `$HOME/.cf`, so changing the target in one terminal
Expand Down
11 changes: 6 additions & 5 deletions docs/comparison.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,10 @@
# Cloud Foundry CLI context options
# Cloud Foundry CLI contexts for multiple sessions and targets

The official Cloud Foundry CLI stores its active API, organization, space, and
authentication state under `CF_HOME`. Terminals that share the same `CF_HOME`
therefore share one current target. Several tools address this in different
ways.
Multiple Cloud Foundry CLI sessions can use different targets in parallel when
their mutable state is isolated. The official CLI stores its active API,
organization, space, and authentication state under `CF_HOME`. Terminals that
share the same `CF_HOME` therefore share one current target. Several tools
address this in different ways.

| Approach | Isolation and selection | Keeps normal `cf` commands | Best fit |
| --- | --- | --- | --- |
Expand Down
Loading