diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 00000000000..df559212d22
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,85 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+ and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+ overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+ advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+ address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement by emailing
+[hoakiet98@gmail.com](mailto:hoakiet98@gmail.com).
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at
+https://www.contributor-covenant.org/translations.
\ No newline at end of file
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index fe4d5d354be..6f765e1d3c8 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1 +1,28 @@
-Coming soon
\ No newline at end of file
+When contributing to this repository, please first discuss the change you wish to make via [issues](https://github.com/superset-sh/superset/issues) before making a change.
+
+Please note we have a [code of conduct](./CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
+
+## Pull Request Process
+
+1. To create a Pull Request (PR), [create a fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo) of the project.
+
+
+
+2. Create your changes in your fork and [open a PR from that fork.](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork)
+
+
+
+3. Update the PR description with details of the changes. Link the issue if relevant.
+
+4. Be sure to check the box to "Allow edits from maintainer". This allows maintainers to update your PR if necessary which speeds up the review process. [See more here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork).
+
+
+
+
+5. Request a review of one of the maintainers. Once accepted, they will be able to merge your PR.
+
+## Style guide
+
+We try to follow guidelines from [Clean Code](https://gist.github.com/wojteklu/73c6914cc446146b8b533c0988cf8d29) and the boy scoute rule:
+
+"Leave the code cleaner, not messier, than how you found it".
\ No newline at end of file
diff --git a/README.md b/README.md
index 207ba3c1919..7689c6c9ee4 100644
--- a/README.md
+++ b/README.md
@@ -3,26 +3,24 @@
-
- The last developer tool you'll ever need + Run 10+ parallel coding agents on your machine
[](https://x.com/superset_sh) -## Motivation -What do you do when your coding agent is running? Our answer is to start another coding task in parallel. The best developer can run 10+ tasks in parallel. - -With Superset, you can run 100. +## A Terminal Built for Coding Agents +Run 10+ CLI coding agents like Claude Code, Codex, etc. in parallel on your machine. +Spin up new coding tasks while waiting for your current agent to finish. Quickly switch between tasks as they need your attention. ## What you can do with Superset: - [X] Create and organize parallel coding environment - [X] Get notified when an agent needs your review -- [ ] Share context between your agents +- [ ] Share context between agents - [ ] Code on the go with a cloud environment - [ ] Automate reviewing and feedback - [ ] Create and manage Git pull requests @@ -31,46 +29,81 @@ With Superset, you can run 100. ## Getting Started - -[Download the app](https://superset.sh) or -[run locally](https://superset.sh). +Prerequesite: -### Usage +1. Install [Bun](https://bun.sh/) (package manager and Node runtime) + +2. Clone the repo from GitHub +``` +git clone https://github.com/superset-sh/superset.git +``` + +Install dependencies: +```bash +bun install +``` + +Run in dev mode: +```bash +bun install +bun run dev +``` + +Build desktop app: +```bash +bun run build +open apps/desktop/release +``` -For each parallel tasks, Superset uses git worktree to clone a new branch on your machine. +> [!NOTE] +> While Electron is cross-platform, Superset Desktop has only been built and tested on **macOS**. Other platforms are currently untested and may not work as expected. -Automate copying env variables, installing dependencies, etc. through the app or with a setup script `./superset/setup.json` +### Usage + +For each parallel tasks, Superset uses git worktree to clone a new branch on your machine. Automate copying env variables, installing dependencies, etc. through a setup script `./superset/setup.json` - - +
+