chore: rename package to opencode-synced

Author: iHildy

README.md

@@ -1,4 +1,4 @@
-# opencode-sync
+# opencode-synced
 
 Sync global OpenCode configuration across machines via a GitHub repo, with optional secrets support for private repos.
 
@@ -9,7 +9,7 @@ Sync global OpenCode configuration across machines via a GitHub repo, with optio
 - Optional session sync to share conversation history across machines
 - Optional prompt stash sync to share stashed prompts and history across machines
 - Startup auto-sync with restart toast
-- Per-machine overrides via `opencode-sync.overrides.jsonc`
+- Per-machine overrides via `opencode-synced.overrides.jsonc`
 - Custom `/sync-*` commands and `opencode_sync` tool
 
 ## Requirements
@@ -24,14 +24,14 @@ Enable the plugin in your global OpenCode config (OpenCode will install it on ne
 ```jsonc
 {
   "$schema": "https://opencode.ai/config.json",
-  "plugin": ["opencode-sync"],
+  "plugin": ["opencode-synced"],
 }
 ```
 
 OpenCode does not auto-update plugins. To update, remove the cached plugin and restart OpenCode:
 
 ```bash
-rm -rf ~/.cache/opencode/node_modules/opencode-sync
+rm -rf ~/.cache/opencode/node_modules/opencode-synced
 opencode
 ```
 
@@ -56,7 +56,7 @@ You can specify a custom repo name or use an organization:
 <details>
 <summary>Manual configuration</summary>
 
-Create `~/.config/opencode/opencode-sync.jsonc`:
+Create `~/.config/opencode/opencode-synced.jsonc`:
 
 ```jsonc
 {
@@ -129,7 +129,7 @@ Synced prompt data:
 Create a local-only overrides file at:
 
 ```
-~/.config/opencode/opencode-sync.overrides.jsonc
+~/.config/opencode/opencode-synced.overrides.jsonc
 ```
 
 Overrides are merged into the runtime config and re-applied to `opencode.json(c)` after pull.
@@ -155,7 +155,7 @@ Restart OpenCode to run the startup sync flow (pull remote, apply if changed, pu
 Inspect the local repo directly:
 
 ```bash
-cd ~/.local/share/opencode/opencode-sync/repo
+cd ~/.local/share/opencode/opencode-synced/repo
 git status
 git log --oneline -5
 ```
@@ -170,7 +170,7 @@ If the sync repo has uncommitted changes, you can:
 2. **Manual resolution**: Navigate to the repo and resolve manually:
 
 ```bash
-cd ~/.local/share/opencode/opencode-sync/repo
+cd ~/.local/share/opencode/opencode-synced/repo
 git status
 git pull --rebase
 ```

package.json

@@ -1,5 +1,5 @@
 {
-  "name": "opencode-sync",
+  "name": "opencode-synced",
   "version": "0.1.0",
   "description": "Sync global OpenCode config across machines via GitHub.",
   "author": {
@@ -14,7 +14,7 @@
   },
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/iHildy/opencode-sync.git"
+    "url": "git+https://github.com/iHildy/opencode-synced.git"
   },
   "publishConfig": {
     "access": "public"

src/command/sync-init.md

@@ -1,5 +1,5 @@
 ---
-description: Initialize opencode-sync configuration
+description: Initialize opencode-synced configuration
 ---
 
 Use the opencode_sync tool with command "init".

src/command/sync-status.md

@@ -1,4 +1,5 @@
 ---
-description: Show opencode-sync status
+description: Show opencode-synced status
 ---
+
 Use the opencode_sync tool with command "status" and report the results.

src/sync/commit.ts

@@ -34,7 +34,7 @@ export async function generateCommitMessage(
   let sessionId: string | null = null;
 
   try {
-    const sessionResult = await ctx.client.session.create({ body: { title: 'opencode-sync' } });
+    const sessionResult = await ctx.client.session.create({ body: { title: 'opencode-synced' } });
     const session = unwrapData<{ id: string }>(sessionResult);
     sessionId = session?.id ?? null;
     if (!sessionId) return fallback;

src/sync/config.ts

@@ -164,7 +164,7 @@ export async function writeJsonFile(
   options: { jsonc: boolean; mode?: number } = { jsonc: false }
 ): Promise<void> {
   const json = JSON.stringify(data, null, 2);
-  const content = options.jsonc ? `// Generated by opencode-sync\n${json}\n` : `${json}\n`;
+  const content = options.jsonc ? `// Generated by opencode-synced\n${json}\n` : `${json}\n`;
   await fs.writeFile(filePath, content, 'utf8');
   if (options.mode !== undefined) {
     await fs.chmod(filePath, options.mode);

src/sync/paths.test.ts

@@ -34,8 +34,8 @@ describe('resolveSyncLocations', () => {
     const locations = resolveSyncLocations(env, 'linux');
 
     expect(locations.configRoot).toBe('/custom/opencode');
-    expect(locations.syncConfigPath).toBe('/custom/opencode/opencode-sync.jsonc');
-    expect(locations.overridesPath).toBe('/custom/opencode/opencode-sync.overrides.jsonc');
+    expect(locations.syncConfigPath).toBe('/custom/opencode/opencode-synced.jsonc');
+    expect(locations.overridesPath).toBe('/custom/opencode/opencode-synced.overrides.jsonc');
   });
 });
 

src/sync/paths.ts

@@ -46,8 +46,8 @@ export interface SyncPlan {
 const DEFAULT_CONFIG_NAME = 'opencode.json';
 const DEFAULT_CONFIGC_NAME = 'opencode.jsonc';
 const DEFAULT_AGENTS_NAME = 'AGENTS.md';
-const DEFAULT_SYNC_CONFIG_NAME = 'opencode-sync.jsonc';
-const DEFAULT_OVERRIDES_NAME = 'opencode-sync.overrides.jsonc';
+const DEFAULT_SYNC_CONFIG_NAME = 'opencode-synced.jsonc';
+const DEFAULT_OVERRIDES_NAME = 'opencode-synced.overrides.jsonc';
 const DEFAULT_STATE_NAME = 'sync-state.json';
 
 const CONFIG_DIRS = ['agent', 'command', 'mode', 'tool', 'themes', 'plugin'];
@@ -112,7 +112,7 @@ export function resolveSyncLocations(
     syncConfigPath: path.join(configRoot, DEFAULT_SYNC_CONFIG_NAME),
     overridesPath: path.join(configRoot, DEFAULT_OVERRIDES_NAME),
     statePath: path.join(dataRoot, DEFAULT_STATE_NAME),
-    defaultRepoDir: path.join(dataRoot, 'opencode-sync', 'repo'),
+    defaultRepoDir: path.join(dataRoot, 'opencode-synced', 'repo'),
   };
 }
 

src/sync/service.ts

@@ -63,7 +63,7 @@ export function createSyncService(ctx: SyncServiceContext): SyncService {
     startupSync: async () => {
       const config = await loadSyncConfig(locations);
       if (!config) {
-        await showToast(ctx, 'Configure opencode-sync with /sync-init.', 'info');
+        await showToast(ctx, 'Configure opencode-synced with /sync-init.', 'info');
         return;
       }
       try {
@@ -75,7 +75,7 @@ export function createSyncService(ctx: SyncServiceContext): SyncService {
     status: async () => {
       const config = await loadSyncConfig(locations);
       if (!config) {
-        return 'opencode-sync is not configured. Run /sync-init to set it up.';
+        return 'opencode-synced is not configured. Run /sync-init to set it up.';
       }
 
       const repoRoot = resolveRepoRoot(config, locations);
@@ -145,7 +145,7 @@ export function createSyncService(ctx: SyncServiceContext): SyncService {
       await ensureSecretsPolicy(ctx, config);
 
       const lines = [
-        'opencode-sync configured.',
+        'opencode-synced configured.',
         `Repo: ${repoIdentifier}${created ? ' (created)' : ''}`,
         `Branch: ${resolveRepoBranch(config)}`,
         `Local repo: ${repoRoot}`,
@@ -320,7 +320,9 @@ async function getConfigOrThrow(
 ): Promise<ReturnType<typeof normalizeSyncConfig>> {
   const config = await loadSyncConfig(locations);
   if (!config) {
-    throw new SyncConfigMissingError('Missing opencode-sync config. Run /sync-init to set it up.');
+    throw new SyncConfigMissingError(
+      'Missing opencode-synced config. Run /sync-init to set it up.'
+    );
   }
   return config;
 }
@@ -414,7 +416,7 @@ async function showToast(
   message: string,
   variant: ToastVariant
 ): Promise<void> {
-  await ctx.client.tui.showToast({ body: { message: `opencode-sync: ${message}`, variant } });
+  await ctx.client.tui.showToast({ body: { message: `opencode-synced: ${message}`, variant } });
 }
 
 function formatError(error: unknown): string {
@@ -438,7 +440,7 @@ async function analyzeAndDecideResolution(
     const statusOutput = changes.join('\n');
 
     const prompt = [
-      'You are analyzing uncommitted changes in an opencode-sync repository.',
+      'You are analyzing uncommitted changes in an opencode-synced repository.',
       'Decide whether to commit these changes or discard them.',
       '',
       'IMPORTANT: Only choose "commit" if the changes appear to be legitimate config updates.',