This tutorial by ego-lite focuses on the specific task in the title. Currently macOS is officially supported, Windows and Linux should still be checked according to the project roadmap; migrating the browser login session will expand the range of accounts that the Agent can access.
Below is a demonstration using a test environment and revocable data. When accounts, keys, machine control, investments or emergency communications are involved, manual confirmation must be done.
The difference between ego-lite, regular Chrome and automated browsers
This section only deals with “the differences between ego-lite, regular Chrome and automated browsers”. Save the current state first and then run the minimal test. Do not change multiple conditions at the same time.
|
|
For ego-lite, this boundary must be combined when judging the results: macOS is currently officially supported, Windows and Linux should still be checked according to the project roadmap; migrating the browser login session will expand the range of accounts that the Agent can access.
If the results are not repeatable, record the version, input, and logs, then narrow the scope of the test.
How Space isolates the Agent tab
It is recommended to execute in the following order:
- Check the actual version and source.
- Use a test account, test directory, or test device.
- Perform an undoable action.
- Save the output, exit code, or screenshot.
- Revert the changes and re-verify.
|
|
The completion criterion is that “How Space isolates Agent tabs” gets verifiable results, not that the command just doesn’t report an error.
What to check before installing ego-browser Skill
| Check items | Passing criteria | Stop signal |
|---|---|---|
| What to check before installing ego-browser Skill | Clear input, output and permission scope | The tool automatically expands the scope of operations |
| Source | Can return to the official warehouse or original data | Rely on unknown mirrors or second-hand conclusions |
| Security | No secret value in log | Token, cookie or private data present |
| Recovery | Ability to return to pre-execution state | No backup or undo methods |
|
|
When a stop signal appears, resume first and do not continue to the next step.
Only migrate one test Profile
This section only deals with “migrating only one test profile”. Save the current state first and then run the minimal test. Do not change multiple conditions at the same time.
|
|
For ego-lite, this boundary must be combined when judging the results: macOS is currently officially supported, Windows and Linux should still be checked according to the project roadmap; migrating the browser login session will expand the range of accounts that the Agent can access.
If the results are not repeatable, record the version, input, and logs, then narrow the scope of the test.
What are the risks of cookies, extensions and bookmarks?
It is recommended to execute in the following order:
- Check the actual version and source.
- Use a test account, test directory, or test device.
- Perform an undoable action.
- Save the output, exit code, or screenshot.
- Revert the changes and re-verify.
|
|
The completion standard is “what risks do cookies, extensions and bookmarks bring respectively” to obtain verifiable results, rather than the command just not reporting an error.
Give Codex a read-only web page task
| Check items | Passing criteria | Stop signal |
|---|---|---|
| Give Codex a read-only web page task | Input, output and permission scope are clear | Tool automatically expands the scope of operation |
| Source | Can return to the official warehouse or original data | Rely on unknown mirrors or second-hand conclusions |
| Security | No secret value in log | Token, cookie or private data present |
| Recovery | Ability to return to pre-execution state | No backup or undo methods |
|
|
When a stop signal appears, resume first and do not continue to the next step.
Verify that the Agent does not take over the user tab
This section only deals with “verifying that the agent has not taken over the user’s tab”. Save the current state first and then run the minimal test. Do not change multiple conditions at the same time.
|
|
For ego-lite, this boundary must be combined when judging the results: macOS is currently officially supported, Windows and Linux should still be checked according to the project roadmap; migrating the browser login session will expand the range of accounts that the Agent can access.
If the results are not repeatable, record the version, input, and logs, then narrow the scope of the test.
How to re-authorize after the login session is invalid?
It is recommended to execute in the following order:
- Check the actual version and source.
- Use a test account, test directory, or test device.
- Perform an undoable action.
- Save the output, exit code, or screenshot.
- Revert the changes and re-verify.
|
|
The completion standard is “how to re-authorize after the login session is invalid” to obtain a verifiable result, rather than the command not reporting an error.
Where should the downloaded file go?
| Check items | Passing criteria | Stop signal |
|---|---|---|
| Where the downloaded file should go | Clear input, output and permission scope | Tool automatically expands the scope of operation |
| Source | Can return to the official warehouse or original data | Rely on unknown mirrors or second-hand conclusions |
| Security | No secret value in log | Token, cookie or private data present |
| Recovery | Ability to return to pre-execution state | No backup or undo methods |
|
|
When a stop signal appears, resume first and do not continue to the next step.
Form submission boundaries in web tasks
This section only deals with “form submission boundaries in web tasks”. Save the current state first and then run the minimal test. Do not change multiple conditions at the same time.
|
|
For ego-lite, this boundary must be combined when judging the results: macOS is currently officially supported, Windows and Linux should still be checked according to the project roadmap; migrating the browser login session will expand the range of accounts that the Agent can access.
If the results are not repeatable, record the version, input, and logs, then narrow the scope of the test.
Do not allow sensitive input to appear in browser logs
It is recommended to execute in the following order:
- Check the actual version and source.
- Use a test account, test directory, or test device.
- Perform an undoable action.
- Save the output, exit code, or screenshot.
- Revert the changes and re-verify.
|
|
The completion standard is “no sensitive input appears in the browser log” to obtain verifiable results, rather than the command just not reporting an error.
Which process should be ended first when Space is stuck?
| Check items | Passing criteria | Stop signal |
|---|---|---|
| Which process should be terminated first when Space is stuck | Clear input, output and permission ranges | The tool automatically expands the scope of operations |
| Source | Can return to the official warehouse or original data | Rely on unknown mirrors or second-hand conclusions |
| Security | No secret value in log | Token, cookie or private data present |
| Recovery | Ability to return to pre-execution state | No backup or undo methods |
|
|
When a stop signal appears, resume first and do not continue to the next step.
What settings should be backed up before upgrading?
This section only deals with “which settings to back up before upgrading”. Save the current state first and then run the minimal test. Do not change multiple conditions at the same time.
|
|
For ego-lite, this boundary must be combined when judging the results: macOS is currently officially supported, Windows and Linux should still be checked according to the project roadmap; migrating the browser login session will expand the range of accounts that the Agent can access.
If the results are not repeatable, record the version, input, and logs, then narrow the scope of the test.
Windows users can now verify
It is recommended to execute in the following order:
- Check the actual version and source.
- Use a test account, test directory, or test device.
- Perform an undoable action.
- Save the output, exit code, or screenshot.
- Revert the changes and re-verify.
|
|
The completion standard is “verifications that Windows users can now do” to obtain verifiable results, rather than the command just not reporting an error.
A to-do list suitable for ego-lite
| Check items | Passing criteria | Stop signal |
|---|---|---|
| Task list suitable for ego-lite | Clear input, output and permission scope | Tool automatically expands the scope of operations |
| Source | Can return to the official warehouse or original data | Rely on unknown mirrors or second-hand conclusions |
| Security | No secret value in log | Token, cookie or private data present |
| Recovery | Ability to return to pre-execution state | No backup or undo methods |
|
|
When a stop signal appears, resume first and do not continue to the next step.
Delete the test space and do a final review
This section only deals with “final review after deleting the test space”. Save the current state first and then run the minimal test. Do not change multiple conditions at the same time.
|
|
For ego-lite, this boundary must be combined when judging the results: macOS is currently officially supported, Windows and Linux should still be checked according to the project roadmap; migrating the browser login session will expand the range of accounts that the Agent can access.
If the results are not repeatable, record the version, input, and logs, then narrow the scope of the test.
Which data in the main browser Profile will never be migrated
It is recommended to execute in the following order:
- Check the actual version and source.
- Use a test account, test directory, or test device.
- Perform an undoable action.
- Save the output, exit code, or screenshot.
- Revert the changes and re-verify.
|
|
The completion criterion is “which data in the main browser profile will never be migrated” to obtain a verifiable result, rather than the command just not reporting an error.
How to avoid task grabbing when two Spaces are running at the same time
| Check items | Passing criteria | Stop signal |
|---|---|---|
| How to avoid task grabbing when two Spaces are running at the same time | Clear input, output and permission ranges | Tools automatically expand the scope of operations |
| Source | Can return to the official warehouse or original data | Rely on unknown mirrors or second-hand conclusions |
| Security | No secret value in log | Token, cookie or private data present |
| Recovery | Ability to return to pre-execution state | No backup or undo methods |
|
|
When a stop signal appears, resume first and do not continue to the next step.
Re-do the login verification after upgrading the browser
This section only deals with “re-doing login verification after upgrading the browser”. Save the current state first and then run the minimal test. Do not change multiple conditions at the same time.
|
|
For ego-lite, this boundary must be combined when judging the results: macOS is currently officially supported, Windows and Linux should still be checked according to the project roadmap; migrating the browser login session will expand the range of accounts that the Agent can access.
If the results are not repeatable, record the version, input, and logs, then narrow the scope of the test.
ego-lite final check
- The versions and sources used are documented.
- Test input and formal data have been isolated.
- Commands, configurations and actual output can correspond.
- The failed path was actively tested at least once.
- Keys, accounts and private data do not enter Git or logs.
- There are clear actions for upgrading, stopping and resuming.
If you still can’t explain how the results are produced, keep ego-lite in the test environment without extending the permissions or replacing the existing stable process.