Skip to content

InteJer v0.1.0-beta.12

Choose a tag to compare

View all tags
@azamkhan555622848 azamkhan555622848 released this 28 Jul 12:54
v0.1.0-beta.12
25bb302
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

The agents can see images now

Ask InteJer about a screenshot, a UI mock-up, a PCB or 3D render, or a photo, and
it will actually look at it.

Until now it could not. The model that runs your session is text-only, so an
image was invisible to it — and rather than say so, it would often reason from
the filename and sound confident about a picture it had never seen. The advisor
model behind each agent is able to see (Kimi K3 and Claude Sonnet 5 are both
multimodal); it was simply never handed the image.

Now the agent passes the file to its advisor and works from what the advisor
actually reports: layout and spacing, colours, labels, what is wrong and where.
This applies to all three agents — InteJer Agent, Frontend Developer, Designer.

Practical notes:

  • Point at the file however you like ("look at screenshots/home.png"), or just
    ask about a render the agent produced itself.
  • Up to 4 images per consult, 5 MB each, PNG/JPG/GIF/WEBP. Anything skipped is
    reported back rather than silently dropped, so the agent can never quietly
    reason about an image that never arrived.
  • Images are sent only when the question is genuinely visual. They cost real
    tokens and, unlike the conversation, are not cached.
  • Expect a visual consult to take longer than a text one — the vision models are
    slower, and a full-screen screenshot is a lot to read.

The composer's attach button is still hidden on Z.AI models; that is separate and
unchanged. Point the agent at a file path instead.

Also in this release

Everything from 0.1.0-beta.11, if you skipped it — account sign-in replacing
access keys, and the 20 MB attachment cap that stops large files from bloating
the app until it crawls.

Known issue

Requests can occasionally be blocked by the network layer in front of our API,
surfacing as "Forbidden: request was blocked by a gateway or proxy." It is
not your account and not your credentials — signing out will not help. It is
being raised with the hosting provider; starting a fresh session is the current
workaround.

Assets 3
Loading