Ego Lite

Keep browsing while an external coding agent works in an Ego Lite task Space. The ego-browser Skill connects the agent to a Chromium browser with imported login context, making account-specific reading and visible human handoffs possible.

Summarize an approved portal section

A small portal summary checks whether the task Space uses the intended account and preserves useful sources before delegating a larger report.

Portal URL, account/workspace, task Space, date range, fields, and desired report format.

Copy the request into a new Floatboat conversation and provide the required material.

Download Floatboat

Your request for Floatboat

Preview and copy the request. It is not sent automatically from this page.

Reference: Ego Lite
https://github.com/citrolabs/ego-lite

Read the original documentation and check the current environment and dependencies. Propose any new installation or tool connection before proceeding.

My task:
Use Ego Lite through ego-browser to read the approved portal section in a task Space. Confirm the account, collect only the fields I specify, and return source links without modifying records.

Expected deliverable:
A sourced summary with the inspected account and missing values. Include failed steps and unresolved questions when evidence is insufficient.

About Ego Lite

Ego Lite is CitroLabs’ Chromium-based browser for people and external coding agents. Rather than moving the entire conversation into a new browser assistant, the ego-browser connection lets the selected host operate pages. The official instructions name Cursor and Codex among shell-capable hosts. The task model and its reasoning remain with that external host.

An agent task uses a Space to organize its tabs while the person continues browsing elsewhere. Imported Chrome data can supply an existing login context, so a portal task may not need to start from a blank browser. A Space is an activity boundary, not a promise of independent credentials: inspect the selected account and workspace before interpreting the page’s data.

The official Skill bootstraps the installed version with ego-browser skill. That command returns the actual operating guide, so the browser’s current output governs commands and target selection rather than an old copied tutorial. Ego Lite supports macOS and Windows; Linux is on the roadmap. The GitHub tooling uses MIT, separately from bundled browser-component terms. Floatboat can use the corresponding shell-capable external-agent path after setup.

Share Browser Work Without Moving the Agent

Ego Lite combines a real browser, task Spaces, and version-matched agent instructions. Those parts support continuity and human visibility, but they do not decide which account is correct or where the host sends page observations for inference.

  • Task Spaces beside personal tabs

    Keep the agent’s research or portal work grouped in a Space so the user can see the task without surrendering every active tab. Grouping is not equivalent to a separate login profile.

  • Imported login continuity

    Existing browser data can make account-specific pages available. Check the application’s active account and selected organization, since a working session can still belong to the wrong workspace.

  • Runtime-supplied usage guide

    ego-browser skill prints instructions matched to the installed browser. Re-read after upgrade; a missing end-of-guide marker means the guide was truncated, not that the remaining instructions are optional.

Tasks That Need Browser Continuity and a Handoff

Use a Space when the work benefits from an existing login or must remain visible beside everyday browsing. Specify the account, target pages, and deliverable for each task; the person and agent may share a browser while still having different responsibilities.

Read a portal report for one workspace

Provide the portal URL, organization name, reporting period, and fields such as open items and overdue items. Let the agent read them in its task Space while the user keeps browsing. Return the selected organization and period with each value; if login or workspace differs, stop with that finding instead of producing a misleading report.

Research beside an ongoing browsing session

Give the agent a small set of public comparison pages and a question, such as which plans include an export feature. Group its evidence tabs in a Space and return the source passage for each plan. Separate a missing claim from an unavailable page, and leave useful sources open for review when requested.

Prepare a form for the user to finish

Provide a test or draft form, exact values, and a stopping point before submission. The agent fills and reads back the fields in its Space, then leaves the visible state for the user. If the application transforms a value, report the transformed value rather than assuming the supplied input was retained.

Reproduce an authenticated application defect

Use a dedicated approved account and provide one failing route or validation step. The agent reproduces the issue with the relevant login context and returns the path, observed state, and screenshot where useful. If it can only reproduce under another account, identify that difference rather than calling it the same test.

Prepare Ego Lite and the External Host

The first task below reads a small portal report. It assumes the browser and external host are connected, while account and report inputs come from the user. Installing a Skill alone cannot supply the browser or establish the correct application login.

  • Supported browser build

    Install a current macOS or Windows build and complete its onboarding. If ego-browser is missing or skill is an unknown command, follow the official install reference for that system instead of guessing a newer syntax.

  • Shell-capable host and full guide

    The host needs to run ego-browser skill and read its output. Confirm the line beginning [ego-browser:skill] end of guide is present; read saved output in parts if the response is truncated.

  • Account and report definition

    Supply the exact portal URL, approved account or organization, period, required fields, and read-only scope. Import browser data only through a deliberate user setup, not as an implied consequence of running the task.

Read a Portal Report in an Agent Space

The public Skill deliberately delegates operating details to the installed ego-browser guide. Follow that guide for exact command syntax, then use the sequence below to keep account selection, field reading, and the final report connected to one observable browser state.

  1. Load the installed guide completely

    Run ego-browser skill before browser work. Read its complete output and follow the operating and connection instructions it gives. If the CLI is absent or the output lacks its end marker, resolve installation or truncation first; do not invent open, snapshot, or Space commands from another browser tool.

  2. Open the portal in the task Space

    Use the guide’s task-Space workflow to open the supplied URL. Inspect the account, organization, and reporting period before reading numbers. If the browser shows a login or ambiguous organization choice, ask the user to resolve that state and continue only after the intended page is visible.

  3. Read fields and resolve ambiguity

    Use the installed guide’s snapshot and reading operations to locate the named fields. Record their displayed values and labels together, including the selected date range. A blank widget, loading placeholder, and actual zero are different outcomes; capture that distinction in the result.

  4. Return the report and visible handoff

    Return a compact field table with portal URL, account or organization, period, and missing data. Leave the task Space available when the user needs to review it, and explain any unresolved login or field issue. Do not clear browser state to repair a report; some clearing operations affect the whole profile.

Related Software Projects

Compare the workflows, operating requirements, and source licenses of these projects.

Ego Lite FAQ

Why run ego-browser skill rather than copy a command list?
Its output matches the installed browser version. The repository Skill is a bootstrap entry, and the runtime guide may change after upgrade. Re-read it when instructed, and resolve truncated output before following the workflow.
Does a Space isolate accounts?
Do not assume that. It organizes task activity and tabs, while login state can come from the same configured browser. Confirm the application account and workspace; use deliberate profile or account setup when separation is required.
Can I use it on Windows?
The official README and install references cover macOS and Windows. Linux remains on the roadmap. Use the current build and onboarding for the selected platform instead of inferring support from the fact that a Skill file can be copied there.
What if a login or imported account is wrong?
Stop before reading or changing account data and let the user select the intended account. Report the mismatch explicitly. Do not clear cookies or storage indiscriminately: the Skill warns that some clearing operations reach the whole browser profile.
Does the browser provide the task model?
The external-agent route uses the host selected by the user. Browser state can remain local while observations are sent to that host’s model provider. Imported login continuity does not change the inference location or grant a different model subscription.
What does this mean for Floatboat and licensing?
Floatboat can use the corresponding shell-capable agent path with the installed browser and official guidance. This does not imply a bundled browser or upstream endorsement. MIT covers the GitHub tooling; check browser-component and binary-distribution terms separately.