Repository navigation
Releases
Marea 0.1.0-preview.39
Preview installation and updates
The commands below target 0.1.0-preview.39.
This preview updates Zod to 4.6.7 throughout the application and dependency tree,
fixing GHSA-mrhx-c7xc-m3w5.
Oversized constrained collections are rejected before validating their elements.
An included compatibility patch preserves existing Unicode passwords and protocol
text limits while keeping the upstream collection-size security fix.
It also updates both server Hono dependencies to 4.13.11 for
GHSA-5r4p-p66f-jhc7.
The protocol remains 0.1 and the database schema remains 14. Existing installations
retain their data, credentials and settings when updated.
Preview 35 validated the existing direct OTLP exporter against Langfuse 4.68.0
and added a repeatable check of the stored observations through the modern API.
No Langfuse SDK or collector migration is needed in Marea. See
Observability for verified fields, retry semantics and costs.
It also updated the dashboard build tool to Vite 8.2.4 to address
GHSA-587h-7wmj-h5pm.
Preview 34 fixed Windows installation and startup, including Windows PowerShell
5.1 on ARM64. Architecture detection uses the native processor, the bootstrap waits
for installation in the same console, and cleanup warnings preserve the installer's
result. All Marea executables explicitly run with the invoking user's privileges,
so installation and ordinary startup do not require administrator rights.
The complete bootstrap, managed launcher and uninstall are tested under a standard
Windows account on x64 and ARM64, with both PowerShell 5.1 and PowerShell 7.
Preview 33 added optional curriculum links to didactic SKILL.md files. Modules
can be identified by name, quoted code, or both; learning outcomes use numeric ra
values. Library search and module filters use these references. The bundled Testing
example corrects its former RA5 labels and links its own indicators to Programación
0485, RA3.f, with the normative source recorded in the Markdown.
If a class already uses the previous Testing revision, open Testing in Library,
choose Use in this class, and save the selection to use the corrected version
for new sessions. Existing sessions and individual selections retain their captured
version until the teacher changes those selections.
Generated skill drafts now appear directly in the editor with an undo action.
Creation belongs in Library; assigning and removing class skills have distinct labels.
The dashboard restores each teacher's saved language, including the choice made in
web setup. Visiting the server root opens the dashboard, and startup prints its URLs.
Managed server updates check installation ownership and offer abandoned-lock recovery
before downloading. The activation step still rechecks ownership to protect against
a server starting during the download. The database remains at schema 14, existing
sessions keep their frozen skill content, and compatible students continue to connect.
Download progress now distinguishes files received from verified files reused locally,
and reports the transferred bytes. The counter covers the whole signed inventory;
reused files are not presented as additional downloads.
Downloads are compressed,
and initial installations reuse the installer and signature verifier already
fetched by the bootstrap script. Updates reuse installed files only after their
bytes match the newly signed inventory; damaged or changed files are downloaded.
The signature verifier ships without debugging symbols, and application code is
minified. Every platform still includes its native runtime and works without a
separate Bun or Node installation.
Existing updaters remain compatible: releases also retain the original raw assets
and manifest format. Updating from preview 26 or earlier uses the old downloader
once; subsequent updates use compression and verified reuse. New installations
benefit immediately. Download sizes differ by platform and by the files changed
between releases.
This preview retains the Safari 17.1 dashboard fixes, interrupted-install recovery,
abandoned-lock recovery, stable password validation layout and restored Marea Code
heading from preview 26.
Fresh teacher installations open a browser setup wizard on their first launch.
Existing schools retain their data and settings. Earlier features remain available:
LAN HTTP, Google sign-in, provider model discovery, unlimited usage defaults,
the tutor writing gate, the example testing skill, session ZIP exports and optional
full-content observability through Langfuse or an OTLP collector.
Published installers and tags remain immutable.
Teacher server
macOS Apple Silicon or Linux x64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.39/install.sh | sh -s -- serverWindows x64, in PowerShell:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.39/install.ps1'))) -Component serverThe installer puts programs and launchers under ~/.marea-preview/server.
It does not ask for school data in the terminal. On Windows, reopen the terminal
after installation to pick up the per-user PATH entry, then run:
marea-teacherOn the first launch, a browser opens a five-step wizard:
- School, first class and teacher account, with password validation beside the fields.
- Provider key and model, with connection verification and model suggestions.
- Local-only, classroom LAN HTTP or a configured HTTPS origin; optional school accounts.
- Optional attention map, reports, automatic evaluation and example testing skill.
- Review and creation. Progress is visible while the installation is prepared.
The first class is saved in tutoring mode with student approval required for
project changes. Usage defaults to unlimited. Automatic evaluation is disabled
unless selected; enabling it also selects the bundled session-review method.
Optional map and report models initially use the verified main connection.
Prices, usage limits and separate feature models can be adjusted later in settings.
The local dashboard opens already signed in. HTTPS installations use their normal
login page. Further launches start the existing school without showing the wizard.
The LAN choice is remembered by the managed launcher.
If the browser cannot open, use the private setup link printed in the terminal
on the same computer. Setup listens only on loopback and requires the random
capability in that link, an exact Host and a same-origin POST. Passwords and API
keys remain in memory or private installation files; they are never put in the URL.
~/marea-prueba and other existing installations are not adopted or modified.
For HTTPS, choose an origin accessible from student computers and configure your
reverse proxy to forward to 127.0.0.1:18787 (or the chosen port), preserving the
public Host and Origin. Certificates, DNS and proxy setup are not provisioned by
the installer.
For a classroom LAN without a proxy or certificates, start with:
marea-teacher --allow-httpThe server listens on all IPv4 interfaces and prints the addresses students can
use. Open http://TEACHER_IP:18787/dashboard/ for the panel. Allow the selected
port through the teacher computer's firewall. HTTP carries passwords, sessions
and classroom traffic without encryption; use it only on a trusted network.
An explicit flag applies to that invocation. When LAN access was selected in the
first-run wizard, the managed launcher supplies the flag on subsequent launches.
Exact Host and Origin checks remain enabled for the computer's local IPs.
Download verification and release signatures are unchanged.
The student installation panel uses the running server's admitted addresses.
Opening the dashboard on localhost no longer puts localhost in student commands.
A single available address is selected automatically; when several networks are
available, choose the classroom address. A dashboard opened through a remote
HTTP or HTTPS address retains that address. With no reachable address, the panel
explains how to enable access instead of offering a loopback command.
After setup, change the model under Settings → Server and the teaching choices
under Settings → This class. New installations use the common connection and
model in every class. Installations with imported class-specific routes also
show the option to replace those routes. Additional classes still need their
teaching configuration saved before admitting students. API keys stay in the
private installation; do not include them in student installation commands.
Entering an OpenRouter key checks it and loads the account's available models.
The model field offers suggestions and also accepts a manually entered ID.
Selecting a catalog model fills its input/output prices, shown in USD per million
tokens; they remain editable. Unknown or manually entered models require a price
review. These estimates omit provider caching and discounts.
New model budgets have usage limits disabled; recorded usage and costs remain
available. Existing saved limits are preserved on update. To remove an old limit,
select Unlimited usage for the relevant purpose and save. Open sessions retain
the configuration they captured when they started.
Fresh installs and updates add testing only when the installation has no skill
with that name; an edited local copy is preserved. Manage selections and authoring in
Skills → This class / By student / Library. Personal selections replace the class
selection until Use the class selection is chosen. Updates to a selected personal
skill apply to new sessions; existing conversations retain their frozen content. See
[Skills workspace](SETUP-UX.md#skills-workspace...
Marea 0.1.0-preview.35
Preview installation and updates
The commands below target 0.1.0-preview.35.
This preview validates the existing direct OTLP exporter against Langfuse 4.68.0
and adds a repeatable check of the stored observations through the modern API.
No Langfuse SDK or collector migration is needed in Marea. See
Observability for verified fields, retry semantics and costs.
It also updates the dashboard build tool to Vite 8.2.4 to address
GHSA-587h-7wmj-h5pm.
Preview 34 fixed Windows installation and startup, including Windows PowerShell
5.1 on ARM64. Architecture detection uses the native processor, the bootstrap waits
for installation in the same console, and cleanup warnings preserve the installer's
result. All Marea executables explicitly run with the invoking user's privileges,
so installation and ordinary startup do not require administrator rights.
The complete bootstrap, managed launcher and uninstall are tested under a standard
Windows account on x64 and ARM64, with both PowerShell 5.1 and PowerShell 7.
Preview 33 added optional curriculum links to didactic SKILL.md files. Modules
can be identified by name, quoted code, or both; learning outcomes use numeric ra
values. Library search and module filters use these references. The bundled Testing
example corrects its former RA5 labels and links its own indicators to Programación
0485, RA3.f, with the normative source recorded in the Markdown.
If a class already uses the previous Testing revision, open Testing in Library,
choose Use in this class, and save the selection to use the corrected version
for new sessions. Existing sessions and individual selections retain their captured
version until the teacher changes those selections.
Generated skill drafts now appear directly in the editor with an undo action.
Creation belongs in Library; assigning and removing class skills have distinct labels.
The dashboard restores each teacher's saved language, including the choice made in
web setup. Visiting the server root opens the dashboard, and startup prints its URLs.
Managed server updates check installation ownership and offer abandoned-lock recovery
before downloading. The activation step still rechecks ownership to protect against
a server starting during the download. The database remains at schema 14, existing
sessions keep their frozen skill content, and compatible students continue to connect.
Download progress now distinguishes files received from verified files reused locally,
and reports the transferred bytes. The counter covers the whole signed inventory;
reused files are not presented as additional downloads.
Downloads are compressed,
and initial installations reuse the installer and signature verifier already
fetched by the bootstrap script. Updates reuse installed files only after their
bytes match the newly signed inventory; damaged or changed files are downloaded.
The signature verifier ships without debugging symbols, and application code is
minified. Every platform still includes its native runtime and works without a
separate Bun or Node installation.
Existing updaters remain compatible: releases also retain the original raw assets
and manifest format. Updating from preview 26 or earlier uses the old downloader
once; subsequent updates use compression and verified reuse. New installations
benefit immediately. Download sizes differ by platform and by the files changed
between releases.
This preview retains the Safari 17.1 dashboard fixes, interrupted-install recovery,
abandoned-lock recovery, stable password validation layout and restored Marea Code
heading from preview 26.
Fresh teacher installations open a browser setup wizard on their first launch.
Existing schools retain their data and settings. Earlier features remain available:
LAN HTTP, Google sign-in, provider model discovery, unlimited usage defaults,
the tutor writing gate, the example testing skill, session ZIP exports and optional
full-content observability through Langfuse or an OTLP collector.
Published installers and tags remain immutable.
Teacher server
macOS Apple Silicon or Linux x64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.35/install.sh | sh -s -- serverWindows x64, in PowerShell:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.35/install.ps1'))) -Component serverThe installer puts programs and launchers under ~/.marea-preview/server.
It does not ask for school data in the terminal. On Windows, reopen the terminal
after installation to pick up the per-user PATH entry, then run:
marea-teacherOn the first launch, a browser opens a five-step wizard:
- School, first class and teacher account, with password validation beside the fields.
- Provider key and model, with connection verification and model suggestions.
- Local-only, classroom LAN HTTP or a configured HTTPS origin; optional school accounts.
- Optional attention map, reports, automatic evaluation and example testing skill.
- Review and creation. Progress is visible while the installation is prepared.
The first class is saved in tutoring mode with student approval required for
project changes. Usage defaults to unlimited. Automatic evaluation is disabled
unless selected; enabling it also selects the bundled session-review method.
Optional map and report models initially use the verified main connection.
Prices, usage limits and separate feature models can be adjusted later in settings.
The local dashboard opens already signed in. HTTPS installations use their normal
login page. Further launches start the existing school without showing the wizard.
The LAN choice is remembered by the managed launcher.
If the browser cannot open, use the private setup link printed in the terminal
on the same computer. Setup listens only on loopback and requires the random
capability in that link, an exact Host and a same-origin POST. Passwords and API
keys remain in memory or private installation files; they are never put in the URL.
~/marea-prueba and other existing installations are not adopted or modified.
For HTTPS, choose an origin accessible from student computers and configure your
reverse proxy to forward to 127.0.0.1:18787 (or the chosen port), preserving the
public Host and Origin. Certificates, DNS and proxy setup are not provisioned by
the installer.
For a classroom LAN without a proxy or certificates, start with:
marea-teacher --allow-httpThe server listens on all IPv4 interfaces and prints the addresses students can
use. Open http://TEACHER_IP:18787/dashboard/ for the panel. Allow the selected
port through the teacher computer's firewall. HTTP carries passwords, sessions
and classroom traffic without encryption; use it only on a trusted network.
An explicit flag applies to that invocation. When LAN access was selected in the
first-run wizard, the managed launcher supplies the flag on subsequent launches.
Exact Host and Origin checks remain enabled for the computer's local IPs.
Download verification and release signatures are unchanged.
The student installation panel uses the running server's admitted addresses.
Opening the dashboard on localhost no longer puts localhost in student commands.
A single available address is selected automatically; when several networks are
available, choose the classroom address. A dashboard opened through a remote
HTTP or HTTPS address retains that address. With no reachable address, the panel
explains how to enable access instead of offering a loopback command.
After setup, change the model under Settings → Server and the teaching choices
under Settings → This class. New installations use the common connection and
model in every class. Installations with imported class-specific routes also
show the option to replace those routes. Additional classes still need their
teaching configuration saved before admitting students. API keys stay in the
private installation; do not include them in student installation commands.
Entering an OpenRouter key checks it and loads the account's available models.
The model field offers suggestions and also accepts a manually entered ID.
Selecting a catalog model fills its input/output prices, shown in USD per million
tokens; they remain editable. Unknown or manually entered models require a price
review. These estimates omit provider caching and discounts.
New model budgets have usage limits disabled; recorded usage and costs remain
available. Existing saved limits are preserved on update. To remove an old limit,
select Unlimited usage for the relevant purpose and save. Open sessions retain
the configuration they captured when they started.
Fresh installs and updates add testing only when the installation has no skill
with that name; an edited local copy is preserved. Manage selections and authoring in
Skills → This class / By student / Library. Personal selections replace the class
selection until Use the class selection is chosen. Updates to a selected personal
skill apply to new sessions; existing conversations retain their frozen content. See
Skills workspace.
The optional Google fields accept a desktop OAuth client ID, client secret and
school domain. Domain administration, OAuth consent and trusting the application
for minors still happen in Google Workspace. Group membership additionally needs
service-account configuration, explained in its own optional section. Administrators
can change these connections under Settings → Server → School accounts; saved
identity changes require a server restart. Class admission addresses and groups
remain under Settings → This class → Student access. These controls only
appear when the identity plugin is bundled. Model connections likewise come from
installed inference plugins; n...
Marea 0.1.0-preview.34
Preview installation and updates
The commands below target 0.1.0-preview.34.
This preview fixes Windows installation and startup, including Windows PowerShell
5.1 on ARM64. Architecture detection uses the native processor, the bootstrap waits
for installation in the same console, and cleanup warnings preserve the installer's
result. All Marea executables explicitly run with the invoking user's privileges,
so installation and ordinary startup do not require administrator rights.
The complete bootstrap, managed launcher and uninstall are tested under a standard
Windows account on x64 and ARM64, with both PowerShell 5.1 and PowerShell 7.
The previous preview added optional curriculum links to didactic SKILL.md files. Modules
can be identified by name, quoted code, or both; learning outcomes use numeric ra
values. Library search and module filters use these references. The bundled Testing
example corrects its former RA5 labels and links its own indicators to Programación
0485, RA3.f, with the normative source recorded in the Markdown.
If a class already uses the previous Testing revision, open Testing in Library,
choose Use in this class, and save the selection to use the corrected version
for new sessions. Existing sessions and individual selections retain their captured
version until the teacher changes those selections.
Generated skill drafts now appear directly in the editor with an undo action.
Creation belongs in Library; assigning and removing class skills have distinct labels.
The dashboard restores each teacher's saved language, including the choice made in
web setup. Visiting the server root opens the dashboard, and startup prints its URLs.
Managed server updates check installation ownership and offer abandoned-lock recovery
before downloading. The activation step still rechecks ownership to protect against
a server starting during the download. The database remains at schema 14, existing
sessions keep their frozen skill content, and compatible students continue to connect.
Download progress now distinguishes files received from verified files reused locally,
and reports the transferred bytes. The counter covers the whole signed inventory;
reused files are not presented as additional downloads.
Downloads are compressed,
and initial installations reuse the installer and signature verifier already
fetched by the bootstrap script. Updates reuse installed files only after their
bytes match the newly signed inventory; damaged or changed files are downloaded.
The signature verifier ships without debugging symbols, and application code is
minified. Every platform still includes its native runtime and works without a
separate Bun or Node installation.
Existing updaters remain compatible: releases also retain the original raw assets
and manifest format. Updating from preview 26 or earlier uses the old downloader
once; subsequent updates use compression and verified reuse. New installations
benefit immediately. Download sizes differ by platform and by the files changed
between releases.
This preview retains the Safari 17.1 dashboard fixes, interrupted-install recovery,
abandoned-lock recovery, stable password validation layout and restored Marea Code
heading from preview 26.
Fresh teacher installations open a browser setup wizard on their first launch.
Existing schools retain their data and settings. Earlier features remain available:
LAN HTTP, Google sign-in, provider model discovery, unlimited usage defaults,
the tutor writing gate, the example testing skill, session ZIP exports and optional
full-content observability through Langfuse or an OTLP collector.
Published installers and tags remain immutable.
Teacher server
macOS Apple Silicon or Linux x64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.34/install.sh | sh -s -- serverWindows x64, in PowerShell:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.34/install.ps1'))) -Component serverThe installer puts programs and launchers under ~/.marea-preview/server.
It does not ask for school data in the terminal. On Windows, reopen the terminal
after installation to pick up the per-user PATH entry, then run:
marea-teacherOn the first launch, a browser opens a five-step wizard:
- School, first class and teacher account, with password validation beside the fields.
- Provider key and model, with connection verification and model suggestions.
- Local-only, classroom LAN HTTP or a configured HTTPS origin; optional school accounts.
- Optional attention map, reports, automatic evaluation and example testing skill.
- Review and creation. Progress is visible while the installation is prepared.
The first class is saved in tutoring mode with student approval required for
project changes. Usage defaults to unlimited. Automatic evaluation is disabled
unless selected; enabling it also selects the bundled session-review method.
Optional map and report models initially use the verified main connection.
Prices, usage limits and separate feature models can be adjusted later in settings.
The local dashboard opens already signed in. HTTPS installations use their normal
login page. Further launches start the existing school without showing the wizard.
The LAN choice is remembered by the managed launcher.
If the browser cannot open, use the private setup link printed in the terminal
on the same computer. Setup listens only on loopback and requires the random
capability in that link, an exact Host and a same-origin POST. Passwords and API
keys remain in memory or private installation files; they are never put in the URL.
~/marea-prueba and other existing installations are not adopted or modified.
For HTTPS, choose an origin accessible from student computers and configure your
reverse proxy to forward to 127.0.0.1:18787 (or the chosen port), preserving the
public Host and Origin. Certificates, DNS and proxy setup are not provisioned by
the installer.
For a classroom LAN without a proxy or certificates, start with:
marea-teacher --allow-httpThe server listens on all IPv4 interfaces and prints the addresses students can
use. Open http://TEACHER_IP:18787/dashboard/ for the panel. Allow the selected
port through the teacher computer's firewall. HTTP carries passwords, sessions
and classroom traffic without encryption; use it only on a trusted network.
An explicit flag applies to that invocation. When LAN access was selected in the
first-run wizard, the managed launcher supplies the flag on subsequent launches.
Exact Host and Origin checks remain enabled for the computer's local IPs.
Download verification and release signatures are unchanged.
The student installation panel uses the running server's admitted addresses.
Opening the dashboard on localhost no longer puts localhost in student commands.
A single available address is selected automatically; when several networks are
available, choose the classroom address. A dashboard opened through a remote
HTTP or HTTPS address retains that address. With no reachable address, the panel
explains how to enable access instead of offering a loopback command.
After setup, change the model under Settings → Server and the teaching choices
under Settings → This class. New installations use the common connection and
model in every class. Installations with imported class-specific routes also
show the option to replace those routes. Additional classes still need their
teaching configuration saved before admitting students. API keys stay in the
private installation; do not include them in student installation commands.
Entering an OpenRouter key checks it and loads the account's available models.
The model field offers suggestions and also accepts a manually entered ID.
Selecting a catalog model fills its input/output prices, shown in USD per million
tokens; they remain editable. Unknown or manually entered models require a price
review. These estimates omit provider caching and discounts.
New model budgets have usage limits disabled; recorded usage and costs remain
available. Existing saved limits are preserved on update. To remove an old limit,
select Unlimited usage for the relevant purpose and save. Open sessions retain
the configuration they captured when they started.
Fresh installs and updates add testing only when the installation has no skill
with that name; an edited local copy is preserved. Manage selections and authoring in
Skills → This class / By student / Library. Personal selections replace the class
selection until Use the class selection is chosen. Updates to a selected personal
skill apply to new sessions; existing conversations retain their frozen content. See
Skills workspace.
The optional Google fields accept a desktop OAuth client ID, client secret and
school domain. Domain administration, OAuth consent and trusting the application
for minors still happen in Google Workspace. Group membership additionally needs
service-account configuration, explained in its own optional section. Administrators
can change these connections under Settings → Server → School accounts; saved
identity changes require a server restart. Class admission addresses and groups
remain under Settings → This class → Student access. These controls only
appear when the identity plugin is bundled. Model connections likewise come from
installed inference plugins; neither the wizard nor the dashboard requires OpenRouter.
If a model provider is removed, the server can still start so its administrator can
select a replacement. Saved credentials are retained, but never read for absent plugins.
Under Settings → This class, Tutor writing gate offers Off, Block the first
attempt, and Block up to three attempts. It pauses exercise-code writes/edits
without a prior structured questi...
Marea 0.1.0-preview.33
Preview installation and updates
The commands below target 0.1.0-preview.33.
This preview adds optional curriculum links to didactic SKILL.md files. Modules
can be identified by name, quoted code, or both; learning outcomes use numeric ra
values. Library search and module filters use these references. The bundled Testing
example corrects its former RA5 labels and links its own indicators to Programación
0485, RA3.f, with the normative source recorded in the Markdown.
If a class already uses the previous Testing revision, open Testing in Library,
choose Use in this class, and save the selection to use the corrected version
for new sessions. Existing sessions and individual selections retain their captured
version until the teacher changes those selections.
Generated skill drafts now appear directly in the editor with an undo action.
Creation belongs in Library; assigning and removing class skills have distinct labels.
The dashboard restores each teacher's saved language, including the choice made in
web setup. Visiting the server root opens the dashboard, and startup prints its URLs.
Managed server updates check installation ownership and offer abandoned-lock recovery
before downloading. The activation step still rechecks ownership to protect against
a server starting during the download. The database remains at schema 14, existing
sessions keep their frozen skill content, and compatible students continue to connect.
Download progress now distinguishes files received from verified files reused locally,
and reports the transferred bytes. The counter covers the whole signed inventory;
reused files are not presented as additional downloads.
Downloads are compressed,
and initial installations reuse the installer and signature verifier already
fetched by the bootstrap script. Updates reuse installed files only after their
bytes match the newly signed inventory; damaged or changed files are downloaded.
The signature verifier ships without debugging symbols, and application code is
minified. Every platform still includes its native runtime and works without a
separate Bun or Node installation.
Existing updaters remain compatible: releases also retain the original raw assets
and manifest format. Updating from preview 26 or earlier uses the old downloader
once; subsequent updates use compression and verified reuse. New installations
benefit immediately. Download sizes differ by platform and by the files changed
between releases.
This preview retains the Safari 17.1 dashboard fixes, interrupted-install recovery,
abandoned-lock recovery, stable password validation layout and restored Marea Code
heading from preview 26.
Fresh teacher installations open a browser setup wizard on their first launch.
Existing schools retain their data and settings. Earlier features remain available:
LAN HTTP, Google sign-in, provider model discovery, unlimited usage defaults,
the tutor writing gate, the example testing skill, session ZIP exports and optional
full-content observability through Langfuse or an OTLP collector.
Published installers and tags remain immutable.
Teacher server
macOS Apple Silicon or Linux x64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.33/install.sh | sh -s -- serverWindows x64, in PowerShell:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.33/install.ps1'))) -Component serverThe installer puts programs and launchers under ~/.marea-preview/server.
It does not ask for school data in the terminal. On Windows, reopen the terminal
after installation to pick up the per-user PATH entry, then run:
marea-teacherOn the first launch, a browser opens a five-step wizard:
- School, first class and teacher account, with password validation beside the fields.
- Provider key and model, with connection verification and model suggestions.
- Local-only, classroom LAN HTTP or a configured HTTPS origin; optional school accounts.
- Optional attention map, reports, automatic evaluation and example testing skill.
- Review and creation. Progress is visible while the installation is prepared.
The first class is saved in tutoring mode with student approval required for
project changes. Usage defaults to unlimited. Automatic evaluation is disabled
unless selected; enabling it also selects the bundled session-review method.
Optional map and report models initially use the verified main connection.
Prices, usage limits and separate feature models can be adjusted later in settings.
The local dashboard opens already signed in. HTTPS installations use their normal
login page. Further launches start the existing school without showing the wizard.
The LAN choice is remembered by the managed launcher.
If the browser cannot open, use the private setup link printed in the terminal
on the same computer. Setup listens only on loopback and requires the random
capability in that link, an exact Host and a same-origin POST. Passwords and API
keys remain in memory or private installation files; they are never put in the URL.
~/marea-prueba and other existing installations are not adopted or modified.
For HTTPS, choose an origin accessible from student computers and configure your
reverse proxy to forward to 127.0.0.1:18787 (or the chosen port), preserving the
public Host and Origin. Certificates, DNS and proxy setup are not provisioned by
the installer.
For a classroom LAN without a proxy or certificates, start with:
marea-teacher --allow-httpThe server listens on all IPv4 interfaces and prints the addresses students can
use. Open http://TEACHER_IP:18787/dashboard/ for the panel. Allow the selected
port through the teacher computer's firewall. HTTP carries passwords, sessions
and classroom traffic without encryption; use it only on a trusted network.
An explicit flag applies to that invocation. When LAN access was selected in the
first-run wizard, the managed launcher supplies the flag on subsequent launches.
Exact Host and Origin checks remain enabled for the computer's local IPs.
Download verification and release signatures are unchanged.
The student installation panel uses the running server's admitted addresses.
Opening the dashboard on localhost no longer puts localhost in student commands.
A single available address is selected automatically; when several networks are
available, choose the classroom address. A dashboard opened through a remote
HTTP or HTTPS address retains that address. With no reachable address, the panel
explains how to enable access instead of offering a loopback command.
After setup, change the model under Settings → Server and the teaching choices
under Settings → This class. New installations use the common connection and
model in every class. Installations with imported class-specific routes also
show the option to replace those routes. Additional classes still need their
teaching configuration saved before admitting students. API keys stay in the
private installation; do not include them in student installation commands.
Entering an OpenRouter key checks it and loads the account's available models.
The model field offers suggestions and also accepts a manually entered ID.
Selecting a catalog model fills its input/output prices, shown in USD per million
tokens; they remain editable. Unknown or manually entered models require a price
review. These estimates omit provider caching and discounts.
New model budgets have usage limits disabled; recorded usage and costs remain
available. Existing saved limits are preserved on update. To remove an old limit,
select Unlimited usage for the relevant purpose and save. Open sessions retain
the configuration they captured when they started.
Fresh installs and updates add testing only when the installation has no skill
with that name; an edited local copy is preserved. Manage selections and authoring in
Skills → This class / By student / Library. Personal selections replace the class
selection until Use the class selection is chosen. Updates to a selected personal
skill apply to new sessions; existing conversations retain their frozen content. See
Skills workspace.
The optional Google fields accept a desktop OAuth client ID, client secret and
school domain. Domain administration, OAuth consent and trusting the application
for minors still happen in Google Workspace. Group membership additionally needs
service-account configuration, explained in its own optional section. Administrators
can change these connections under Settings → Server → School accounts; saved
identity changes require a server restart. Class admission addresses and groups
remain under Settings → This class → Student access. These controls only
appear when the identity plugin is bundled. Model connections likewise come from
installed inference plugins; neither the wizard nor the dashboard requires OpenRouter.
If a model provider is removed, the server can still start so its administrator can
select a replacement. Saved credentials are retained, but never read for absent plugins.
Under Settings → This class, Tutor writing gate offers Off, Block the first
attempt, and Block up to three attempts. It pauses exercise-code writes/edits
without a prior structured question in the current student turn. The attempt limit
prevents an endless retry loop. Student approval is still required afterward. Setup
files, shell commands and free mode are excluded. New classes start with the first-attempt
mode; existing classes keep their previous behavior. Changes affect new sessions only.
Clients predating this feature must run marea update before joining a class that
enables it. Restarting the client does not reset the policy or retry history of a turn.
Session exports and optional observability
Teachers can download conversations, events a...
Marea 0.1.0-preview.31
Preview installation and updates
The commands below target 0.1.0-preview.31.
This preview makes SKILL.md the visible, editable source of every skill. Creation
starts with a Markdown template and a guide. Teachers can generate a draft using the
configured model, the complete Testing example and their own topics and criteria,
then review and edit it before saving. Personal skills can be deleted after reviewing
the class and individual assignments that will be withdrawn. Existing conversations
retain their frozen content; existing companion files are preserved when editing.
The Skills workspace retains class selections, persistent per-student selections,
bulk personalization and the personal library from preview 29. The database remains
at schema 14 and compatible students continue to connect.
Download progress now distinguishes files received from verified files reused locally,
and reports the transferred bytes. The counter covers the whole signed inventory;
reused files are not presented as additional downloads.
Downloads are compressed,
and initial installations reuse the installer and signature verifier already
fetched by the bootstrap script. Updates reuse installed files only after their
bytes match the newly signed inventory; damaged or changed files are downloaded.
The signature verifier ships without debugging symbols, and application code is
minified. Every platform still includes its native runtime and works without a
separate Bun or Node installation.
Existing updaters remain compatible: releases also retain the original raw assets
and manifest format. Updating from preview 26 or earlier uses the old downloader
once; subsequent updates use compression and verified reuse. New installations
benefit immediately. Download sizes differ by platform and by the files changed
between releases.
This preview retains the Safari 17.1 dashboard fixes, interrupted-install recovery,
abandoned-lock recovery, stable password validation layout and restored Marea Code
heading from preview 26.
Fresh teacher installations open a browser setup wizard on their first launch.
Existing schools retain their data and settings. Earlier features remain available:
LAN HTTP, Google sign-in, provider model discovery, unlimited usage defaults,
the tutor writing gate, the example testing skill, session ZIP exports and optional
full-content observability through Langfuse or an OTLP collector.
Published installers and tags remain immutable.
Teacher server
macOS Apple Silicon or Linux x64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.31/install.sh | sh -s -- serverWindows x64, in PowerShell:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.31/install.ps1'))) -Component serverThe installer puts programs and launchers under ~/.marea-preview/server.
It does not ask for school data in the terminal. On Windows, reopen the terminal
after installation to pick up the per-user PATH entry, then run:
marea-teacherOn the first launch, a browser opens a five-step wizard:
- School, first class and teacher account, with password validation beside the fields.
- Provider key and model, with connection verification and model suggestions.
- Local-only, classroom LAN HTTP or a configured HTTPS origin; optional school accounts.
- Optional attention map, reports, automatic evaluation and example testing skill.
- Review and creation. Progress is visible while the installation is prepared.
The first class is saved in tutoring mode with student approval required for
project changes. Usage defaults to unlimited. Automatic evaluation is disabled
unless selected; enabling it also selects the bundled session-review method.
Optional map and report models initially use the verified main connection.
Prices, usage limits and separate feature models can be adjusted later in settings.
The local dashboard opens already signed in. HTTPS installations use their normal
login page. Further launches start the existing school without showing the wizard.
The LAN choice is remembered by the managed launcher.
If the browser cannot open, use the private setup link printed in the terminal
on the same computer. Setup listens only on loopback and requires the random
capability in that link, an exact Host and a same-origin POST. Passwords and API
keys remain in memory or private installation files; they are never put in the URL.
~/marea-prueba and other existing installations are not adopted or modified.
For HTTPS, choose an origin accessible from student computers and configure your
reverse proxy to forward to 127.0.0.1:18787 (or the chosen port), preserving the
public Host and Origin. Certificates, DNS and proxy setup are not provisioned by
the installer.
For a classroom LAN without a proxy or certificates, start with:
marea-teacher --allow-httpThe server listens on all IPv4 interfaces and prints the addresses students can
use. Open http://TEACHER_IP:18787/dashboard/ for the panel. Allow the selected
port through the teacher computer's firewall. HTTP carries passwords, sessions
and classroom traffic without encryption; use it only on a trusted network.
An explicit flag applies to that invocation. When LAN access was selected in the
first-run wizard, the managed launcher supplies the flag on subsequent launches.
Exact Host and Origin checks remain enabled for the computer's local IPs.
Download verification and release signatures are unchanged.
The student installation panel uses the running server's admitted addresses.
Opening the dashboard on localhost no longer puts localhost in student commands.
A single available address is selected automatically; when several networks are
available, choose the classroom address. A dashboard opened through a remote
HTTP or HTTPS address retains that address. With no reachable address, the panel
explains how to enable access instead of offering a loopback command.
After setup, change the model under Settings → Server and the teaching choices
under Settings → This class. New installations use the common connection and
model in every class. Installations with imported class-specific routes also
show the option to replace those routes. Additional classes still need their
teaching configuration saved before admitting students. API keys stay in the
private installation; do not include them in student installation commands.
Entering an OpenRouter key checks it and loads the account's available models.
The model field offers suggestions and also accepts a manually entered ID.
Selecting a catalog model fills its input/output prices, shown in USD per million
tokens; they remain editable. Unknown or manually entered models require a price
review. These estimates omit provider caching and discounts.
New model budgets have usage limits disabled; recorded usage and costs remain
available. Existing saved limits are preserved on update. To remove an old limit,
select Unlimited usage for the relevant purpose and save. Open sessions retain
the configuration they captured when they started.
Fresh installs and updates add testing only when the installation has no skill
with that name; an edited local copy is preserved. Manage selections and authoring in
Skills → This class / By student / Library. Personal selections replace the class
selection until Use the class selection is chosen. Updates to a selected personal
skill apply to new sessions; existing conversations retain their frozen content. See
Skills workspace.
The optional Google fields accept a desktop OAuth client ID, client secret and
school domain. Domain administration, OAuth consent and trusting the application
for minors still happen in Google Workspace. Group membership additionally needs
service-account configuration, explained in its own optional section. Administrators
can change these connections under Settings → Server → School accounts; saved
identity changes require a server restart. Class admission addresses and groups
remain under Settings → This class → Student access. These controls only
appear when the identity plugin is bundled. Model connections likewise come from
installed inference plugins; neither the wizard nor the dashboard requires OpenRouter.
If a model provider is removed, the server can still start so its administrator can
select a replacement. Saved credentials are retained, but never read for absent plugins.
Under Settings → This class, Tutor writing gate offers Off, Block the first
attempt, and Block up to three attempts. It pauses exercise-code writes/edits
without a prior structured question in the current student turn. The attempt limit
prevents an endless retry loop. Student approval is still required afterward. Setup
files, shell commands and free mode are excluded. New classes start with the first-attempt
mode; existing classes keep their previous behavior. Changes affect new sessions only.
Clients predating this feature must run marea update before joining a class that
enables it. Restarting the client does not reset the policy or retry history of a turn.
Session exports and optional observability
Teachers can download conversations, events and usage from Sessions, filtered
by class, student and UTC dates, using names or pseudonyms. Administrators can
configure Settings → Server → External traces, test a synthetic connection, and
explicitly enable delivery with content. Langfuse supports self-hosted base URLs;
OTLP accepts an HTTP collector. No student-side credentials are needed.
Managed updates back up and migrate the database to schema 14. Export authorization,
content limits, retries and local/external retention are documented in
Observability. Existing clients remain compatible; their traces
contain only the diagnostic detail they actually r...
Marea 0.1.0-preview.29
Preview installation and updates
The commands below target 0.1.0-preview.29.
This preview introduces the Skills workspace: class selections, persistent
per-student selections and an editable personal library. Teachers can search and
choose skills without moving rows, personalize several students at once, create a
version of an included skill and edit its name, instructions and optional materials.
Updated selections apply to new sessions; ongoing conversations retain their content.
Managed server updates back up and migrate the database to schema 14.
Download progress now distinguishes files received from verified files reused locally,
and reports the transferred bytes. The counter covers the whole signed inventory;
reused files are not presented as additional downloads.
Downloads are compressed,
and initial installations reuse the installer and signature verifier already
fetched by the bootstrap script. Updates reuse installed files only after their
bytes match the newly signed inventory; damaged or changed files are downloaded.
The signature verifier ships without debugging symbols, and application code is
minified. Every platform still includes its native runtime and works without a
separate Bun or Node installation.
Existing updaters remain compatible: releases also retain the original raw assets
and manifest format. Updating from preview 26 or earlier uses the old downloader
once; subsequent updates use compression and verified reuse. New installations
benefit immediately. Download sizes differ by platform and by the files changed
between releases.
This preview retains the Safari 17.1 dashboard fixes, interrupted-install recovery,
abandoned-lock recovery, stable password validation layout and restored Marea Code
heading from preview 26.
Fresh teacher installations open a browser setup wizard on their first launch.
Existing schools retain their data and settings. Earlier features remain available:
LAN HTTP, Google sign-in, provider model discovery, unlimited usage defaults,
the tutor writing gate, the example testing skill, session ZIP exports and optional
full-content observability through Langfuse or an OTLP collector.
Published installers and tags remain immutable.
Teacher server
macOS Apple Silicon or Linux x64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.29/install.sh | sh -s -- serverWindows x64, in PowerShell:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.29/install.ps1'))) -Component serverThe installer puts programs and launchers under ~/.marea-preview/server.
It does not ask for school data in the terminal. On Windows, reopen the terminal
after installation to pick up the per-user PATH entry, then run:
marea-teacherOn the first launch, a browser opens a five-step wizard:
- School, first class and teacher account, with password validation beside the fields.
- Provider key and model, with connection verification and model suggestions.
- Local-only, classroom LAN HTTP or a configured HTTPS origin; optional school accounts.
- Optional attention map, reports, automatic evaluation and example testing skill.
- Review and creation. Progress is visible while the installation is prepared.
The first class is saved in tutoring mode with student approval required for
project changes. Usage defaults to unlimited. Automatic evaluation is disabled
unless selected; enabling it also selects the bundled session-review method.
Optional map and report models initially use the verified main connection.
Prices, usage limits and separate feature models can be adjusted later in settings.
The local dashboard opens already signed in. HTTPS installations use their normal
login page. Further launches start the existing school without showing the wizard.
The LAN choice is remembered by the managed launcher.
If the browser cannot open, use the private setup link printed in the terminal
on the same computer. Setup listens only on loopback and requires the random
capability in that link, an exact Host and a same-origin POST. Passwords and API
keys remain in memory or private installation files; they are never put in the URL.
~/marea-prueba and other existing installations are not adopted or modified.
For HTTPS, choose an origin accessible from student computers and configure your
reverse proxy to forward to 127.0.0.1:18787 (or the chosen port), preserving the
public Host and Origin. Certificates, DNS and proxy setup are not provisioned by
the installer.
For a classroom LAN without a proxy or certificates, start with:
marea-teacher --allow-httpThe server listens on all IPv4 interfaces and prints the addresses students can
use. Open http://TEACHER_IP:18787/dashboard/ for the panel. Allow the selected
port through the teacher computer's firewall. HTTP carries passwords, sessions
and classroom traffic without encryption; use it only on a trusted network.
An explicit flag applies to that invocation. When LAN access was selected in the
first-run wizard, the managed launcher supplies the flag on subsequent launches.
Exact Host and Origin checks remain enabled for the computer's local IPs.
Download verification and release signatures are unchanged.
The student installation panel uses the running server's admitted addresses.
Opening the dashboard on localhost no longer puts localhost in student commands.
A single available address is selected automatically; when several networks are
available, choose the classroom address. A dashboard opened through a remote
HTTP or HTTPS address retains that address. With no reachable address, the panel
explains how to enable access instead of offering a loopback command.
After setup, change the model under Settings → Server and the teaching choices
under Settings → This class. New installations use the common connection and
model in every class. Installations with imported class-specific routes also
show the option to replace those routes. Additional classes still need their
teaching configuration saved before admitting students. API keys stay in the
private installation; do not include them in student installation commands.
Entering an OpenRouter key checks it and loads the account's available models.
The model field offers suggestions and also accepts a manually entered ID.
Selecting a catalog model fills its input/output prices, shown in USD per million
tokens; they remain editable. Unknown or manually entered models require a price
review. These estimates omit provider caching and discounts.
New model budgets have usage limits disabled; recorded usage and costs remain
available. Existing saved limits are preserved on update. To remove an old limit,
select Unlimited usage for the relevant purpose and save. Open sessions retain
the configuration they captured when they started.
Fresh installs and updates add testing only when the installation has no skill
with that name; an edited local copy is preserved. Manage selections and authoring in
Skills → This class / By student / Library. Personal selections replace the class
selection until Use the class selection is chosen. Updates to a selected personal
skill apply to new sessions; existing conversations retain their frozen content. See
Skills workspace.
The optional Google fields accept a desktop OAuth client ID, client secret and
school domain. Domain administration, OAuth consent and trusting the application
for minors still happen in Google Workspace. Group membership additionally needs
service-account configuration, explained in its own optional section. Administrators
can change these connections under Settings → Server → School accounts; saved
identity changes require a server restart. Class admission addresses and groups
remain under Settings → This class → Student access. These controls only
appear when the identity plugin is bundled. Model connections likewise come from
installed inference plugins; neither the wizard nor the dashboard requires OpenRouter.
If a model provider is removed, the server can still start so its administrator can
select a replacement. Saved credentials are retained, but never read for absent plugins.
Under Settings → This class, Tutor writing gate offers Off, Block the first
attempt, and Block up to three attempts. It pauses exercise-code writes/edits
without a prior structured question in the current student turn. The attempt limit
prevents an endless retry loop. Student approval is still required afterward. Setup
files, shell commands and free mode are excluded. New classes start with the first-attempt
mode; existing classes keep their previous behavior. Changes affect new sessions only.
Clients predating this feature must run marea update before joining a class that
enables it. Restarting the client does not reset the policy or retry history of a turn.
Session exports and optional observability
Teachers can download conversations, events and usage from Sessions, filtered
by class, student and UTC dates, using names or pseudonyms. Administrators can
configure Settings → Server → External traces, test a synthetic connection, and
explicitly enable delivery with content. Langfuse supports self-hosted base URLs;
OTLP accepts an HTTP collector. No student-side credentials are needed.
Managed updates back up and migrate the database to schema 14. Export authorization,
content limits, retries and local/external retention are documented in
Observability. Existing clients remain compatible; their traces
contain only the diagnostic detail they actually recorded.
Student computers
Student computers need Git installed and available on PATH for project snapshots
and change tracking. The application runtime is included in the package.
Installation selects the recommended client without quer...
Marea 0.1.0-preview.28
Preview installation and updates
The commands below target 0.1.0-preview.28. Downloads are now compressed,
and initial installations reuse the installer and signature verifier already
fetched by the bootstrap script. Updates reuse installed files only after their
bytes match the newly signed inventory; damaged or changed files are downloaded.
The signature verifier ships without debugging symbols, and application code is
minified. Every platform still includes its native runtime and works without a
separate Bun or Node installation.
Existing updaters remain compatible: releases also retain the original raw assets
and manifest format. Updating from preview 26 or earlier uses the old downloader
once; subsequent updates use compression and verified reuse. New installations
benefit immediately. Download sizes differ by platform and by the files changed
between releases.
This preview retains the Safari 17.1 dashboard fixes, interrupted-install recovery,
abandoned-lock recovery, stable password validation layout and restored Marea Code
heading from preview 26.
Fresh teacher installations open a browser setup wizard on their first launch.
Existing schools retain their data and settings. Earlier features remain available:
LAN HTTP, Google sign-in, provider model discovery, unlimited usage defaults,
the tutor writing gate, the example testing skill, session ZIP exports and optional
full-content observability through Langfuse or an OTLP collector.
Published installers and tags remain immutable.
Teacher server
macOS Apple Silicon or Linux x64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.28/install.sh | sh -s -- serverWindows x64, in PowerShell:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.28/install.ps1'))) -Component serverThe installer puts programs and launchers under ~/.marea-preview/server.
It does not ask for school data in the terminal. On Windows, reopen the terminal
after installation to pick up the per-user PATH entry, then run:
marea-teacherOn the first launch, a browser opens a five-step wizard:
- School, first class and teacher account, with password validation beside the fields.
- Provider key and model, with connection verification and model suggestions.
- Local-only, classroom LAN HTTP or a configured HTTPS origin; optional school accounts.
- Optional attention map, reports, automatic evaluation and example testing skill.
- Review and creation. Progress is visible while the installation is prepared.
The first class is saved in tutoring mode with student approval required for
project changes. Usage defaults to unlimited. Automatic evaluation is disabled
unless selected; enabling it also selects the bundled session-review method.
Optional map and report models initially use the verified main connection.
Prices, usage limits and separate feature models can be adjusted later in settings.
The local dashboard opens already signed in. HTTPS installations use their normal
login page. Further launches start the existing school without showing the wizard.
The LAN choice is remembered by the managed launcher.
If the browser cannot open, use the private setup link printed in the terminal
on the same computer. Setup listens only on loopback and requires the random
capability in that link, an exact Host and a same-origin POST. Passwords and API
keys remain in memory or private installation files; they are never put in the URL.
~/marea-prueba and other existing installations are not adopted or modified.
For HTTPS, choose an origin accessible from student computers and configure your
reverse proxy to forward to 127.0.0.1:18787 (or the chosen port), preserving the
public Host and Origin. Certificates, DNS and proxy setup are not provisioned by
the installer.
For a classroom LAN without a proxy or certificates, start with:
marea-teacher --allow-httpThe server listens on all IPv4 interfaces and prints the addresses students can
use. Open http://TEACHER_IP:18787/dashboard/ for the panel. Allow the selected
port through the teacher computer's firewall. HTTP carries passwords, sessions
and classroom traffic without encryption; use it only on a trusted network.
An explicit flag applies to that invocation. When LAN access was selected in the
first-run wizard, the managed launcher supplies the flag on subsequent launches.
Exact Host and Origin checks remain enabled for the computer's local IPs.
Download verification and release signatures are unchanged.
The student installation panel uses the running server's admitted addresses.
Opening the dashboard on localhost no longer puts localhost in student commands.
A single available address is selected automatically; when several networks are
available, choose the classroom address. A dashboard opened through a remote
HTTP or HTTPS address retains that address. With no reachable address, the panel
explains how to enable access instead of offering a loopback command.
After setup, change the model under Settings → Server and the teaching choices
under Settings → This class. New installations use the common connection and
model in every class. Installations with imported class-specific routes also
show the option to replace those routes. Additional classes still need their
teaching configuration saved before admitting students. API keys stay in the
private installation; do not include them in student installation commands.
Entering an OpenRouter key checks it and loads the account's available models.
The model field offers suggestions and also accepts a manually entered ID.
Selecting a catalog model fills its input/output prices, shown in USD per million
tokens; they remain editable. Unknown or manually entered models require a price
review. These estimates omit provider caching and discounts.
New model budgets have usage limits disabled; recorded usage and costs remain
available. Existing saved limits are preserved on update. To remove an old limit,
select Unlimited usage for the relevant purpose and save. Open sessions retain
the configuration they captured when they started.
Fresh installs and updates add testing only when the installation has no skill
with that name; an edited local copy is preserved.
The optional Google fields accept a desktop OAuth client ID, client secret and
school domain. Domain administration, OAuth consent and trusting the application
for minors still happen in Google Workspace. Group membership additionally needs
service-account configuration, explained in its own optional section. Administrators
can change these connections under Settings → Server → School accounts; saved
identity changes require a server restart. Class admission addresses and groups
remain under Settings → This class → Student access. These controls only
appear when the identity plugin is bundled. Model connections likewise come from
installed inference plugins; neither the wizard nor the dashboard requires OpenRouter.
If a model provider is removed, the server can still start so its administrator can
select a replacement. Saved credentials are retained, but never read for absent plugins.
Under Settings → This class, Tutor writing gate offers Off, Block the first
attempt, and Block up to three attempts. It pauses exercise-code writes/edits
without a prior structured question in the current student turn. The attempt limit
prevents an endless retry loop. Student approval is still required afterward. Setup
files, shell commands and free mode are excluded. New classes start with the first-attempt
mode; existing classes keep their previous behavior. Changes affect new sessions only.
Clients predating this feature must run marea update before joining a class that
enables it. Restarting the client does not reset the policy or retry history of a turn.
Session exports and optional observability
Teachers can download conversations, events and usage from Sessions, filtered
by class, student and UTC dates, using names or pseudonyms. Administrators can
configure Settings → Server → External traces, test a synthetic connection, and
explicitly enable delivery with content. Langfuse supports self-hosted base URLs;
OTLP accepts an HTTP collector. No student-side credentials are needed.
Managed updates back up and migrate the database to schema 13. Export authorization,
content limits, retries and local/external retention are documented in
Observability. Existing clients remain compatible; their traces
contain only the diagnostic detail they actually recorded.
Student computers
Student computers need Git installed and available on PATH for project snapshots
and change tracking. The application runtime is included in the package.
Installation selects the recommended client without querying the school server.
Replace the example origin with the address supplied by the teacher, including
http:// when the server was started with --allow-http. After installation,
a different server can be selected for one invocation:
marea --server http://192.168.1.20:18787--server takes precedence over MAREA_SERVER_URL and the saved installation
address. Compatibility discovery uses the same selected server. It does not
change the saved address or silently downgrade an HTTPS connection.
macOS Apple Silicon or Linux x64/ARM64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.28/install.sh | sh -s -- student --server https://marea.example.eduWindows x64/ARM64:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.28/install.ps1'))) -Component student -Server https://marea.example.eduRun marea from the project directory. The managed installation keeps student
sessio...
Marea 0.1.0-preview.26
Preview installation and updates
The commands below target 0.1.0-preview.26. This preview fixes dashboard modules
that failed after setup in Safari 17.1, including class progress once students have
criteria. The browser handoff now verifies Sessions, Map, Progress and Reports,
both immediately after setup and after reloading. The Marea Code heading uses its
serif face and accent color again.
First installations are staged before activation. Interrupted downloads no longer
occupy the final installation directory, and older download-only leftovers can
be removed with explicit confirmation. Uninstall can recover abandoned locks;
live-process warnings and confirmation remain in place. Setup also clarifies the
first class name, keeps password fields in place during validation, and removes
the redundant automatic-evaluation method label.
Fresh teacher installations open a browser setup wizard on their first launch.
Existing schools retain their data and settings. Earlier features remain available:
LAN HTTP, Google sign-in, provider model discovery, unlimited usage defaults,
the tutor writing gate, the example testing skill, session ZIP exports and optional
full-content observability through Langfuse or an OTLP collector.
Published installers and tags remain immutable.
Teacher server
macOS Apple Silicon or Linux x64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.26/install.sh | sh -s -- serverWindows x64, in PowerShell:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.26/install.ps1'))) -Component serverThe installer puts programs and launchers under ~/.marea-preview/server.
It does not ask for school data in the terminal. On Windows, reopen the terminal
after installation to pick up the per-user PATH entry, then run:
marea-teacherOn the first launch, a browser opens a five-step wizard:
- School, first class and teacher account, with password validation beside the fields.
- Provider key and model, with connection verification and model suggestions.
- Local-only, classroom LAN HTTP or a configured HTTPS origin; optional school accounts.
- Optional attention map, reports, automatic evaluation and example testing skill.
- Review and creation. Progress is visible while the installation is prepared.
The first class is saved in tutoring mode with student approval required for
project changes. Usage defaults to unlimited. Automatic evaluation is disabled
unless selected; enabling it also selects the bundled session-review method.
Optional map and report models initially use the verified main connection.
Prices, usage limits and separate feature models can be adjusted later in settings.
The local dashboard opens already signed in. HTTPS installations use their normal
login page. Further launches start the existing school without showing the wizard.
The LAN choice is remembered by the managed launcher.
If the browser cannot open, use the private setup link printed in the terminal
on the same computer. Setup listens only on loopback and requires the random
capability in that link, an exact Host and a same-origin POST. Passwords and API
keys remain in memory or private installation files; they are never put in the URL.
~/marea-prueba and other existing installations are not adopted or modified.
For HTTPS, choose an origin accessible from student computers and configure your
reverse proxy to forward to 127.0.0.1:18787 (or the chosen port), preserving the
public Host and Origin. Certificates, DNS and proxy setup are not provisioned by
the installer.
For a classroom LAN without a proxy or certificates, start with:
marea-teacher --allow-httpThe server listens on all IPv4 interfaces and prints the addresses students can
use. Open http://TEACHER_IP:18787/dashboard/ for the panel. Allow the selected
port through the teacher computer's firewall. HTTP carries passwords, sessions
and classroom traffic without encryption; use it only on a trusted network.
An explicit flag applies to that invocation. When LAN access was selected in the
first-run wizard, the managed launcher supplies the flag on subsequent launches.
Exact Host and Origin checks remain enabled for the computer's local IPs.
Download verification and release signatures are unchanged.
The student installation panel uses the running server's admitted addresses.
Opening the dashboard on localhost no longer puts localhost in student commands.
A single available address is selected automatically; when several networks are
available, choose the classroom address. A dashboard opened through a remote
HTTP or HTTPS address retains that address. With no reachable address, the panel
explains how to enable access instead of offering a loopback command.
After setup, change the model under Settings → Server and the teaching choices
under Settings → This class. New installations use the common connection and
model in every class. Installations with imported class-specific routes also
show the option to replace those routes. Additional classes still need their
teaching configuration saved before admitting students. API keys stay in the
private installation; do not include them in student installation commands.
Entering an OpenRouter key checks it and loads the account's available models.
The model field offers suggestions and also accepts a manually entered ID.
Selecting a catalog model fills its input/output prices, shown in USD per million
tokens; they remain editable. Unknown or manually entered models require a price
review. These estimates omit provider caching and discounts.
New model budgets have usage limits disabled; recorded usage and costs remain
available. Existing saved limits are preserved on update. To remove an old limit,
select Unlimited usage for the relevant purpose and save. Open sessions retain
the configuration they captured when they started.
Fresh installs and updates add testing only when the installation has no skill
with that name; an edited local copy is preserved.
The optional Google fields accept a desktop OAuth client ID, client secret and
school domain. Domain administration, OAuth consent and trusting the application
for minors still happen in Google Workspace. Group membership additionally needs
service-account configuration, explained in its own optional section. Administrators
can change these connections under Settings → Server → School accounts; saved
identity changes require a server restart. Class admission addresses and groups
remain under Settings → This class → Student access. These controls only
appear when the identity plugin is bundled. Model connections likewise come from
installed inference plugins; neither the wizard nor the dashboard requires OpenRouter.
If a model provider is removed, the server can still start so its administrator can
select a replacement. Saved credentials are retained, but never read for absent plugins.
Under Settings → This class, Tutor writing gate offers Off, Block the first
attempt, and Block up to three attempts. It pauses exercise-code writes/edits
without a prior structured question in the current student turn. The attempt limit
prevents an endless retry loop. Student approval is still required afterward. Setup
files, shell commands and free mode are excluded. New classes start with the first-attempt
mode; existing classes keep their previous behavior. Changes affect new sessions only.
Clients predating this feature must run marea update before joining a class that
enables it. Restarting the client does not reset the policy or retry history of a turn.
Session exports and optional observability
Teachers can download conversations, events and usage from Sessions, filtered
by class, student and UTC dates, using names or pseudonyms. Administrators can
configure Settings → Server → External traces, test a synthetic connection, and
explicitly enable delivery with content. Langfuse supports self-hosted base URLs;
OTLP accepts an HTTP collector. No student-side credentials are needed.
Managed updates back up and migrate the database to schema 13. Export authorization,
content limits, retries and local/external retention are documented in
Observability. Existing clients remain compatible; their traces
contain only the diagnostic detail they actually recorded.
Student computers
Student computers need Git installed and available on PATH for project snapshots
and change tracking. The application runtime is included in the package.
Installation selects the recommended client without querying the school server.
Replace the example origin with the address supplied by the teacher, including
http:// when the server was started with --allow-http. After installation,
a different server can be selected for one invocation:
marea --server http://192.168.1.20:18787--server takes precedence over MAREA_SERVER_URL and the saved installation
address. Compatibility discovery uses the same selected server. It does not
change the saved address or silently downgrade an HTTPS connection.
macOS Apple Silicon or Linux x64/ARM64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.26/install.sh | sh -s -- student --server https://marea.example.eduWindows x64/ARM64:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.26/install.ps1'))) -Component student -Server https://marea.example.eduRun marea from the project directory. The managed installation keeps student
session state under ~/.marea-preview/student/student-state; it does not reuse
the old manual installation's ~/.marea state. MAREA_SERVER_URL and
MAREA_STATE_HOME still allow explicit overrides.
Updates and recovery
- `mar...
Marea 0.1.0-preview.25
Preview installation and updates
The commands below target 0.1.0-preview.25. This preview simplifies first-run
setup and organizes settings by task. It adds inline password validation, optional
educational features, web-managed school accounts and clearer Google group setup.
Drafts survive section changes, saved keys remain private, and saving reveals any
invalid field. It also fixes the blank dashboard on browsers without URL.parse.
Fresh teacher installations open a browser setup wizard on their first launch.
The wizard collects the school,
teacher account, model connection and classroom access, then saves a usable first
class and opens the dashboard. Existing schools retain their data and settings.
This version adds authorized session ZIP exports and optional full-content
observability through Langfuse or an OTLP collector. Delivery is off by default
and configured by a server administrator. Existing teaching choices and the
configurable tutor writing gate are preserved. Earlier installation, LAN HTTP,
model catalog, unlimited usage defaults and plugin-driven setup are included.
Published installers and tags remain immutable.
Teacher server
macOS Apple Silicon or Linux x64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.25/install.sh | sh -s -- serverWindows x64, in PowerShell:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.25/install.ps1'))) -Component serverThe installer puts programs and launchers under ~/.marea-preview/server.
It does not ask for school data in the terminal. On Windows, reopen the terminal
after installation to pick up the per-user PATH entry, then run:
marea-teacherOn the first launch, a browser opens a five-step wizard:
- School, first class and teacher account, with password validation beside the fields.
- Provider key and model, with connection verification and model suggestions.
- Local-only, classroom LAN HTTP or a configured HTTPS origin; optional school accounts.
- Optional attention map, reports, automatic evaluation and example testing skill.
- Review and creation. Progress is visible while the installation is prepared.
The first class is saved in tutoring mode with student approval required for
project changes. Usage defaults to unlimited. Automatic evaluation is disabled
unless selected; enabling it also selects the bundled session-review method.
Optional map and report models initially use the verified main connection.
Prices, usage limits and separate feature models can be adjusted later in settings.
The local dashboard opens already signed in. HTTPS installations use their normal
login page. Further launches start the existing school without showing the wizard.
The LAN choice is remembered by the managed launcher.
If the browser cannot open, use the private setup link printed in the terminal
on the same computer. Setup listens only on loopback and requires the random
capability in that link, an exact Host and a same-origin POST. Passwords and API
keys remain in memory or private installation files; they are never put in the URL.
~/marea-prueba and other existing installations are not adopted or modified.
For HTTPS, choose an origin accessible from student computers and configure your
reverse proxy to forward to 127.0.0.1:18787 (or the chosen port), preserving the
public Host and Origin. Certificates, DNS and proxy setup are not provisioned by
the installer.
For a classroom LAN without a proxy or certificates, start with:
marea-teacher --allow-httpThe server listens on all IPv4 interfaces and prints the addresses students can
use. Open http://TEACHER_IP:18787/dashboard/ for the panel. Allow the selected
port through the teacher computer's firewall. HTTP carries passwords, sessions
and classroom traffic without encryption; use it only on a trusted network.
An explicit flag applies to that invocation. When LAN access was selected in the
first-run wizard, the managed launcher supplies the flag on subsequent launches.
Exact Host and Origin checks remain enabled for the computer's local IPs.
Download verification and release signatures are unchanged.
The student installation panel uses the running server's admitted addresses.
Opening the dashboard on localhost no longer puts localhost in student commands.
A single available address is selected automatically; when several networks are
available, choose the classroom address. A dashboard opened through a remote
HTTP or HTTPS address retains that address. With no reachable address, the panel
explains how to enable access instead of offering a loopback command.
After setup, change the model under Settings → Server and the teaching choices
under Settings → This class. New installations use the common connection and
model in every class. Installations with imported class-specific routes also
show the option to replace those routes. Additional classes still need their
teaching configuration saved before admitting students. API keys stay in the
private installation; do not include them in student installation commands.
Entering an OpenRouter key checks it and loads the account's available models.
The model field offers suggestions and also accepts a manually entered ID.
Selecting a catalog model fills its input/output prices, shown in USD per million
tokens; they remain editable. Unknown or manually entered models require a price
review. These estimates omit provider caching and discounts.
New model budgets have usage limits disabled; recorded usage and costs remain
available. Existing saved limits are preserved on update. To remove an old limit,
select Unlimited usage for the relevant purpose and save. Open sessions retain
the configuration they captured when they started.
Fresh installs and updates add testing only when the installation has no skill
with that name; an edited local copy is preserved.
The optional Google fields accept a desktop OAuth client ID, client secret and
school domain. Domain administration, OAuth consent and trusting the application
for minors still happen in Google Workspace. Group membership additionally needs
service-account configuration, explained in its own optional section. Administrators
can change these connections under Settings → Server → School accounts; saved
identity changes require a server restart. Class admission addresses and groups
remain under Settings → This class → Student access. These controls only
appear when the identity plugin is bundled. Model connections likewise come from
installed inference plugins; neither the wizard nor the dashboard requires OpenRouter.
If a model provider is removed, the server can still start so its administrator can
select a replacement. Saved credentials are retained, but never read for absent plugins.
Under Settings → This class, Tutor writing gate offers Off, Block the first
attempt, and Block up to three attempts. It pauses exercise-code writes/edits
without a prior structured question in the current student turn. The attempt limit
prevents an endless retry loop. Student approval is still required afterward. Setup
files, shell commands and free mode are excluded. New classes start with the first-attempt
mode; existing classes keep their previous behavior. Changes affect new sessions only.
Clients predating this feature must run marea update before joining a class that
enables it. Restarting the client does not reset the policy or retry history of a turn.
Session exports and optional observability
Teachers can download conversations, events and usage from Sessions, filtered
by class, student and UTC dates, using names or pseudonyms. Administrators can
configure Settings → Server → External traces, test a synthetic connection, and
explicitly enable delivery with content. Langfuse supports self-hosted base URLs;
OTLP accepts an HTTP collector. No student-side credentials are needed.
Managed updates back up and migrate the database to schema 13. Export authorization,
content limits, retries and local/external retention are documented in
Observability. Existing clients remain compatible; their traces
contain only the diagnostic detail they actually recorded.
Student computers
Student computers need Git installed and available on PATH for project snapshots
and change tracking. The application runtime is included in the package.
Installation selects the recommended client without querying the school server.
Replace the example origin with the address supplied by the teacher, including
http:// when the server was started with --allow-http. After installation,
a different server can be selected for one invocation:
marea --server http://192.168.1.20:18787--server takes precedence over MAREA_SERVER_URL and the saved installation
address. Compatibility discovery uses the same selected server. It does not
change the saved address or silently downgrade an HTTPS connection.
macOS Apple Silicon or Linux x64/ARM64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.25/install.sh | sh -s -- student --server https://marea.example.eduWindows x64/ARM64:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.25/install.ps1'))) -Component student -Server https://marea.example.eduRun marea from the project directory. The managed installation keeps student
session state under ~/.marea-preview/student/student-state; it does not reuse
the old manual installation's ~/.marea state. MAREA_SERVER_URL and
MAREA_STATE_HOME still allow explicit overrides.
Updates and recovery
marea --version/marea-teacher --version: installed preview version.status(or--status): managed installation details, with no ...
Marea 0.1.0-preview.22
Preview installation and updates
The commands below target 0.1.0-preview.22. Fresh teacher installations open a
browser setup wizard on their first launch. The wizard collects the school,
teacher account, model connection and classroom access, then saves a usable first
class and opens the dashboard. Existing schools retain their data and settings.
This version adds authorized session ZIP exports and optional full-content
observability through Langfuse or an OTLP collector. Delivery is off by default
and configured by a server administrator. Existing teaching choices and the
configurable tutor writing gate are preserved. Earlier installation, LAN HTTP,
model catalog, unlimited usage defaults and plugin-driven setup are included.
Published installers and tags remain immutable.
Teacher server
macOS Apple Silicon or Linux x64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.22/install.sh | sh -s -- serverWindows x64, in PowerShell:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.22/install.ps1'))) -Component serverThe installer puts programs and launchers under ~/.marea-preview/server.
It does not ask for school data in the terminal. On Windows, reopen the terminal
after installation to pick up the per-user PATH entry, then run:
marea-teacherOn the first launch, a browser opens a four-step wizard:
- School, first class and teacher account (password: 12–256 characters).
- Provider key and model, with OpenRouter verification, suggestions and editable prices.
- Local-only, classroom LAN HTTP or a configured HTTPS origin; optional Google and testing skill.
- Review and creation. Progress is visible while the installation is prepared.
The first class is saved in tutoring mode with automatic evaluation disabled and
student approval required for project changes. Usage defaults to unlimited.
The local dashboard opens already signed in. HTTPS installations use their normal
login page. Further launches start the existing school without showing the wizard.
The LAN choice is remembered by the managed launcher.
If the browser cannot open, use the private setup link printed in the terminal
on the same computer. Setup listens only on loopback and requires the random
capability in that link, an exact Host and a same-origin POST. Passwords and API
keys remain in memory or private installation files; they are never put in the URL.
~/marea-prueba and other existing installations are not adopted or modified.
For HTTPS, choose an origin accessible from student computers and configure your
reverse proxy to forward to 127.0.0.1:18787 (or the chosen port), preserving the
public Host and Origin. Certificates, DNS and proxy setup are not provisioned by
the installer.
For a classroom LAN without a proxy or certificates, start with:
marea-teacher --allow-httpThe server listens on all IPv4 interfaces and prints the addresses students can
use. Open http://TEACHER_IP:18787/dashboard/ for the panel. Allow the selected
port through the teacher computer's firewall. HTTP carries passwords, sessions
and classroom traffic without encryption; use it only on a trusted network.
An explicit flag applies to that invocation. When LAN access was selected in the
first-run wizard, the managed launcher supplies the flag on subsequent launches.
Exact Host and Origin checks remain enabled for the computer's local IPs.
Download verification and release signatures are unchanged.
The student installation panel uses the running server's admitted addresses.
Opening the dashboard on localhost no longer puts localhost in student commands.
A single available address is selected automatically; when several networks are
available, choose the classroom address. A dashboard opened through a remote
HTTP or HTTPS address retains that address. With no reachable address, the panel
explains how to enable access instead of offering a loopback command.
After setup, change the model under Settings → Server and the teaching choices
under Settings → This class. New installations use the common connection and
model in every class. Installations with imported class-specific routes also
show the option to replace those routes. Additional classes still need their
teaching configuration saved before admitting students. API keys stay in the
private installation; do not include them in student installation commands.
Entering an OpenRouter key checks it and loads the account's available models.
The model field offers suggestions and also accepts a manually entered ID.
Selecting a catalog model fills its input/output prices, shown in USD per million
tokens; they remain editable. Unknown or manually entered models require a price
review. These estimates omit provider caching and discounts.
New model budgets have usage limits disabled; recorded usage and costs remain
available. Existing saved limits are preserved on update. To remove an old limit,
select Unlimited usage for the relevant purpose and save. Open sessions retain
the configuration they captured when they started.
Fresh installs and updates add testing only when the installation has no skill
with that name; an edited local copy is preserved.
The optional Google fields accept a desktop OAuth client ID, client secret and
school domain. Domain administration, OAuth consent and trusting the application
for minors still happen in Google Workspace. Group membership additionally needs
service-account configuration in the optional advanced fields. These controls only
appear when the identity plugin is bundled. Model connections likewise come from
installed inference plugins; neither the wizard nor the dashboard requires OpenRouter.
If a model provider is removed, the server can still start so its administrator can
select a replacement. Saved credentials are retained, but never read for absent plugins.
Under Settings → This class, Tutor writing gate offers Off, Block the first
attempt, and Block up to three attempts. It pauses exercise-code writes/edits
without a prior structured question in the current student turn. The attempt limit
prevents an endless retry loop. Student approval is still required afterward. Setup
files, shell commands and free mode are excluded. New classes start with the first-attempt
mode; existing classes keep their previous behavior. Changes affect new sessions only.
Clients predating this feature must run marea update before joining a class that
enables it. Restarting the client does not reset the policy or retry history of a turn.
Session exports and optional observability
Teachers can download conversations, events and usage from Sessions, filtered
by class, student and UTC dates, using names or pseudonyms. Administrators can
configure Settings → Server → Observability, test a synthetic connection, and
explicitly enable delivery with content. Langfuse supports self-hosted base URLs;
OTLP accepts an HTTP collector. No student-side credentials are needed.
Managed updates back up and migrate the database to schema 13. Export authorization,
content limits, retries and local/external retention are documented in
Observability. Existing clients remain compatible; their traces
contain only the diagnostic detail they actually recorded.
Student computers
Student computers need Git installed and available on PATH for project snapshots
and change tracking. The application runtime is included in the package.
Installation selects the recommended client without querying the school server.
Replace the example origin with the address supplied by the teacher, including
http:// when the server was started with --allow-http. After installation,
a different server can be selected for one invocation:
marea --server http://192.168.1.20:18787--server takes precedence over MAREA_SERVER_URL and the saved installation
address. Compatibility discovery uses the same selected server. It does not
change the saved address or silently downgrade an HTTPS connection.
macOS Apple Silicon or Linux x64/ARM64:
curl -fsSL https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.22/install.sh | sh -s -- student --server https://marea.example.eduWindows x64/ARM64:
& ([scriptblock]::Create((Invoke-RestMethod 'https://github.com/IES-Rafael-Alberti/marea-code/releases/download/v0.1.0-preview.22/install.ps1'))) -Component student -Server https://marea.example.eduRun marea from the project directory. The managed installation keeps student
session state under ~/.marea-preview/student/student-state; it does not reuse
the old manual installation's ~/.marea state. MAREA_SERVER_URL and
MAREA_STATE_HOME still allow explicit overrides.
Updates and recovery
marea --version/marea-teacher --version: installed preview version.status(or--status): managed installation details, with no credentials.update(or--update): check the latest published preview and ask to install
it, without starting the application. Publishing alone does not notify everyone.update --version 0.1.0-preview.22: try a specific published preview.- Ordinary startup offers only a recommended version for this component and
wire protocol. Declining keeps the installed version. A noninteractive start
never accepts updates; discovery failures leave the current installation usable. - Client and server release numbers need not match. A common protocol and the
required baseline capabilities determine compatibility; optional capabilities
remain optional. Support is bounded to the advertised protocol generation,
rather than an indefinite collection of historical adapters. - If the school reports an incompatible prot...