You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hides basecamp connect service (install, uninstall and status) until it's ready, and stops the connect skill telling assistants to install it.
Why it isn't ready:
The unit runs the connector in the home directory: systemd user units start there when no WorkingDirectory is set. Workers run in the connector's folder and may change files without asking, so a background agent could change anything in ~.
It freezes PATH at install, so upgrading Claude Code or Codex can quietly break it.
It's Linux-only, and most people will be on Macs, which need a separate launchd version.
It hasn't been tried on a real machine.
What changes:
The service command is Hidden and dropped from the command catalog and from basecamp connect --help. The help now says to start the connector in the folder it should work in and leave it running.
skills/basecamp-connect/SKILL.md covers:
the person runs cd '<folder>' && basecamp connect -P '<profile>' in their own terminal;
the folder is the agent's workspace, and never the home directory;
Ctrl-C is safe, and once it has run, a restarted connector catches up (its very first start begins at that moment);
"is it running?" is answered by the person's terminal, not by connect status, whose lock metadata is only a hint;
tmux or screen on a server.
It says there's no background service yet.
The code and its tests stay, for the follow-up that makes the service safe on Linux and Macs.
connect service was never in a release (v0.11.0 has no connect). Hidden commands are left out of .surface, so its 72 entries are acknowledged in .surface-breaking (appended, nothing else moved).
It pairs with #794, which stops guided setup offering the service. Either can land first.
Hides basecamp connect service (install and uninstall) until it's safe to hand out, and stops the connect skill from telling assistants to install it.
The service isn't ready: its systemd unit runs the connector in the home directory, where workers may change files without asking; it freezes PATH at install so upgrading Claude Code or Codex can quietly break it; it's Linux-only; and it hasn't been tried on a real machine.
Changes
service is now hidden from help and the command catalog; its 72 entries are appended to .surface-breaking (nothing else moved).
The help and skill now tell the person to run cd '<folder>' && basecamp connect -P '<profile>' in their own terminal, with the folder as the agent's workspace and never the home directory.
The skill documents that Ctrl-C is safe, catch-up begins once the connector has run, tmux/screen work on a server, and there is no background service yet.
connect status is a hint, not an answer, so "is it running?" goes to the person's terminal.
Code and tests stay for the follow-up that makes the service safe on Linux and Macs.
connect service was never in a release. Pairs with #794; either can land first.
Written for commit bb72ae2. Summary will update on new commits.
The service isn't ready to hand out. Its unit runs the connector in the
home directory, where workers may change files without asking; it freezes
PATH at install, so upgrading the worker can quietly break it; it is
Linux-only, where most people will be on Macs; and it hasn't been tried
on a real machine.
`connect service` is hidden from help and the command catalog, and the
connect skill no longer tells assistants to install it. It says instead
that the person starts the connector in the folder it should work in and
leaves it running, that stopping is safe, and that a restarted connector
catches up. The code and its tests stay for the follow-up that makes the
service safe on Linux and Macs.
The command was never in a release, so its removal from the surface
snapshot is acknowledged in .surface-breaking.
Hides the unfinished connector service while preserving its implementation for future work.
Changes:
Hides connect service from help and the command catalog.
Guides users to run the connector from its workspace.
Updates CLI surface baselines.
[!TIP]
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.
File
Description
skills/basecamp-connect/SKILL.md
Replaces service guidance with foreground operation instructions.
The connect skill said a restarted connector loses nothing, and that
`connect status` says whether a connector is running. Neither is quite
true. A connector with no stored feed position enters at the present, so
what was asked before its very first run isn't picked up. And status
only shows what the last connector wrote beside its lock: a crash leaves
that behind and a pid can be reused, so it's a hint, not an answer.
The skill now says catch-up starts once the connector has run, and sends
the question "is it running?" to the person's terminal.
Shell-quote folder and profile values in generated commands
skills/basecamp-connect/SKILL.md:495
The folder is also a variable in a copy-paste shell command, but this only requires quoting the profile. A workspace such as team's repo makes the substituted cd command malformed, and shell-active path text could be interpreted. Require POSIX shell-quoting for both values.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
github-actions
Bot
added
commands
Hides
basecamp connect service(install, uninstall and status) until it's ready, and stops the connect skill telling assistants to install it.Why it isn't ready:
WorkingDirectoryis set. Workers run in the connector's folder and may change files without asking, so a background agent could change anything in~.PATHat install, so upgrading Claude Code or Codex can quietly break it.What changes:
The
servicecommand isHiddenand dropped from the command catalog and frombasecamp connect --help. The help now says to start the connector in the folder it should work in and leave it running.skills/basecamp-connect/SKILL.mdcovers:cd '<folder>' && basecamp connect -P '<profile>'in their own terminal;connect status, whose lock metadata is only a hint;tmuxorscreenon a server.It says there's no background service yet.
The code and its tests stay, for the follow-up that makes the service safe on Linux and Macs.
connect servicewas never in a release (v0.11.0 has noconnect). Hidden commands are left out of.surface, so its 72 entries are acknowledged in.surface-breaking(appended, nothing else moved).It pairs with #794, which stops guided setup offering the service. Either can land first.
Card: https://app.basecamp.com/2914079/buckets/48699913/card_tables/cards/10356300973
Summary by cubic
Hides
basecamp connect service(install and uninstall) until it's safe to hand out, and stops the connect skill from telling assistants to install it.The service isn't ready: its systemd unit runs the connector in the home directory, where workers may change files without asking; it freezes PATH at install so upgrading Claude Code or Codex can quietly break it; it's Linux-only; and it hasn't been tried on a real machine.
Changes
serviceis now hidden from help and the command catalog; its 72 entries are appended to.surface-breaking(nothing else moved).cd '<folder>' && basecamp connect -P '<profile>'in their own terminal, with the folder as the agent's workspace and never the home directory.tmux/screenwork on a server, and there is no background service yet.connect statusis a hint, not an answer, so "is it running?" goes to the person's terminal.connect servicewas never in a release. Pairs with #794; either can land first.Written for commit bb72ae2. Summary will update on new commits.