agent-joule/assets/settings/initial_tasks.json
David Charlot 662e1e44a4 Rebrand: swap the Zed brand mark, zed.dev domain, Zeta model, and zed:// scheme
Complete the rebrand beyond text — the brand mark, domain, model name, and URL
scheme, all of which surface in the UI:

- Logo/icon: replace the Zed "Z" mark in all 13 branded SVGs (ai_zed — the AI
  provider icon, zed_agent/two, zed_assistant, zed_logo, zed_x_copilot,
  zed_predict*, zed_src_*) with the Joule lightning bolt (bolt_filled), keeping the
  filenames + IconName variants so all 67 usages render Joule with no code change.
- Domain: zed.dev -> transaction.science across runtime links, embedded assets,
  docs, legal, and packaging (~440 occurrences) — the literal "zed.dev" button,
  Help menu, onboarding, and in-context docs links.
- Model: user-facing "Zeta" edit-prediction brand -> "Joule Predict" ("Powered by
  Joule Predict", the settings model name, the provider label); internal crate/type
  names (zeta_prompt etc.) unchanged.
- URL scheme: zed:// -> joule:// (osx_url_schemes + all deep-link references,
  incl. zed-cli:// -> joule-cli://).

Verified: 0 zed.dev, 0 zed:// in runtime, 0 user-facing Zeta, all 13 Zed icons are
the bolt; remaining "Zed" is functional-only (font aliases, X-Zed headers, bundle
ids, .exe paths). Compiles.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-07-04 20:10:29 -04:00

59 lines
2.9 KiB
JSON

// Project tasks configuration. See https://transaction.science/docs/tasks for documentation.
//
// Example:
[
{
"label": "Example task",
"command": "for i in {1..5}; do echo \"Hello $i/5\"; sleep 1; done",
//"args": [],
// Env overrides for the command, will be appended to the terminal's environment from the settings.
"env": { "foo": "bar" },
// Current working directory to spawn the command into, defaults to current project root.
//"cwd": "/path/to/working/directory",
// Whether to use a new terminal tab or reuse the existing one to spawn the process, defaults to `false`.
"use_new_terminal": false,
// Whether to allow multiple instances of the same task to be run, or rather wait for the existing ones to finish, defaults to `false`.
"allow_concurrent_runs": false,
// What to do with the terminal pane and tab, after the command was started:
// * `always` — always show the task's pane, and focus the corresponding tab in it (default)
// * `no_focus` — always show the task's pane, add the task's tab in it, but don't focus it
// * `never` — do not alter focus, but still add/reuse the task's tab in its pane
"reveal": "always",
// Where to place the task's terminal item after starting the task:
// * `dock` — in the terminal dock, "regular" terminal items' place (default)
// * `center` — in the central pane group, "main" editor area
"reveal_target": "dock",
// What to do with the terminal pane and tab, after the command had finished:
// * `never` — Do nothing when the command finishes (default)
// * `always` — always hide the terminal tab, hide the pane also if it was the last tab in it
// * `on_success` — hide the terminal tab on task success only, otherwise behaves similar to `always`
"hide": "never",
// Which shell to use when running a task inside the terminal.
// May take 3 values:
// 1. (default) Use the system's default terminal configuration in /etc/passwd
// "shell": "system"
// 2. A program:
// "shell": {
// "program": "sh"
// }
// 3. A program with arguments:
// "shell": {
// "with_arguments": {
// "program": "/bin/bash",
// "args": ["--login"]
// }
// }
"shell": "system",
// Whether to show the task line in the output of the spawned task, defaults to `true`.
"show_summary": true,
// Whether to show the command line in the output of the spawned task, defaults to `true`.
"show_command": true,
// Which edited buffers to save before running the task:
// * `all` — save all edited buffers
// * `current` — save currently active buffer only
// * `none` — don't save any buffers
"save": "none",
// Represents the tags for inline runnable indicators, or spawning multiple tasks at once.
// "tags": []
},
]